Obility Editorial · · 4 min read
IndexNow is a change notice, not a ranking signal
IndexNow keeps turning up in AI search checklists, often with a promise that it gets your pages into ChatGPT or Copilot within minutes. The protocol itself promises much less. Its own documentation describes a simple ping: your site tells participating search engines that a URL was added, updated or deleted, so they can prioritise crawling it instead of waiting to find the change on a routine crawl, which it says can take days to weeks.
One submission is shared across every engine in the scheme. The documentation is careful about what a successful request means: an HTTP 200 response only indicates that the search engine has received your URL. The protocol’s FAQ adds that a submission does not guarantee indexing, and that each engine decides for itself whether to index the page. Being crawled sooner is useful. It is a long way from being chosen as the source an answer cites.
It reaches Copilot directly and ChatGPT only by a side door
Who receives the ping decides what it can affect. The protocol publishes its list of participating endpoints, and when we read it on 10 November 2026 it named Microsoft Bing, Yandex, Seznam, Naver, Yep, the Internet Archive and Amazon’s crawler. Google is not on it. Nor are OpenAI, Anthropic or Perplexity.
Copilot is the clear case. Microsoft’s Bing Webmaster Guidelines say Bing and Copilot rely on the same core crawling, indexing and ranking foundation, list IndexNow first among the ways to help Bing discover URLs, and say timely notifications reduce outdated or incorrect URL references in Copilot responses and grounding results.
ChatGPT is indirect at best. OpenAI’s crawler documentation describes OAI-SearchBot and says nothing about IndexNow. Its help page says ChatGPT search sometimes partners with other search providers and points readers to Microsoft’s privacy statement, so a fresher Bing index may help some ChatGPT searches, but OpenAI does not say which provider handles which query. Google has its own route: its documentation says crawling can take a few days to a few weeks, offers sitemaps and a request indexing button with a quota, and says requesting a crawl does not guarantee inclusion.
Its value shows up when a fact changes
For a page that already exists and rarely changes, IndexNow does little. The engines will find it. Where it earns its place is the gap between changing a fact and an engine noticing, because that gap is when an answer quotes the old version.
Take an illustrative case. A software company renames its plans and drops its free tier on a Monday. Five URLs change: the pricing page, two comparison pages, a feature page, and the old free plan page, which now redirects. Without a notice, Bing picks each change up whenever it next crawls that URL, and until then Copilot can describe a free tier that no longer exists. With IndexNow, the CMS sends all five on publish. The protocol’s FAQ explicitly asks for redirected and deleted URLs to be submitted too, so engines drop the old address instead of continuing to reference it.
The same logic applies to a product launch, a discontinued product, a new integration, or a correction to a page that an answer has been misquoting. Price and availability changes are named in the protocol’s own list of cases worth a notification.
Turn it on once, and send only real changes
Setup is rarely a project. The protocol’s FAQ lists native or plugin support in WordPress, Shopify, Wix, Drupal, Joomla and several other systems, and names Cloudflare as a CDN with built-in support. A manual setup needs a key file on your domain and a request to one endpoint.
Two details catch teams out. Each subdomain is a separate host with its own key file, so a help centre or documentation site on its own subdomain is not covered by the main site’s setup, and those pages often hold exactly the facts buyers ask about. And the protocol asks for meaningful changes only, not every cosmetic edit, with at least five minutes between resubmissions of the same URL. Pair it with an XML sitemap whose lastmod values are true; Bing’s July 2025 guidance on sitemaps for AI search says lastmod helps it decide what to recrawl, and warns against setting it to the time the sitemap was generated.
Check the answer, not the ping
A 200 from the endpoint proves only delivery, so judge IndexNow in three steps. First, did the crawler come back for the changed URLs? Obility’s Agent Analytics keeps crawler requests separate from citations and visits, because a request shows a page was fetched, not that an answer used it, and a user agent string is a signal rather than verified identity. Second, does Bing Webmaster Tools show the new version indexed? Third, did the answer change? Answer Engine Insights keeps the full answer and its cited sources for each tracked question, so you can see whether Copilot now states the new plan names, and in which source it found them.
That third step is also where IndexNow’s limit shows. If the stale fact sits on a review site or a partner’s page, notifying engines about your own URLs changes nothing; that page has to be corrected by whoever owns it. And if the answer never cited you before the change, faster crawling will not make it start. Bing’s own sitemap guidance says no tool can guarantee when or how your content will appear in AI generated results. IndexNow shortens the wait for a change you have made. Whether the engine picks your page still depends on what the page says.