IndexNow: Get Your Blog Indexed in Bing and ChatGPT

Photo by Campaign Creators on Unsplash

You spent weeks getting your blog to rank on Google. Meanwhile the index that feeds ChatGPT, Microsoft Copilot, DuckDuckGo, Yahoo, and Ecosia never heard your post exists. That index belongs to Bing. And the fastest way into it is a protocol most SEO guides still skip: IndexNow.

IndexNow is a free, open protocol that lets you instantly tell search engines a URL was added, updated, or removed. Instead of waiting days for a crawler to stumble onto your page, you send one ping and participating engines, led by Bing and Yandex, queue it for crawling fast. Google doesn't take part. But the engines behind AI search do.

Here's why that matters more in 2026 than it ever has. ChatGPT passed 900 million weekly active users in February 2026, and ChatGPT Search reads Bing's index to answer them. Bing itself crossed 1 billion monthly active users. "Getting indexed in Bing" stopped being a rounding error. It's now your on-ramp to roughly a billion people asking AI questions every week.

By the end of this guide you'll have IndexNow live, know exactly which engines it reaches, and have a way to confirm you're actually in Bing's index.

What is IndexNow?

IndexNow is defined as an open, free protocol that lets you notify search engines the moment a URL is added, updated, or deleted. You host a small key file on your domain, then send a simple HTTP request listing the changed URLs. The engine verifies the key and queues those pages for crawling.

Think of it as push instead of pull. Traditional indexing is pull: a crawler decides when to revisit your site and discover changes. IndexNow flips that. You push the news the second it happens, so the engine isn't guessing.

Microsoft and Yandex launched IndexNow in October 2021. It's now backed by Bing, Yandex, Naver, Seznam.cz, and Yep, plus the Internet Archive and Amazon. The protocol is keyless in spirit (no account, no OAuth) and costs nothing.

One submission fans out to every participating engine. The protocol's own rule is blunt: "Search engines adopting the IndexNow protocol agree that submitted URLs will be automatically shared with all other participating search engines." Ping one, reach all.

Why Bing indexing decides your AI search visibility

Here's the contrarian part. Most SEO advice treats Bing as an afterthought because its search box holds only about 5% of global market share. That number badly undersells Bing's real reach, because Bing's index powers far more than Bing.com.

Call it the Bing Bridge: Bing's index is the bridge between your blog and the AI tools your readers now use to ask questions. Cross that bridge and you show up in places that have nothing to do with Bing.com.

Bing's index feeds:

• ChatGPT Search, which leans on Bing's index to answer queries. As Yoast puts it plainly: "If your site isn't in Bing's index, it won't appear in ChatGPT's results."

• Microsoft Copilot, which uses Bing for external web retrieval across Windows, Edge, and Microsoft 365.

• DuckDuckGo, which pulls its primary results from Bing.

• Yahoo (US), which has been served by Bing since 2019.

• Ecosia and AOL, which also draw on Bing.

Now stack the 2026 numbers on top. ChatGPT hit 900 million weekly active users in February 2026 and is closing on a billion. Bing crossed 1 billion monthly active users for the first time. AI search referrals are still small as a share of total traffic, but they grew roughly 5x year over year, and Ahrefs found AI visitors convert at far higher rates than plain organic clicks.

So the math is simple. You can keep optimizing only for the engine that doesn't accept instant submissions (Google), or you can also feed the index that pipes into a billion AI conversations a week. IndexNow is how you feed it without lifting a finger after setup. For the wider AI-citation playbook, see how to rank in Google AI Overviews and get cited by ChatGPT.

How IndexNow actually works

IndexNow has three moving parts: a key, a key file, and a submission. None of them are hard.

1. The key. You generate a random string of 8 to 128 characters. The allowed set is letters (a-z, A-Z), numbers (0-9), and dashes. A typical key looks like a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6.

2. The key file. You host a text file named {your-key}.txt at your domain root. Its only contents are the key itself. This proves you control the domain. One catch worth knowing: the file's location scopes what it can submit. A key file at /blog/key.txt can only submit URLs under /blog/, not the rest of the site. Put it at the root to cover everything.

