serkankaya.
Türkçe sürüm
Let’s work together ↗

What Is IndexNow? Notify Bing and Yandex of Changes Instantly

What is IndexNow, how does it work, and does Google support it? API key, single and bulk URL submission, response codes and automated setup, explained.

What is IndexNow? The short answer: IndexNow is an open, free protocol that tells search engines, with a single HTTP request (for example to api.indexnow.org), when a URL on your site is added, updated or deleted. Participating search engines, led by Bing and Yandex, share the notification with each other. Google is not one of the participants.

In this post I explain how IndexNow works, how to create the API key, single and bulk URL submission, the response codes, and how to connect notifications to your publishing process. If you want to see how I approach technical SEO in general, take a look at my SEO services page.

Why does IndexNow exist and what problem does it solve?

IndexNow lets the site owner report a change directly instead of search engines crawling based on guesses. In the classic model, a search engine bot visits your site at intervals and tries to guess whether a page has changed. According to IndexNow’s FAQ, this process can take days or even weeks.[2]

This model has two costs. The first is delay: a new product, an updated price or a removed page shows up late in search results. The second is waste: the bot also recrawls pages that never changed. That puts unnecessary load on both your server and the search engine.

IndexNow reverses this relationship. Instead of “wait and crawl”, it sets up a “this changed, come and look” model. The search engine still crawls the page itself; the notification only tells it where and when to look.

Page changes Site sends notification Search engine verifies Page is recrawled
The IndexNow flow: the change is reported immediately, the search engine verifies the key and crawls the page on its own schedule.

Which search engines does IndexNow work with?

IndexNow’s official list of participants includes Bing, Yandex, Seznam, Naver, Yep, the Internet Archive and Amazonbot.[3] The list is published on the protocol’s own site as a machine-readable JSON file and is updated as participants join.

The most practical part of the protocol is the sharing rule. According to the documentation, participating search engines agree to share the URLs they receive with the other participants.[1] So a URL you send to Bing’s endpoint also reaches Yandex and the other participants. You do not need to send the same notification to each search engine separately.

Two details matter from a Turkish market perspective. First, Yandex is a search engine used in Turkey and one of IndexNow’s founding participants. Second, Microsoft Bing’s index also feeds Microsoft’s own AI-powered search experiences. So fast notification to Bing matters not only for classic Bing results but also for freshness in AI answers. I covered this connection in a broader context in my post on what GEO is.

Does Google support IndexNow?

Short answer

Does Google support IndexNow?

No. Google is not on IndexNow’s official list of participants, so IndexNow notifications do not directly affect Google’s crawling. On the Google side, you should keep using sitemap.xml, accurate lastmod values and the URL Inspection tool in Search Console to announce new and changed pages.

Google’s own documentation also recommends sitemaps for discovery and notes that they are especially useful for large or frequently updated sites.[5] In practice this means running two channels together: sitemaps for Google, IndexNow for the participating search engines.

How does IndexNow work?

IndexNow consists of three parts: an API key, a key file published on the site and an endpoint where changed URLs are sent. An endpoint is the specific address where an API accepts requests. On the first notification, the search engine reads the key file and uses it to verify that the site really belongs to you.[1]

API key and key file

An IndexNow key is at least 8 and at most 128 characters long. It may only contain lowercase letters, uppercase letters, numbers and hyphens.[1] The FAQ recommends using a GUID or UUID generator to create the key.[2]

After generating the key, you create a text file with the same name. For example, if your key is a1b2c3d4e5f6, the file is named a1b2c3d4e5f6.txt and contains only the key itself. The file must be saved with UTF-8 encoding and be reachable from the site root.

The documentation also defines a second option: placing the file in a folder outside the root and declaring its location with the keyLocation parameter. In that case the key is valid only for URLs under that folder. The documentation clearly recommends the root directory as the stronger choice.[1]

Single URL and bulk URL submission

A GET request is enough to report a single URL:

curl "https://api.indexnow.org/indexnow?url=https%3A%2F%2Fexample.com%2Fproduct%2Fnew%2F&key=a1b2c3d4e5f6"

The submitted URL must be encoded according to RFC 3986; that is, : becomes %3A and / becomes %2F.[2] For multiple URLs, you use a POST request with a JSON body:

