The value of IndexNow is only one sentence: it reduces the waiting time for "new content to be seen by search engines" from days of passive crawlers to hours of active push. It is also effective for AI answer interfaces with Bing as the underlying index. It is not a ranking tool, nor does it allow pages with insufficient quality to be cited out of thin air; what it does is shorten the time difference between "publishing" and "indexing". Many B2B websites in Taiwan update product pages and blogs every week, but this time gap eats up visibility for several days.
What is IndexNow and why it’s relevant to AI search
Traditionally, search engines rely on crawlers to periodically visit your website and discover on their own what has changed. For websites with few pages and low weight, the frequency of return visits may be several days or even longer. IndexNow does the opposite: when you add, update, or delete a URL, it actively uses an API to notify the search engine that "this page has changed, come and crawl it." This agreement was jointly launched by Microsoft Bing and Yandex in 2021, and engines such as Seznam and Naver have since joined. The key design is that you only need to submit to one of the participating engines, and it will share the submissions with other participants without having to chain them one by one.
The relationship with AI search must be clearly stated to avoid misunderstandings. IndexNow directly benefits from Bing and interfaces built on top of Bing's index: Microsoft Copilot, DuckDuckGo, and some ChatGPT search results indexed through Bing. In other words, what you are accelerating is the Bing index pipeline, which will also affect the AI products that eat this pipeline. As for Google, it currently does not use IndexNow; Perplexity and OpenAI's own search crawlers do not directly consume IndexNow signals. Therefore, the pragmatic positioning is: IndexNow is an accelerator to "open up the Bing system" and is a part of the GEO technology foundation, rather than a universal switch covering all AI engines.
Three prerequisites before taking action
The entire mechanism only requires three things to be in place before the push can begin.
- Generate a set of keys: 8 to 128 characters, using only a–z, A–Z, 0–9, and hyphens. It can be generated in Bing Webmaster Tools or generated by yourself as a random hexadecimal string.
- Deploy the key verification file: Save the key content as a plain text file, name it "your key.txt", and place it in the root directory of the website so that https://yourdomain/yourkey.txt can be publicly accessed. Search engines will read this file to confirm that the submission was made by you.
- Make sure that the URL to be submitted and the key file belong to the same domain: cross-domain submissions will be rejected; each subdomain needs its own key file.
The simplest approach: single URL push
When publishing a new article and only want to notify a URL, a GET request is enough. Just call https://api.indexnow.org/indexnow?url=the complete URL to be submitted&key=your key; you can also directly call the Bing endpoint https://www.bing.com/indexnow, which has the same effect. Remember to perform URL encoding on the URL, especially for Chinese paths. Returning 200 means it has been received. This method is suitable for manual triggering or websites with small content.
Batch push: send multiple URLs at once (API example)
The website is large and sending one by one is too slow, so use the batch endpoint instead. Send a POST to https://api.indexnow.org/indexnow with Content-Type: application/json; charset=utf-8 in the header and a JSON object containing four fields in the request body.
- host: Your domain hostname, such as www.example.com.
- key: Your key string must be exactly the same as the key file content.
- keyLocation: The complete URL of the key file, such as https://www.example.com/yourkey.txt.
- urlList: An array of URLs to be submitted, up to 10,000 at a time, and each URL must belong to the domain specified by host.
One principle runs through them all: only send when the content really changes. Think of IndexNow as a notification, not a scheduled task. Some teams have written loops to resend the entire website URL every day. This will not speed up anything, but may trigger rate limits and reduce trust. The correct trigger point is a release, major update, or deletion of a page - commit when deleting to allow the engine to move the invalid page out of the index as quickly as possible.
Can't understand the response code? Use this checklist to debug
- 200 OK: The submission was successful and the engine has been accepted.
- 202 Accepted: Received, but the key is still being verified, which usually means that the engine has not read your key file.
- 400 Bad Request: The request format is wrong, most likely due to bad JSON or missing fields.
- 403 Forbidden: The key is invalid. Check whether the content of the key file is completely consistent with the submitted key.
- 422 Unprocessable Entity: The URL does not belong to the specified domain, or the key and keyLocation do not match.
- 429 Too Many Requests: Sending too frequently, slow down the speed, merge into batches and then send.
Integrate IndexNow into the publishing process and let it run automatically
Manual delivery is only suitable for getting started. The real benefit comes from tying the push into the release process so that it is automatically triggered every time it goes online. WordPress users can install Bing’s official plug-in, or use Rank Math or Yoast’s built-in IndexNow support. If your website is hosted on Cloudflare, there is a click to open Crawler Hints in the background, which will automatically send them to you. For architectures such as self-built websites or Next.js, the method is to call the batch endpoint in the webhook or CI process of content publishing: collect the URLs that have been changed and send them out in one POST. The key point is to let the action of "publish" itself type out the notification, without relying on people to remember it.
IndexNow is a piece of GEO's technical foundation with a high return rate: set it once and you will automatically benefit in the long term, and the cost is almost only the initial connection. But it is only one link in the visibility chain. The former is whether the website can be crawled and structured and understood, and the latter is whether the content can be quoted cleanly by AI. If you're not sure how well your website is indexed and where it gets stuck on Bing and the AI interface, you can book a 30-minute GEO diagnosis where we'll break down indexing, crawlability, and citability.