3. The submission. You send the changed URLs to an IndexNow endpoint. You can ping one engine directly (Bing, Yandex, and so on) or hit the shared endpoint at api.indexnow.org, which distributes to all of them.

A single submission can carry up to 10,000 URLs in one POST request. That makes IndexNow practical for bulk updates, migrations, and large publishing runs, not just one post at a time.

Here's a minimal single-URL ping using GET:

GET https://api.indexnow.org/indexnow?url=https://yourdomain.com/blog/your-post&key=YOUR_KEY

And a batch submission using POST, which is what you'll use in practice:

POST https://api.indexnow.org/indexnow
Content-Type: application/json

{
  "host": "yourdomain.com",
  "key": "YOUR_KEY",
  "keyLocation": "https://yourdomain.com/key.txt",
  "urlList": [
    "https://yourdomain.com/blog/post-one",
    "https://yourdomain.com/blog/post-two"
  ]
}

An HTTP 200 or 202 response means "received," not "indexed." The engine still decides whether and when to crawl. If you get a 429, you're being rate limited. Wait at least ten minutes before resubmitting the same unchanged URL.

IndexNow vs sitemaps vs Google's Indexing API

These three tools get confused constantly. They solve different problems and you should run more than one. Here's the honest breakdown.

The takeaway: a sitemap is your full inventory, IndexNow is your instant push for changes, and webmaster tools are your feedback loop. Use all three. Fabrice Canel and Krishna Madhavan of Microsoft Bing say it directly: "By combining sitemaps for comprehensive site coverage with IndexNow for fast, URL-level submission, you provide the strongest foundation for keeping your content fresh, discoverable, and visible in both traditional and AI-powered search experiences."

Note what's missing from that list: Google does not support IndexNow. It said it would "test" the protocol back in 2021 and never adopted it. So for Google you still lean on sitemaps, Search Console, and the Indexing API. If Google indexing is your bottleneck, work through the 2026 fix stack for blogs Google won't index.

Which engines (and AI tools) one IndexNow ping reaches

When you submit a URL through IndexNow, it doesn't just land at Bing. It propagates across the whole participating network, and several of those engines quietly power tools your readers use every day.

One POST, and you've notified the index behind the world's most-used AI assistant plus four regional search leaders. That's the leverage no Google-only strategy can match.

The adoption numbers back up that this is mainstream infrastructure, not a fringe trick. By late 2024, Microsoft reported that around 18% of all newly clicked URLs in Bing's web results came in through IndexNow, with billions of URLs submitted daily. Cloudflare wires IndexNow into its Crawler Hints feature, so a huge slice of the web is already submitting automatically, sometimes without the site owner realizing it.

The 3-Signal Indexing Stack

If you want to stop guessing about indexing, run what I call the 3-Signal Indexing Stack. It's three signals that each do one job, and they compound when used together.

1. The map (sitemap.xml). Your complete, current inventory of every URL. Engines read it to understand your full site. Keep it auto-updated and accurate, with honest lastmod dates.

2. The push (IndexNow). The instant "this changed" signal. Fired on every publish, update, and delete, so engines never wait to learn about a change.

3. The proof (webmaster feedback). Bing Webmaster Tools and Google Search Console tell you whether the page actually got indexed, what it ranks for, and why it didn't if it failed.

Most blogs run signal one and forget the other two. They publish, generate a sitemap, then sit back and hope. The stack closes the loop: you tell engines what exists (map), tell them the second it changes (push), then verify the result (proof). Skip any one and you're flying half-blind.

Bing's own team ties this directly to AI answers. Canel and Madhavan note that "freshness signals directly influence how quickly updates are reflected in search results and AI generated answers." The push signal is your freshness signal.

How fast does IndexNow get you indexed?

This is the part competing articles wave at without numbers. Here's a realistic before-and-after, using the time ranges Microsoft and the protocol team have described.

Fabrice Canel, Principal Product Manager at Microsoft Bing and the protocol's public face, frames the gap like this: "Without IndexNow, it can take days to weeks to get content changes reflected in search engines. With IndexNow, this is more like seconds to max two days."

For a blog that publishes several times a week, that delta is the difference between your fresh take landing while a topic is hot versus surfacing after the conversation moved on. Speed-to-index is a ranking and citation advantage, not a vanity metric.

How to set up IndexNow manually (step by step)