curl -X POST "https://api.indexnow.org/indexnow" \
  -H "Content-Type: application/json; charset=utf-8" \
  -d '{
    "host": "example.com",
    "key": "a1b2c3d4e5f6",
    "urlList": [
      "https://example.com/product/new/",
      "https://example.com/category/winter-collection/"
    ]
  }'

According to the documentation, a single POST request can carry up to 10,000 URLs.[1] Requests above that limit may return an error.

What do the response codes mean?

The response code tells you whether the request was received; it does not tell you whether the page was indexed. The codes in the documentation are:[1]

CodeMeaningWhat to do
200 OKURL received successfullyNothing; just log it
202 AcceptedURL received, key validation pendingNormal on the first submission; check the key file is reachable
400 Bad RequestInvalid formatCheck the JSON structure and URL encoding
403 ForbiddenKey invalid or not found in the fileCheck the file name, contents and accessibility
422 Unprocessable EntityURL does not belong to the host or the key does not match the schemaMatch the host field to the URLs’ domain
429 Too Many RequestsToo many requestsReduce submission frequency

How do you set up IndexNow?

Short answer

How do you set up IndexNow?

To set up IndexNow, you generate an API key, upload it to the site root as a .txt file with the same name, and send changed URLs to a search engine’s /indexnow endpoint. On platforms such as WordPress, Shopify and Cloudflare, these steps can be handled automatically by a built-in integration.

  1. First check whether your CMS, plugin or CDN already has a built-in integration.
  2. Generate a key of 8-128 characters.
  3. Upload a {key}.txt file containing the key to the site root.
  4. Check that the file opens in a browser and shows only the key.
  5. Send changed URLs to the API endpoint and log the response code.

IndexNow’s FAQ recommends starting by checking your CMS. The list includes platforms such as WordPress, Shopify, Wix, Joomla!, Drupal, PrestaShop and OpenCart, which support IndexNow natively or through plugins.[2] If an integration exists, you may not even need to deal with the key file.

If you use Cloudflare: Crawler Hints

Cloudflare supports IndexNow directly through a feature called Crawler Hints. According to Cloudflare’s documentation, the feature infers from a cache MISS that content has probably changed and reports this to IndexNow.[4] The feature is available on all plans, including the free plan, and is turned on with a single setting in the dashboard.

There is one point to watch here. Crawler Hints is a site-wide setting. On pages you do not want indexed, you need to add a noindex tag or an X-Robots-Tag: noindex header separately.[4]

In your own software: connect it to the release process

If you run a custom-built site or a static site generator, the most robust place is the deploy process. The logic is simple: after deploy, find the URLs that changed in this release and send them in a single POST request. Because I come from a software development background, I prefer to set up these notifications as a step in the release pipeline rather than as a separate manual task.

  1. List the changed URLs

    Use git diff, the CMS publishing log or a sitemap comparison to identify URLs added, changed and deleted in this release.

  2. Filter for meaningful changes

    Send content, price, stock or redirect changes. Leave out pages where only the design or footer changed.

  3. Submit in bulk

    Split the list into chunks of 10,000 URLs and send each chunk in a single POST request to the api.indexnow.org endpoint.

  4. Log the response

    Record the time, URL count and response code of every submission. On 403 and 422 errors, raise a warning without breaking the deploy.

When should you use IndexNow, and when is it unnecessary?

IndexNow is most useful on sites whose content changes often and where it matters that changes are reflected quickly. According to the FAQ, typical cases to report are new content, updated content, price and stock changes, user-generated content and deleted pages.[2] Deleted or redirected URLs are included too; reporting pages that return 404, 410 or 301 helps old results get cleaned up faster.

Report

  • Newly published product, post or service page
  • Product whose price, stock or promotion changed
  • URL that was deleted or moved with a 301
  • All URLs after a site migration or redesign

Do not report

  • Pages where only the design or footer changed
  • The same URL already submitted in the last 5 minutes
  • Old pages that changed before IndexNow was set up
  • Pages with noindex or blocked by robots.txt
IndexNow's FAQ recommends waiting at least 5 minutes before resubmitting the same URL on frequently updated pages and using sitemaps for past changes.

