IndexNow: how instant URL submission actually works
IndexNow lets you ping search engines the moment a page changes, instead of waiting for a crawl. Here is how it works and who actually supports it.
Most search engines find your new or updated pages by crawling: following links, rechecking your sitemap, or revisiting URLs on their own schedule. IndexNow skips that wait. It is a small protocol that lets you tell participating search engines the instant a URL changes, so they can queue it for a crawl right away instead of discovering it later.
What IndexNow actually does
IndexNow is an open protocol, not a company or a product. You host a key file on your domain to prove ownership, then send a list of changed URLs (new, updated, or deleted) to an IndexNow endpoint with a single HTTP request. Because participating engines share submissions with each other, one call can reach more than one search engine at once. It costs nothing to use and there is no submission cap for reasonable, real-time updates.
It is worth being precise about what it does not do. IndexNow speeds up discovery and crawl scheduling. It does not guarantee indexing, and it has no effect on ranking. A submitted URL still goes through the same quality and relevance checks as any other page.
Who actually supports it
Microsoft and Yandex built IndexNow and both consume submissions through it, which means Bing gets the benefit directly. A handful of smaller engines, including Seznam.cz and Naver, have also adopted it. As of this writing, Google does not consume IndexNow submissions; it still relies on its own crawl scheduling, sitemaps, and the Search Console URL Inspection tool for fast re-crawl requests.
That matters for AI search too. Bing's index feeds Microsoft Copilot, so a faster Bing crawl can plausibly help content show up there sooner. But there is no public documentation from OpenAI, Perplexity, or Anthropic confirming that their crawlers consume IndexNow submissions or prioritize pages because of them. Treat any AI-engine benefit as a secondary, unproven effect of getting into Bing's index faster, not a direct channel to those engines.
Setting it up
- Generate a key: a random alphanumeric string at least 8 characters long.
- Host the key as a text file at your domain root, named after the key itself, so the endpoint can verify you control the site.
- Submit URLs with a GET or POST request to an IndexNow endpoint, listing the key, key location, and the changed URLs.
- Automate it. Most sites do this through a CMS plugin, a Cloudflare integration, or a hook in the publishing pipeline, not by hand.
If you run WordPress, several SEO plugins added IndexNow support after Bing pushed for adoption. Cloudflare offers a one-click integration that submits URLs automatically when content changes on domains it proxies. For anything custom, the request format is simple enough to add to whatever process already publishes or updates pages.
When it is worth the effort
- Sites that publish or update frequently, like news, listings, or inventory-driven ecommerce, where stale pages cost clicks or sales.
- Time-sensitive content where a delay of days genuinely matters.
- Site migrations, where you want redirects and new URLs picked up faster instead of trickling in over weeks.
- Large catalogs where sitemap-only discovery is slow to reach every changed page.
For a small site that updates a few times a month and is already crawled promptly, IndexNow adds setup work for a benefit you likely will not notice. It is not a substitute for a clean sitemap, a crawlable link structure, or fixing whatever is actually keeping pages out of the index.
Mistakes to avoid
- Submitting URLs that are blocked by robots.txt or marked noindex; the engines will just ignore them.
- Submitting non-canonical duplicates instead of the URL you actually want indexed.
- Treating submission volume as a ranking lever. It is a discovery mechanism, nothing more.
- Forgetting to submit deletions, which leaves stale URLs lingering in the index longer than necessary.
IndexNow is a low-cost way to shorten the gap between publishing and crawling on Bing and a few smaller engines. It will not move Google, and any effect on AI answer engines is indirect at best. If you update content often and rely on Bing-derived traffic or Copilot visibility, set it up once through your CMS or Cloudflare and let it run in the background. If neither applies, spend the time on your sitemap and internal links instead.