If you run your own stack, you can wire up IndexNow by hand in about fifteen minutes. Here's the full checklist. Copy it.

1. Generate a key. Create a random string of 8 to 128 characters using a-z, A-Z, 0-9, and dashes. A 32-character hex string is plenty.

2. Create the key file. Make a file named {your-key}.txt containing only the key. Example: a1b2c3d4e5f6...txt.

3. Host it at your root. Upload it to https://yourdomain.com/{your-key}.txt. Confirm it loads in a browser and returns the raw key.

4. Submit your URLs. Send a POST to https://api.indexnow.org/indexnow with your host, key, keyLocation, and urlList (up to 10,000 URLs).

5. Automate the ping. Hook the submission into your publish flow so every new or updated post fires automatically. A manual ping you forget to send is worthless.

6. Verify in Bing Webmaster Tools. Open the IndexNow section to see submitted URLs and their status.

Here's a reusable curl command for step 4:

curl -X POST "https://api.indexnow.org/indexnow" \
  -H "Content-Type: application/json" \
  -d '{
    "host": "yourdomain.com",
    "key": "YOUR_KEY",
    "keyLocation": "https://yourdomain.com/YOUR_KEY.txt",
    "urlList": ["https://yourdomain.com/blog/new-post"]
  }'

On WordPress, plugins like Yoast and Rank Math handle the key file and pings for you. On Cloudflare, the Crawler Hints toggle submits to IndexNow automatically based on cache activity. The hard part isn't any single step. It's remembering to fire the ping on every single content change, forever.

The faster path: let your AI publish and ping for you

Step 5 above (automate the ping) is where most setups quietly fall apart. People wire up the key file, submit once, then forget IndexNow exists. New posts go out. No ping fires. The whole point evaporates.

This is the gap Quillly closes. The second a post goes live on your own domain, Quillly tells Google, Bing, Yandex, Naver, Seznam.cz, and Yep automatically, using the Google Indexing API plus IndexNow with zero setup. There's no key file to host, no curl command to remember, no plugin to babysit. It runs on the free plan.

In practice, the flow looks like this. Your AI writes the post in Claude, ChatGPT, or Cursor. It calls create_blog to save the draft, check_blog_seo to score it against the SEO criteria, then publish_blog to push it live. That final call is what fires the multi-engine notification. You publish once; the whole IndexNow network and Google both hear about it in the same breath.

That's the difference between IndexNow as a chore you maintain and IndexNow as plumbing that just works. If you're building an end-to-end pipeline, a content engine in Claude Code wires the writing, scoring, and publishing into one loop. The point of either approach is the same: the index push should be invisible, not another box on your to-do list.

How to confirm you're actually in Bing (and ChatGPT)

Submitting is not the same as indexing. Close the loop with the proof signal.

Start in Bing Webmaster Tools. Use URL Inspection to check a specific page's index status, and open the IndexNow panel to confirm your submissions are landing. If a site is already verified in Google Search Console, Bing lets you import that verification, so connecting takes a minute, not an afternoon.

In February 2026, Bing shipped something genuinely new for this: an AI Performance report in Bing Webmaster Tools, in public preview. For the first time, publishers can see how often their content gets cited in generative answers across Copilot and Bing's AI summaries, including total citations and which URLs were referenced. Microsoft's framing: "For the first time, you can understand how often your content is cited in generative answers, with clear visibility into which URLs are referenced." That report is the closest thing yet to a "did ChatGPT-style search use my page" dashboard.

On the Google side, keep watching Search Console for indexing and impressions. Pulling both engines into one view saves you tab-juggling; here's an MCP workflow for Google Search Console that does exactly that. To go further on AI-specific traffic, tracking AI search traffic shows which referrals come from ChatGPT, Perplexity, and friends.

What IndexNow won't do (the honest limits)

IndexNow is a sharp tool, not a magic wand. Set expectations correctly.

• It doesn't touch Google. Google never adopted the protocol. For Google, use sitemaps, Search Console, and the Indexing API.

• It doesn't guarantee indexing. A 200 means "received." Each engine independently decides whether your page is worth indexing. Thin or duplicate content still gets skipped.

• It gives no data back. IndexNow is notify-only. For status, rankings, and keywords you still need webmaster tools.