The reason for this distinction is crawl quota. According to the FAQ, every URL submitted through IndexNow counts toward the site’s crawl quota.[2] Unnecessary notifications mean spending that quota on unimportant pages. This matters even more during campaign periods; in my Black Friday SEO post I explained why campaign pages should stay on a permanent URL.

What is the difference between IndexNow and a sitemap?

IndexNow reports a change instantly, while a sitemap presents the site’s full inventory. Neither replaces the other. IndexNow’s own FAQ also recommends using an XML sitemap for the full inventory and long-term discovery, and IndexNow for priority and frequently changing pages.[2]

IndexNowsitemap.xml
What it doesReports the change instantly (push)Presents the URL inventory (pull)
ScopeOnly changed URLsAll indexable URLs
GoogleNot supportedSupported
Past changesNot suitableSuitable with lastmod

Does IndexNow help SEO?

IndexNow is not a ranking signal; its contribution is that changes get crawled earlier by participating search engines. The FAQ states clearly that a submission does not guarantee immediate indexing and that the search engine evaluates the URL based on its own crawl quota, scheduling and quality signals.[2]

So it is more accurate to see IndexNow as a communication channel than as a promise of “get indexed fast”. It announces an update to a good page faster. It will not get a weak, duplicate or wrongly canonicalised page indexed. The role of robots.txt rules on the crawling side is separate; reporting a page that bots are not allowed to access makes no sense. I covered this topic in detail in my post on AI crawlers and robots.txt.

IndexNow setup checklist0/8

Summary and next step

IndexNow is a free protocol that reports changed URLs to Bing, Yandex and the other participating search engines with a single request. Setup amounts to a key file and an API request. The real value lies in connecting notifications to the release process and sending only meaningful changes. On the Google side, sitemaps and Search Console stay in place.

As a next step, check whether your CMS or CDN already supports IndexNow. If it does, simply turn it on; if not, add the four-step flow above to your release process. Then watch the crawl data in Bing Webmaster Tools for a few weeks and observe the effect on your own site.

Key terms

IndexNow
IndexNow is an open protocol that reports to participating search engines, via an HTTP request, when a URL on a website is added, updated or deleted. A notification sent to one search engine is also shared with the other participants in the protocol.
IndexNow key
An IndexNow key is an 8-128 character string of letters, numbers and hyphens that a site owner generates to prove they are authorised to submit URLs. The key also sits inside a .txt file of the same name on the site, and the search engine reads that file to verify it.
Indexing
Indexing is the process in which a search engine processes the content of a crawled page and adds it to its database so it can appear in search results. Not every crawled page is indexed; the search engine decides based on quality, duplicate content and canonical signals.
Crawler Hints
Crawler Hints is a Cloudflare feature that infers from cache signals that a page has probably changed and reports this to search engines through IndexNow. It is turned on with a single setting in the Cloudflare dashboard and applies to the whole site.

Frequently asked questions

What is IndexNow?

IndexNow is an open protocol that tells participating search engines, with a single HTTP request, when a URL on a site is added, updated or deleted. Instead of waiting for the search engine's crawler to discover the change on its own, the site owner reports it directly.

Does Google support IndexNow?

No. IndexNow's official list of participants includes Bing, Yandex, Seznam, Naver, Yep, the Internet Archive and Amazonbot; Google is not on that list. For Google you still need sitemap.xml, accurate lastmod values and Search Console.

Is IndexNow free?

Yes, IndexNow is a free and open protocol. You do not need to create an account; publishing a key file that proves site ownership and sending URLs to the API endpoint is enough.

Does IndexNow replace a sitemap?

No. IndexNow is designed only to report URLs that were recently added, changed or deleted. IndexNow's own FAQ also recommends using an XML sitemap for the site's full URL inventory and running both methods together.

Is a URL submitted to IndexNow indexed immediately?

There is no guarantee. A 200 response code only shows that the search engine received the URL. The search engine evaluates the URL based on its own crawl quota, scheduling and quality signals; if the content is weak, the notification alone will not get it indexed.

Sources

  1. IndexNow.org: Documentation
  2. IndexNow.org: FAQ
  3. IndexNow.org: Participating search engines (searchengines.json)
  4. Cloudflare Docs: Crawler Hints
  5. Google Search Central: Sitemaps overview