IndexNow checker: verify your key and submissions

How to check that IndexNow works: the key file, a submission response, what each status code means and where to confirm the crawl.

·4 min read

An IndexNow checker verifies two things: that your key file is reachable at the right URL and that a submitted URL gets a successful response from the endpoint. If those two pass, IndexNow is working. If either fails, nothing you submit reaches Bing, Yandex, Naver, Seznam or Yep.

IndexNow is a notification protocol, not an indexing guarantee. A correct setup means the engine received the URL. It does not mean the page was crawled or indexed.

Check the key file first

IndexNow proves ownership with a text file hosted on the domain.

  1. Generate a key. It must be 8 to 128 characters, using letters, numbers and dashes.
  2. Create a file named <key>.txt at the root of the site, so it resolves at https://example.com/<key>.txt.
  3. Put the key itself in the file, with no other text.
  4. Request the URL in a browser. It must return a 200 and the exact key.

A file that returns a 404, an HTML page or the key inside a JSON wrapper fails. So does a key file on www when you submit URLs for the apex domain. The host in the key URL must match the host in the submitted URLs.

Submit one URL and read the response

The simplest request is a GET with the URL and key as query parameters.

curl "https://api.indexnow.org/indexnow?url=https://example.com/new-page&key=YOUR_KEY"

A bulk request uses POST with a JSON body.

curl -X POST https://api.indexnow.org/indexnow \
  -H "Content-Type: application/json" \
  -d '{
    "host": "example.com",
    "key": "YOUR_KEY",
    "keyLocation": "https://example.com/YOUR_KEY.txt",
    "urlList": [
      "https://example.com/new-page",
      "https://example.com/updated-page"
    ]
  }'

Read the status code before the body. IndexNow returns very little prose.

Status Meaning Fix
200 URL accepted Nothing
202 Accepted, key validation pending Wait, then check the key file
400 Bad request Check the URL format and required fields
403 Key not valid Key file missing, wrong contents or wrong host
422 URL does not belong to the host, or the key does not match Check the host and the key
429 Too many requests Back off and retry later
5xx Endpoint error Retry with the same URL later

A 200 or 202 means the engine received the notification. It does not mean the page will be crawled today.

Confirm the crawl, not just the submission

Three places show what happened after the request.

  • Bing Webmaster Tools. The URL submission report lists submitted URLs and their status. It is the closest thing to a receipt.
  • Server logs. Look for a request from Bingbot or another participating crawler after the submission time. The user agent and the timestamp tell you whether the notification worked.
  • Bing's index itself. Search for the URL or run a site: query. This is the only place that shows whether the page was actually indexed.

Our IndexNow checker covers the setup half: it fetches the key file, submits up to 1,000 URLs on that host and reports the endpoint response plus the exact URL list that was sent. With no key in hand it uses a key for the site in your workspace and shows the file to serve. It does not report whether the URL is indexed, because IndexNow never returns that. A 200 from this tool tells you the protocol works; the crawl still has to be confirmed in Bing or the logs.

Why Google still does not see the page

IndexNow does not include Google. Submitting a URL to IndexNow changes nothing about Google's crawl, no matter how many times you send it.

For Google, use the paths that actually work:

  1. Internal links. A link from a page Google already crawls is the strongest discovery signal.
  2. A sitemap. Keep it current and submit it in Search Console.
  3. URL Inspection. Request indexing for a URL you own, within the daily quota.
  4. Search Console's Page indexing report. Check whether the page is discovered, crawled or excluded.

If a page is missing from Google, how to get Google to index your site is the right guide. IndexNow is the fast lane for everyone else.

Setup notes for common hosts

  • Cloudflare. A Worker or a Pages function can send the POST on publish. Do not send every URL on every deploy; send only URLs that changed.
  • WordPress. Several plugins submit on publish and update. Check that the key file is served from the site root, not from a plugin directory.
  • Static sites. Generate the key file at build time and include it in the output. Submit the changed URLs from the same pipeline.
  • Multi-host sites. Each host needs its own key file. A key for example.com does not authorize shop.example.com.

Keep the key out of public JavaScript and out of client-side bundles. The key file is public by design; the ability to submit URLs is not.

Verify the setup once, then automate

Our IndexNow checker verifies the key file and the endpoint response, so you can separate a broken setup from a slow crawl. Run it once before you automate submissions, then again after any host or DNS change. If you are new to the protocol, start with what IndexNow is; if the sitemap is the problem, use the sitemap checker.

Related guidesFrom the same topic, then the newest guides.