IndexNow Guide: Protocol, Setup and SEO Benefits

IndexNow is a protocol for notifying participating search engines when a URL is added, updated, or deleted. It can speed up discovery, but submission does not guarantee that a search engine will crawl or index the URL.

Without a notification, a search engine may learn about a changed page through its next crawl or an updated sitemap. IndexNow gives site owners a direct way to report the change. The search engine still decides whether and when to fetch the URL, whether the content meets its guidelines, and whether the page belongs in its index.

How IndexNow works

The basic workflow has four parts:

1. Generate an IndexNow key.
2. Publish the key file at the required location on your host.
3. Send the changed URL or a batch of URLs to an IndexNow endpoint.
4. Monitor server logs and webmaster tools for crawl and indexing outcomes.

The Bing IndexNow setup guide documents the key, endpoint, and request formats. The protocol supports a simple GET request for one URL and a JSON POST request for a batch.

What a submission means

An IndexNow request is a notification, not an indexing command. The official IndexNow FAQ states that using IndexNow does not guarantee that a URL will be crawled or indexed. Search engines continue to apply their own crawl policies, quality systems, canonical selection, and indexing rules.

That means phrases such as instant indexing or guaranteed indexing are misleading. A successful response confirms that the endpoint accepted the notification. It does not prove that the URL was fetched or added to search results.

Submit one URL

For a single change, the request includes the URL and your key. The URL must belong to the host associated with that key. Follow the current endpoint and encoding requirements in Bing's setup guide rather than copying an old example from an unofficial source.

Use single-URL submission when you publish or update one important page and do not have an integration that automatically batches changes.

Submit a batch of URLs

The protocol also supports POST requests containing multiple URLs. According to the official FAQ, one POST can contain up to 10,000 URLs. A batch should include URLs from the host declared in the request and should contain pages that were genuinely added, updated, or deleted.

Batching is useful for a deployment, a catalog update, or a migration that changes many canonical URLs. Split larger sets into valid batches and avoid repeatedly submitting unchanged URLs.

Key placement and verification

The key proves that you control the host. The usual approach is to place a UTF-8 text file named after the key at the root of the website. The file contains the key itself. IndexNow also supports specifying the key file location when it follows the protocol's rules.

Keep the file publicly reachable over HTTPS. A blocked, redirected incorrectly, or mismatched key file can prevent a submission from being validated.

When to send notifications

• After publishing a new canonical page.
• After making a meaningful change to the main content.
• After deleting a URL or changing its canonical destination.
• After restoring a page that was previously unavailable.

Do not use IndexNow as a substitute for a crawlable site, accurate canonical tags, internal links, or an XML sitemap. Those foundations help search engines discover the wider site and understand how its pages relate.

Implementation options

CMS integration

Some content management systems and SEO plugins can send IndexNow notifications when a post is published, updated, or removed. Confirm that the integration submits the canonical public URL and does not fire repeatedly for drafts or insignificant changes.

Application integration

An application can submit URLs after a successful production publish. Queueing the notification after the page is live avoids telling search engines about a URL that still returns an error or old content. Log the response, but do not label the page indexed until a webmaster tool or search engine confirms that state.

Manual testing

A manual request is useful when verifying the initial key setup. Check the HTTP response, confirm the key file is reachable, and then inspect the URL in Bing Webmaster Tools. The inspection result is stronger evidence than the submission response alone.

How to measure the result

Track three separate events: notification accepted, URL crawled, and URL indexed. Keeping them separate prevents an accepted API response from being reported as an organic-search outcome.

Use Bing Webmaster Tools to inspect the canonical URL and review crawl or index status. Continue to monitor impressions and clicks separately. IndexNow can help with discovery, but it does not guarantee rankings, traffic, or inclusion in an AI-generated answer.

IndexNow checklist

• Confirm the final URL returns a successful response and is not blocked from crawling.
• Publish and verify the IndexNow key file.
• Submit only canonical URLs that changed.
• Use batches of no more than 10,000 URLs per POST.
• Record accepted submissions separately from crawl and index outcomes.
• Keep the XML sitemap and internal links current.

IndexNow is best understood as a timely notification channel. It can reduce the delay between a site change and search-engine discovery while leaving crawl, indexing, and ranking decisions with each participating search engine.