Check this page with an assistantOpens a chat asking it to summarise this article and name the evidence behind each claim.
Claude opens with the prompt on your clipboard: Anthropic does not support prefilled prompts on the web, and we would rather copy it than ship a button that drops it.
Push Instead of Wait
Sitemaps are a pull mechanism: you list URLs and wait for a crawler to come and check. IndexNow inverts it. You notify an endpoint that a URL changed, and participating engines are told within seconds rather than whenever crawling next reaches you.
The setup is genuinely small. You host a key file at your root to prove you control the domain, then send URLs to a participating endpoint when they change. Submitting to any one participant propagates to the others, so there is one integration rather than five, and most major platforms have a plugin or built-in support.
The reason to understand it properly rather than just enabling a plugin is that its value depends entirely on which engines participate, and that is the part write-ups consistently get wrong or leave vague.
Google Declined, and Said So
Google tested IndexNow from 2021 and did not adopt it. It runs its own Indexing API, which is restricted to a narrow set of content types rather than open for general URL submission. There is no configuration in which IndexNow accelerates Google indexing.
This matters because IndexNow is frequently sold as instant indexing without naming the engines, and buyers reasonably assume the engine they care about is included. If someone offers to speed up your Google indexing via IndexNow, they are either confused or hoping you are.
For Google, the honest tools are the ordinary ones: a submitted sitemap, internal links from crawled pages, and URL Inspection for a single urgent page. That is the whole toolkit, and the sequence for a site that is not being discovered at all is in the first 90 days.
The Reason It Is Still Worth Doing
Bing's index does not only serve Bing. It underpins search behaviour in other products, including ChatGPT, which means getting a page into that index quickly has a payoff that has nothing to do with Bing's share of ordinary search traffic.
That reframes the calculation. Judged on Bing traffic alone, an afternoon of integration is marginal for most small sites. Judged as the fastest route into an index that feeds an assistant surface, it is one of the cheaper things available in the whole AI visibility category, and unlike most of that category it is a documented mechanism rather than an inference.
It also fits the general principle that being retrievable precedes being cited. A page that is not in an index cannot be quoted by anything reading from that index, which is the point made throughout Bing SEO for ChatGPT and the AI search visibility playbook.
Using It Without Misusing It
The protocol assumes you notify on genuine change. Submitting unchanged URLs wastes quota and degrades the reliability of your signals, which is the one way to make this actively unhelpful.
| Situation | Submit? | Why |
|---|---|---|
| New page published | Yes | The core use case |
| Substantial content update | Yes | Prices, availability, corrected facts |
| Page removed or redirected | Yes | Change of status is a change worth reporting |
| Typo fix or date bump | No | Nothing meaningful changed |
| Entire sitemap, on a schedule | No | The most common plugin misuse; teaches the engine to ignore you |
| Inventory that changes hourly | Selectively | Batch meaningful changes rather than every stock tick |
The bottom row matters for ecommerce specifically, where availability changes constantly and a naive integration will submit thousands of URLs daily. Batch the changes that a searcher would care about and leave the rest, which is the same judgement applied to feed updates in Merchant Center.
Where It Sits Among the Discovery Tools
IndexNow is an accelerant, not a substitute. It tells engines a URL changed; it does not make a page worth indexing, and a page that would not have been indexed anyway is not helped by faster notification.
The sequence stays the same. Sitemaps declare what exists, internal links make pages reachable and signal importance, and IndexNow shortens the delay for the engines that accept it. A site with a discovery problem needs the first two, and adding the third to a site nothing links to changes nothing.
Be equally clear about what fast indexing is worth. Getting a page indexed within minutes is valuable for news, product availability, and anything time-sensitive, and close to irrelevant for an evergreen guide that will be assessed over months. Matching the tool to the content type prevents this becoming another checkbox, which is the general framing in how Google Search works.
Questions About IndexNow
- What is IndexNow?
An open protocol for telling search engines that a URL has changed, rather than waiting for them to discover it. You publish a key file, then send a URL to any participating engine's endpoint, and it forwards the notification to the others within seconds. It is a push mechanism where sitemaps are a pull one.
- Does Google support IndexNow?
No. Google tested it from 2021 and publicly declined to adopt it. Google runs its own Indexing API instead, which is restricted to a narrow set of content types rather than being available for general URLs. Anyone telling you IndexNow speeds up Google indexing is wrong.
- Which engines actually use it?
Bing, Yandex, Naver, Seznam, and Yep are the participating engines. Submitting to any one of their endpoints propagates to the others, so you only need to integrate once. That list is smaller than Google but it includes the index that matters most for reasons unrelated to search traffic.
- Why bother if Google is not included?
Because Bing's index feeds surfaces beyond Bing itself, including ChatGPT's search behaviour. Getting new and updated pages into that index quickly has a payoff that has very little to do with Bing's own traffic share, which is the argument most write-ups of IndexNow miss entirely.
- Can submitting too many URLs cause problems?
Submitting URLs that have not changed is the main misuse, and it wastes your quota while teaching the receiving engine that your signals are unreliable. Submit on genuine publication or meaningful update, not on a schedule, and never submit your entire sitemap repeatedly because a plugin offers to.
