IndexNow: Telling Bing and Other Search Engines About Changed Pages
Short answer: IndexNow is an open protocol that lets a site tell participating search engines when a page was added, changed or removed. Bing and several other engines take part, while Google does not use it for crawling decisions, so keep sending your sitemap to Google as before. To use it, create a key, host a small text file with that key at your domain root, and send a request whenever a URL changes. A plugin can do this for you, or a short script can. Only ping URLs that actually changed, not every page on every visit.
What the protocol does and does not do
IndexNow is a notification. When your site sends a list of changed addresses, the engine can decide to recrawl them sooner than it otherwise would. It does not force indexing, and it does not guarantee a ranking change. A page still needs to be useful, crawlable and not blocked by a noindex tag.
Google has its own tools for the same job: the sitemap report and the URL Inspection tool in Search Console. Use those for Google. IndexNow is for the engines that have joined the protocol, which currently include Bing.
Create the key and host the file
The key is a random string of letters and numbers, between 8 and 128 characters long. Many plugins generate one for you. If you create it yourself, use a password generator and keep the result to letters and digits.
Save the key as a plain text file named after the key, such as 3f9a2c7b1e8d4f60.txt, and make the file contain only the key. Upload it to the root of your domain so that it opens at https://www.example.ca/3f9a2c7b1e8d4f60.txt. The key is meant to be public, because the search engine has to read it to check that you control the site. It is not a password, so treat it as harmless to see in a browser.
Send the notification
The simplest request is a GET with the page address and the key:
https://api.indexnow.org/indexnow?url=https://www.example.ca/blog/spring-deck-cleaning/&key=3f9a2c7b1e8d4f60
For several URLs at once, send a POST request with a JSON body that lists the host, the key, the key file address and up to 10,000 URLs. Most small sites never need that many in one request. Batch the changes from a single day into one request, and send it after your publishing step is finished, so the pages are live when the engine checks them.
Set it up without writing code
Several content management systems and e-commerce platforms have a plugin or app that handles the key and the notifications. Choose one that is actively maintained, check its reviews and last update date, and confirm that it sends notifications for edits as well as new pages. Some plugins only notify on publish, which misses price changes and corrections.
Check the setup by changing one page's title, then looking in the plugin's log or your server's logs for a successful response. A response code that says the key was accepted is what you want to see.
Set it up with a short script
If your site has no plugin for this, a developer can add a small hook that runs when a page is saved. The hook takes the page address, sends it to the endpoint and records the response. Keep the script in a place where only the site's administrators can change it. Limit the requests to real changes, so a busy site does not send a flood of identical pings.
Rules for pinging
- Ping when a page is created, when its text or price changes, and when it is removed.
- Do not ping on every visit, on a timer, or for pages that did not change.
- Send the address exactly as it appears in the sitemap, including the protocol and the www form you use.
- Send deleted pages as well, so the engine can drop them sooner.
- Keep the key file in place permanently. Removing it makes the requests fail.
Check that it works
- Change a sentence on one page and note the time.
- Confirm the notification was accepted in your plugin or server log.
- Search for the new sentence on Bing a day or two later, or check the URL in Bing Webmaster Tools.
- Keep a short note of any errors, such as a key file that returned a 404, and fix the cause before adding more pages.
Pings after a migration or a bulk change
A bulk change, such as a new URL structure or a move to a new domain, sends many addresses at once. Include the old addresses that were removed and the new addresses that replaced them in the same batch, so the engine sees both sides of the change. Keep each request within the limit, and spread very large batches over a day rather than sending everything in one burst.
Use the sitemap as a checklist after a large change. Every new address should appear in it, and every removed address should be gone. If the notifications and the sitemap disagree for more than a day or two, check that the plugin reads the same sitemap your site publishes.
Keep a simple log
Record the date, the number of addresses sent, the response code and any error. A short log answers questions such as whether a page was pinged before a customer reported it missing. It also shows quickly when a theme update has moved the key file.
FAQ
Does IndexNow help me rank on Google?
Not directly. Google does not use IndexNow for crawling decisions, so keep your Search Console sitemap and URL Inspection tools in your routine for Google.
Is it safe to share my key?
Yes. The key is designed to be visible in the key file. Keep it private only if you want to prevent others from using your notifications for your domain, and in that case, rotate it.
Will my plugin send pings for pages I hide?
That depends on the plugin. Check whether it respects your noindex and draft settings, because pinging a page you have blocked wastes requests and may confuse the report.
What if the request returns an error?
Most errors come from a key file that is missing, renamed or blocked by a redirect. Open the key file address in a browser and confirm it shows only the key before you change anything else.
If you would like us to put this in place with a clear log of every change it sends, share the platform your site uses.