CrawlCheck

Guides · 2026-10-02 · By · 3 views

IndexNow: which engines use it and how to check it worked

IndexNow lets a site tell search engines a URL changed instead of waiting to be recrawled. One submission reaches every participating engine. Which engines those are, the key file, the response codes, and what a 200 does and does not mean.

IndexNow is an open protocol for telling search engines that URLs were added, changed or deleted. A site hosts a key in a text file at its root and sends URLs with that key to an IndexNow endpoint; participating engines share submissions with each other, so one request reaches all of them. The registry at indexnow.org lists Bing, Yandex, Seznam, Naver, Yep, the Internet Archive and Amazonbot. Google does not participate. A 200 or 202 response means the submission was received, not that any URL was crawled or indexed.

Check your own site free

About a minute. First scan free with your email, nothing installed.

Across every full scan CrawlCheck has run, 7.4% of sites published a sitemap in which no entry carries a modification date at all, leaving crawlers no change signal from the sitemap either.

Search engines learn that a page changed in one of two ways: they recrawl it on their own schedule, or the site tells them. Sitemaps with lastmod are the passive version of telling, and only when the dates are accurate, as our own 103-page lastmod mistake showed. IndexNow is the active one: when a URL changes, the site sends it to an endpoint, and the engines that participate can fetch it soon after rather than whenever they next pass by.

One IndexNow submission, shared with every participating engineYOUR SITEa page changesyou POST its URL + key/<key>.txtproves you own the hostONE ENDPOINTapi.indexnow.orgor any engine's endpointchecks key fileSHARED WITHBingYandexSeznamNaverYepInternet ArchiveAmazonbotGoogle is not a participant. Use the sitemap and lastmod for Google.

How the protocol works #

Generate a key, a string of 8 to 128 letters, digits and dashes, and publish it as a text file at the root of the host, for example https://example.com/key.txt, containing the key and nothing else. Then submit changed URLs. A single URL can go as a GET request with url and key parameters; batches of up to 10,000 URLs go as a POST with a JSON body:

POST https://api.indexnow.org/indexnow
Content-Type: application/json; charset=utf-8

{"host":"example.com","key":"<key>","keyLocation":"https://example.com/<key>.txt",
 "urlList":["https://example.com/guides/new-page","https://example.com/guides"]}

The receiving engine fetches the key file to confirm the submitter controls the host, then accepts the URLs. Engines share submissions, so posting to one endpoint is enough; posting the same URLs to every engine separately only adds load.

Who receives a submission #

The protocol's own registry, indexnow.org/searchengines.json, lists the participants. As read for this guide it named Bing, Yandex, Seznam, Naver, Yep, the Internet Archive and Amazonbot. Google is not a participant, so for Google the sitemap and accurate lastmod values remain the mechanism, covered in the sitemap audit guide. Bing's participation matters beyond Bing itself, because some AI answer products have drawn on Bing's index.

Reading the response #

StatusMeaningWhat to do
200 OKURLs receivednothing; this is not a crawl or index confirmation
202 Acceptedreceived, key validation pendingnothing; the key file is checked later
400 Bad Requestmalformed requestfix the JSON or parameters
403 Forbiddenkey not valid: file missing, or its content does not matchcheck the key file URL returns the key as plain text
422 UnprocessableURLs do not belong to the host, or key and host disagreesubmit only URLs on the host named in the body
429 Too Many Requestssubmitting too oftenbatch changes and back off

The protocol says a 4xx response must be corrected before retrying, while a 2xx or 5xx lets the notifier move on. Treat 200 as "delivered", never as "indexed". Whether a submitted URL is crawled, and whether it is indexed, is still each engine's decision.

When to submit #

Submit when a URL is created, when its content meaningfully changes, and when it is deleted or redirected, so the engine can drop it. Do not resubmit unchanged URLs on a timer; engines can deprioritise hosts that submit noise. The practical approach is to record what each page looked like when you last submitted it and submit only the pages that changed since, plus the index page that lists them. A new page is then submitted once, and an unchanged page never again.

Checking that it is working #

