IndexNow and AI Search: What It Does and Doesn't Do

IndexNow is a change-notification protocol. You host a key file at your site root to prove you own the domain. When a page changes, you send its URL and your key to a participating endpoint. The engine then knows the page is worth recrawling, instead of waiting to rediscover it.

A single-URL submission is a plain GET request:

https://www.bing.com/indexnow?url=https://www.example.com/pricing&key=YOUR_KEY

That is the whole mechanism. It works at the access stage: it nudges a crawler to come and fetch. It does not decide whether the engine stores the page, whether a retrieval system pulls it into an answer, or whether a model cites it. Those are three separate stages, and IndexNow touches none of them directly.

If you want the protocol basics in one place, see our IndexNow definition.

The IndexNow documentation is short, and it is clear about scope. A case-insensitive search of it for "AI", "LLM", "Copilot", "generative" and "chatbot" returns zero hits. The protocol was written for search engine discovery, and that is all it describes.

The response codes are just as narrow. A 200 tells you the endpoint received your submission. It does not tell you the URL was crawled, indexed or ranked, and the spec guarantees nothing beyond receipt.

What this means in practice:

• A dashboard full of green 200s proves your integration works. It proves nothing about visibility.
• Any tool or agency that reports "IndexNow submitted" as an AI win is reporting plumbing, not an outcome.
• If you need to know whether Bing actually holds a page, check Bing Webmaster Tools, not the ping log.

We walk through the documentation line by line in what the IndexNow protocol docs promise.

The IndexNow registry, as fetched in August 2026, lists exactly seven consuming endpoints: Bing, Yandex, Seznam, Naver, Yep, the Internet Archive and Amazonbot. Google is not on the list. Neither OpenAI, Perplexity nor Anthropic appears.

That single fact settles most of the "IndexNow AI" question. Here is how it maps onto the AI surfaces most marketers care about, as of October 2026:

Google states that a page must be indexed and eligible to be shown in Google Search with a snippet to appear as a supporting link in AI Overviews or AI Mode. Googlebot handles that discovery. An IndexNow ping never reaches it.

Microsoft is the one party that links IndexNow to AI. In a February 2026 Bing Webmaster blog post, it wrote that IndexNow "helps ensure that AI systems reference the most current version of a page when generating answers." That is a first-party assertion from an operator of the protocol. No study sits behind it.

A plausible indirect chain does exist:

1. IndexNow tells Bing a page changed.
2. Bing recrawls and updates its index sooner.
3. Copilot and Azure's Grounding with Bing Search draw on that index.

Each link is documented. The end-to-end effect on what Copilot says is unmeasured. So the honest claim is "it may help Bing's copy of your page stay current", not "it gets you cited in Copilot". Our Copilot citation factors page grades the rest of that picture.

ChatGPT is weaker still. OpenAI says ChatGPT search "sometimes partners with other search providers", which is hedged language with no quantified path through Bing. In OtterlyAI's 2026 experiment with two AI-generated sites, ranking in Bing produced effectively zero ChatGPT citations, even while ChatGPT's crawlers visited, and Copilot cited the same sites thousands of times. That was one pair of sites on a low-stakes topic, so it proves little on its own. It does undercut "get into Bing to get into ChatGPT" as a strategy. The levers that matter for ChatGPT are covered in ChatGPT visibility factors.

Most of what decides AI visibility happens after a crawler fetches your page. IndexNow only influences how soon that fetch happens, and only for the engines that listen.

In your control

• Whether each AI crawler is allowed in robots.txt, per bot. GPTBot governs OpenAI training. OAI-SearchBot governs ChatGPT search.
• Whether your firewall or CDN actually lets those crawlers through. A WAF can return 403 to a bot that robots.txt allows.
• Whether your key facts (prices, product names, definitions) are in the raw HTML, not injected by JavaScript. Most non-Google AI crawlers don't execute JavaScript.
• Whether noindex, nosnippet, max-snippet or data-nosnippet are set by accident.
• Whether you send IndexNow pings when pages genuinely change.

Not in your control

• Whether Bing chooses to index a page after a ping.
• Which queries an engine runs. ChatGPT rewrites prompts and Google fans out across subtopics.
• Whether a retrieved page gets cited.
• What a model knows with retrieval off. That is frozen at its training cutoff, which no ping can move. If you're a new company, whether ChatGPT can know about you depends on this boundary.

Do the checks with documented consequences first. IndexNow comes later because it only helps a page that crawlers can already reach and read.

1. Check crawler access per bot. Read your robots.txt for OAI-SearchBot, PerplexityBot, Claude-SearchBot, Googlebot and bingbot. Then test what your firewall returns to each one. From 15 September 2026, Cloudflare blocks Training and Agent crawlers by default on ad-displaying pages for new domains and existing free-tier customers, while Search stays allowed. The AI Crawler Checker requests a page as each AI crawler and shows which ones get turned away.
2. Check rendering. Fetch your pricing and product pages with JavaScript off. Anything missing from that raw HTML is likely invisible to most AI crawlers.
3. Check index status engine by engine. Open Google Search Console and Bing Webmaster Tools separately. Healthy in one tells you nothing about the other.
4. Set up IndexNow. Host the key file and connect your CMS or deploy pipeline so it pings on real content changes. Our free IndexNow setup guide covers the steps.
5. Keep your XML sitemap accurate. Sitemaps still serve Google, which IndexNow does not. See IndexNow vs XML sitemaps.
6. Watch Bing's AI Performance report. It shows citations from Copilot and Bing AI summaries, plus a sample of the grounding queries the AI actually used. Read it as observation, not proof that pings caused anything.

• Reading a 200 as "indexed". It means received. Check the index itself.
• Expecting a Google effect. Google does not consume IndexNow. Pings do nothing for AI Overviews, AI Mode or Gemini.
• Treating IndexNow as a ChatGPT lever. OpenAI is not an endpoint, and the Bing route into ChatGPT is hedged and unquantified.
• Pinging unchanged pages or bumping dates. Resubmitting pages that didn't change, or refreshing lastmod without a real edit, adds noise. It also makes your own date signals meaningless.
• Dropping the sitemap. IndexNow supplements a sitemap for a handful of engines. It replaces nothing.
• Skipping access checks. A ping cannot help a page your CDN blocks or your JavaScript hides. Access problems remove you silently, and no ping log will show them.