• It won't fix bad content. Fast discovery of a weak page just gets that page ignored faster. Indexing speed amplifies quality; it doesn't replace it.

One more 2026 nuance worth knowing. ChatGPT's reliance on Bing is no longer absolute. OpenAI runs its own crawler, OAI-SearchBot, and SEO researcher Aleyda Solis has shown ChatGPT sometimes pulls Google SERP snippets as a fallback too. So the smart move isn't "rank in Bing and stop." It's "be in Bing's index (IndexNow handles that) and stay crawlable by the AI bots." Keep OAI-SearchBot and GPTBot allowed in your robots.txt, and don't block the crawlers you're trying to win. The same discipline applies to every AI crawler; optimizing for GPTBot, ClaudeBot, and PerplexityBot covers the full robots.txt and access checklist.

Frequently asked questions

Does Google use IndexNow?

No. Google does not participate in IndexNow. It announced in November 2021 that it would "test the potential benefits" of the protocol, but it never adopted it for general web pages and still doesn't. For Google, your indexing signals remain an accurate XML sitemap, Google Search Console, and the Google Indexing API. IndexNow covers Bing, Yandex, Naver, Seznam.cz, and Yep instead, so run both approaches in parallel.

Does ChatGPT Search use Bing's index?

Yes, primarily. ChatGPT Search reads Bing's index to find and cite web pages, supplemented by OpenAI's own OAI-SearchBot crawler. As Yoast states, "If your site isn't in Bing's index, it won't appear in ChatGPT's results." That's why IndexNow matters for AI visibility: it's the fastest way to get a new page into the Bing index that ChatGPT depends on.

How long does Bing take to index a page?

It varies by site health, but IndexNow changes the math dramatically. Microsoft's Fabrice Canel describes the shift as going from "days to weeks" with traditional crawling down to "seconds to max two days" with IndexNow. New or low-authority sites sit at the slower end; established sites that publish often can see new posts crawled within hours of an IndexNow ping.

Do I still need a sitemap if I use IndexNow?

Yes. They do different jobs. A sitemap is your complete inventory of every URL, which engines (including Google) read to understand your whole site. IndexNow is an instant "this one changed" push for individual URLs. Microsoft explicitly recommends combining both: sitemaps for coverage, IndexNow for speed. Drop the sitemap and you lose Google's main discovery signal entirely.

How many URLs can I submit to IndexNow at once?

Up to 10,000 URLs in a single POST request. That makes IndexNow well suited to bulk jobs like site migrations, large content refreshes, or programmatic publishing runs, not just one post at a time. Separately, Bing Webmaster Tools allows up to 10,000 URL submissions per day per domain through its own submission tools.

Is IndexNow free, and is it worth it without Google?

IndexNow is completely free and open. It's worth setting up even though Google opts out, because the engines that do participate, led by Bing, feed ChatGPT, Copilot, DuckDuckGo, Yahoo, and Ecosia. With ChatGPT near a billion weekly users, the Bing-fed audience is now large enough that ignoring it leaves real visibility on the table.

Does submitting via IndexNow guarantee my page gets indexed?

No. IndexNow guarantees fast discovery, not indexing. A successful submission returns HTTP 200, meaning the engine received your notification. Each engine still applies its own quality and relevance checks before deciding to index. Strong, original, well-structured content gets indexed; thin or duplicate pages get skipped, just faster.

The bottom line

IndexNow is the cheapest, fastest indexing lever most blogs aren't pulling. Three numbers make the case. Bing's index now feeds ChatGPT's 900 million-plus weekly users. Around 18% of newly clicked URLs in Bing already arrive through IndexNow. And the time-to-index gap shrinks from weeks to roughly seconds-to-two-days once you turn it on.

So do three things. Set up the 3-Signal Indexing Stack: a clean sitemap, IndexNow on every change, and webmaster tools to verify. Keep your AI crawlers allowed in robots.txt so you're eligible for citations, not just rankings. And automate the ping, because the IndexNow setup you forget to maintain helps no one.

Want your AI to actually publish the post it just wrote, then notify Google and five more search engines the instant it goes live? Connect Quillly to Claude, ChatGPT, or Cursor in 30 seconds.