IndexNow vs XML Sitemaps for AI Search Discovery

An XML sitemap is a file on your site that lists the URLs you want crawled, usually with a lastmod date per URL. Crawlers fetch it when they choose to. Nothing in the file tells them to come now. Our XML sitemap definition covers the format in detail.

IndexNow flips the direction. When a page is added, changed or removed, your site or CMS sends that URL to an IndexNow endpoint. You prove you own the site with a key file hosted at the root.

So the sitemap is a standing inventory, and IndexNow is a change notice. Both are discovery tools. Neither is a request to be ranked, cited or quoted. If you want the narrower question of what a sitemap does for AI engines, see whether your XML sitemap helps AI search engines find your pages.

The endpoint list comes from the IndexNow registry as fetched on 22 August 2026. Check it again before you plan around it, because participants can change.

The practical reading: the sitemap covers every engine you care about. IndexNow covers a subset, and the subset leaves out the engine behind AI Overviews, AI Mode and Gemini.

When you submit a URL to IndexNow and get HTTP 200 back, the endpoint is saying one thing: it received your request. The specification guarantees nothing beyond that. It does not promise a crawl, an index update or a ranking.

That matters because many plugins show a green tick for every successful ping. A wall of green ticks is a log of messages sent. It is not evidence that any engine refreshed your page, and it says nothing about AI answers.

If you want to know whether Bing actually holds the current version of a page, check index status in Bing Webmaster Tools. Our take on whether Bing Webmaster Tools is worth setting up for AI search explains what its AI Performance report shows, including the grounding queries Copilot ran, and what it leaves out.

Microsoft's Bing Webmaster blog stated on 10 February 2026 that "by enabling faster discovery of content changes, IndexNow helps ensure that AI systems reference the most current version of a page when generating answers." That is a first-party assertion from a protocol participant. No study backs it, and the protocol's own documentation never mentions AI.

There is a plausible indirect path:

1. IndexNow tells Bing a URL changed.
2. Bing's index refreshes that URL.
3. Microsoft Copilot, Bing AI summaries and Azure's Grounding with Bing Search draw on the Bing index.

Each link is documented on its own. The end-to-end effect on AI answers has never been measured by anyone. Read more on how Copilot grounds answers in Bing.

Two limits follow. First, ChatGPT is not a reliable downstream. OpenAI says ChatGPT search "sometimes" partners with other search providers, and in Otterly's 2026 test of two AI-generated sites, ranking in Bing produced effectively zero ChatGPT citations even with ChatGPT's crawlers visiting.

Second, Google is outside the chain entirely. As of October 2026, Google says a page must be indexed and eligible to show with a snippet to appear as a supporting link in AI Overviews or AI Mode, with no additional technical requirements. IndexNow does not reach Google, so Google's own crawl, helped by your sitemap, is the route. The split between engines is laid out in Bing index vs Google index for AI answers.

Discovery only helps once a crawler can fetch and read the page. The blocks that stop that are where the strongest evidence sits.

• robots.txt, per bot. Retrieval bots are separate tokens: OAI-SearchBot for ChatGPT search, PerplexityBot, Claude-SearchBot, bingbot. Blocking GPTBot affects training only. A sitemap listing a blocked URL does nothing for that bot.
• Firewalls and CDNs. A WAF can return 403 to a crawler that robots.txt allows. Neither a sitemap nor a ping will show you that.
• JavaScript rendering. Vercel's crawler study found that ChatGPT and Claude crawlers fetch JavaScript files but do not execute them. Content that only appears after hydration may be invisible to them, whatever your sitemap says.
• Suppression tags. noindex, nosnippet, max-snippet:0 and data-nosnippet keep content out of AI answers on Google and Bing.

One more trap: lastmod is self-declared. Bumping dates on unchanged pages, or pinging IndexNow for edits that did not happen, games your own signal. No study shows declared freshness earns citations. The AI Crawler Checker requests a page as each AI crawler and shows which ones your firewall turns away.

Use both, for different reasons, and keep expectations honest.

• Always keep an XML sitemap. It is the only one of the two that Google reads. List canonical, indexable URLs only, and set lastmod to the date content actually changed.
• Add IndexNow if your CMS or CDN supports it at no cost. Treat it as Bing-side hygiene that may speed up Bing, Yandex and the other listed endpoints. Do not budget for it as an AI tactic.
• Ping only real changes. New pages, edited prices, removed products. Not template tweaks or date bumps.
• Fix access first. Check per-bot robots.txt rules, firewall responses and server-rendered HTML before worrying about discovery speed.
• Verify, do not assume. Use Bing Webmaster Tools and Google Search Console separately. A healthy index on one engine tells you nothing about the other.

For the full breakdown of the protocol, see IndexNow and AI search: what it does and doesn't do.

Does IndexNow help me appear in Google AI Overviews or AI Mode? No. Google is not in the IndexNow registry as of the August 2026 fetch, so your pings never reach it. Google says a page needs to be indexed and eligible to show with a snippet to appear as a supporting link in AI Overviews or AI Mode. Google finds your pages through its own crawl, and an accurate sitemap helps that discovery. No ping changes Google's process.

Will a faster Bing index get me cited by Copilot? It may get your current page into the index Copilot grounds on, which is a precondition. It does not decide whether Copilot retrieves or cites you for a given question. Microsoft asserts IndexNow helps AI systems reference current pages, but no study measures that effect. Treat a fresh Bing index as eligibility, not a citation, and check the AI Performance report in Bing Webmaster Tools to see what actually happened.

Is there any downside to running IndexNow? Very little, if you use it honestly. It costs a key file and a request per change, and many CMS and CDN plugins handle it automatically. The risk is self-deception: reading successful pings as proof of indexing or AI visibility. A 200 response only confirms receipt. The other risk is pinging unchanged pages with fresh dates, which muddies your own signals without any evidence of benefit.

Should my sitemap's lastmod dates change every time I republish? Only when the content meaningfully changes. The lastmod field is declared by you, so engines have no way to verify it except by recrawling. Studies linking recent update dates to AI citations have no control group of uncited pages, so they cannot show freshness causes citation. Keep dates accurate and consistent with the visible page date and any schema dateModified value. Consistency is the goal, not a constantly new date.