Three checks cover most failures. Fetch the key file from outside your network and confirm it returns 200, text/plain, and exactly the key, with no HTML wrapper; a CMS that routes unknown paths to a 404 page answered with status 200 breaks validation silently. Log every submission's status code and URL count rather than firing and forgetting. And in Bing Webmaster Tools, the IndexNow report shows the URLs Bing received from your host, which is the only first-party confirmation available. Many plugins and CDNs offer IndexNow as a switch; if two of them are enabled, the same URLs are submitted twice with two different keys.

Deletions and redirects #

Submitting removed URLs is as useful as submitting new ones. When a page is deleted, make it return 404 or 410 first, then submit the URL; the engine fetches it, sees the status and drops it, instead of keeping the page in its index until its next scheduled crawl. When a page moves, put the redirect in place, then submit both the old and the new URL. Submitting a URL that still returns 200 with the old content achieves nothing, because the engine fetches what you told it about and sees no change.

The same applies to updates. Submit after the change is live and cached copies are purged, not when the edit is saved in the CMS. A submission that arrives before the CDN serves the new version invites the engine to fetch the old one, and the next submission for the same URL may be treated as noise.

Choosing an endpoint #

Any participating engine's endpoint, or the shared api.indexnow.org, delivers to all participants, so pick one and stay with it. Submitting the same batch to several endpoints multiplies requests for no benefit and makes rate limits more likely. Keep one key per host, and if a plugin already submits for you, do not add a second integration with its own key.

On a hosted platform #

Whether you can use IndexNow at all depends on where the site is hosted, because the key file has to be served from your own domain. What each common platform does:

PlatformWhat happensWhat you do
WordPressMicrosoft Bing's IndexNow plugin hosts the key file and submits on publish, update and delete.Install the plugin; nothing else
WixBuilt in since September 2023. Wix submits changed pages itself.Nothing; it is on
ShopifyBuilt in since 2025. Shopify submits store URLs itself.Nothing; it is on
Cloudflare (any CMS)Crawler Hints, one switch in the Cache settings, submits for you. It only works when traffic passes through Cloudflare's proxy; a DNS-only record is never seen.Turn on Crawler Hints, keep the record proxied
GhostNo built-in support. The open request is on Ghost's own forum.Put the site behind Cloudflare with Crawler Hints, or call the API from a publish webhook (the key file must still answer at the root)
Substack, MediumNo way to add it: you cannot host the key file or run code on publish.Nothing to set up; the platform decides how it tells engines

Whichever route applies, the check is the same: Bing Webmaster Tools lists the URLs it received through IndexNow, so a platform that says it submits can be confirmed from there.

What IndexNow does not do #

It does not make a page indexable that is blocked by robots.txt, marked noindex, or canonicalised elsewhere; the engine will fetch it and reach the same conclusion it would have reached on its own. It does not influence ranking. And it says nothing about AI crawlers that are not on the participant list. Its value is shortening the delay between publishing and being fetched, for the engines that take part. The status-code side of what a crawler then receives is in what a crawler actually gets.

Share of scanned sites with each finding in this articleSitemap has no lastmod dates7.4%Share of scanned sites with eachfinding in this articleSitemap has no lastmod dates7.4%
Read live from the same counters the dataset page uses, at the moment this page was served. Bars are scaled to the largest value shown, not to 100%.

Share this finding:LinkedInXEmailFollow Emmanuel on LinkedIn

Related findings

The main product

Found this on your own site? We fix it for $100.

Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after.

Free browser extension

Check this on any site you open, without leaving the page.

CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account.

Write for the library

Measured something yourself? Submit an article.

Send your finding, the data and the method. A person reads every submission and replies by email; accepted articles are published under your name with a link to your study. Free to submit. Articles are accepted on merit; no one can pay to have one published.

Submit an article

How it works · a reply within about a week

Spotted a mistake or a bug on this page? Report an error. Confirmed errors are fixed and logged on the corrections page.

Comments

Comments are read before they appear. Nothing is published automatically, and no account is needed. An AI agent with a published signing key can post without the queue: it signs the request and the signature is checked against its own domain (how). Those appear at once, marked verified.

Writing about this? Facts, live figures and marks — every number on that page is dated and traceable to a scan.

All guides · The dataset · How the dataset works