IndexNow Explained: Instant Indexing for Bing, Yandex, and Beyond

IndexNow is a lightweight protocol that lets you push a list of changed URLs to participating search engines the moment content is created, updated, or deleted, instead of waiting for a crawler to discover the change on its own. It's backed primarily by Microsoft Bing and Yandex, with the submitted URLs shared across all participating engines through a single ping. Used correctly, it shortens the lag between "I published" and "the engine knows," and it does so without you babysitting a crawler.

What the protocol actually does (and doesn't do)

The mechanics are deliberately boring. You generate a key, host it on your domain to prove ownership, and then send an HTTP request containing one or more URLs. The receiving engine adds those URLs to its crawl queue. That's the entire contract.

Two points matter here, because they're the source of most disappointment:

• IndexNow is a discovery signal, not an indexing guarantee. You're telling the engine "this URL changed, look at it sooner." The engine still crawls the page, evaluates quality, checks for duplication, and decides whether to index it. Submitting junk doesn't make junk rank.
• Google does not consume IndexNow. Google ran a long evaluation and uses its own internal signals; for Google you still rely on sitemaps, internal linking, and the Indexing API (which is officially scoped to job postings and live-stream markup). Treat IndexNow as a Bing/Yandex/Seznam/Naver play, not a Google one.

The payoff is real but specific: faster pickup on Bing and Yandex, which in turn feeds downstream consumers (Bing powers DuckDuckGo, ChatGPT search, Copilot, and others). If a meaningful slice of your traffic or AI-citation visibility comes from that ecosystem, IndexNow is worth wiring up.

Setting up the key

You need a verification key, a hex string of 8 to 128 characters. Host it as a text file at your domain root, named after the key itself, containing only the key:

• Key: a1b2c3d4e5f6...
• File location: https://example.com/a1b2c3d4e5f6....txt
• File contents: the same key string, nothing else

You can host multiple keys, and you can place a key file in a subdirectory if you submit URLs only from that path. For most sites, one key at the root is fine. Bing Webmaster Tools and Yandex Webmaster can also generate and manage keys for you, and Bing will auto-submit URLs it already knows about, but rolling your own key gives you control over what gets pushed.

Submitting URLs

For a single URL, a simple GET works:

https://api.indexnow.org/indexnow?url=https://example.com/page&key=a1b2c3d4e5f6...

For anything beyond a one-off, use the batch POST endpoint. Send up to 10,000 URLs per request as JSON:

1. POST to https://api.indexnow.org/indexnow with header Content-Type: application/json
2. Body: {"host":"example.com","key":"a1b2c3d4e5f6...","keyLocation":"https://example.com/a1b2c3d4e5f6....txt","urlList":["https://example.com/a","https://example.com/b"]}

You can post to api.indexnow.org or to an engine-specific endpoint (Bing, Yandex). Either way the URLs are shared across all participating engines, so submit once, don't loop the same batch through every endpoint. A 200 means accepted; 202 means accepted but the key is still being verified; 403 means the key file couldn't be validated; 422 means a URL doesn't match the host or the key location is wrong; 429 means you're submitting too aggressively.

Where it actually helps

IndexNow earns its keep when freshness is part of the value proposition:

• News, deals, and time-sensitive content where being crawled hours sooner changes whether you catch the demand curve.
• Large sites with frequent changes, e-commerce price/stock updates, real-estate listings, job boards, where crawlers can't keep pace with your change rate.
• Deletions and 404s/410s. This is underrated: submitting a removed URL prompts the engine to re-check and drop it faster, which keeps stale results out of the index.
• Site migrations and redesigns where you want the new URL set picked up quickly.

Where it helps little: small, slow-changing brochure sites that already get crawled comfortably within their update cadence. The protocol won't hurt, but you won't notice it either.

Protecting crawl budget

The whole point of push-based indexing is efficiency, so don't undermine it by spamming submissions. The discipline:

• Submit only on genuine change. Fire IndexNow from a publish/update/delete hook, not from a cron job that re-submits your entire URL set nightly. Re-pinging unchanged URLs trains the engine to ignore you and can trip rate limits.
• Submit canonical, indexable URLs only. Never push URLs that are noindex, robots-blocked, parameter duplicates, or redirect targets. Pushing a URL you then tell the crawler to ignore wastes the very budget you're trying to save.
• Debounce bursts. If an editor saves a post six times in two minutes, send one submission after the dust settles, not six.
• Batch where possible. One POST of 500 URLs is cleaner than 500 GETs.
• Keep sitemaps in sync. IndexNow is additive to sitemaps, not a replacement. The sitemap remains your authoritative, complete URL inventory; IndexNow handles the "this one changed right now" nudge.

Implementation paths

Pick the lightest path that fits your stack:

• CMS plugin. WordPress users can get IndexNow through Rank Math, Yoast, or the standalone IndexNow plugin from Bing. These hook into post save/delete automatically, verify they're submitting only canonical URLs.
• CDN-level. Cloudflare offers a one-click IndexNow integration that watches your traffic and submits changed URLs. Convenient, but you give up granular control over what gets pushed.
• Custom hook. For bespoke apps, the cleanest design is an event in your publish pipeline that drops changed URLs onto a queue, with a worker that debounces and POSTs batches. This keeps submission off the request path and lets you log responses for debugging.

Whatever the path, log the status codes. A silent 403 means your key broke and you've been getting nothing for weeks.

Common mistakes

• Expecting Google results. It doesn't participate. Measure impact in Bing Webmaster Tools, not Search Console.
• Treating submission as indexing. Low-quality or thin pages still get filtered; IndexNow only changes timing of the crawl, not the verdict.
• Key/host mismatch. Submitting www.example.com URLs with a key hosted only on the apex domain (or vice versa) triggers 422/403. Host the key on the exact host you submit, or use the explicit keyLocation field.
• Re-submitting everything on a schedule. This is the fastest way to look like spam and get throttled.
• Pushing non-canonical URLs. If it shouldn't be indexed, it shouldn't be submitted.
• Forgetting deletions. Removing a page? Submit it. Faster removal is one of the protocol's quiet strengths.

The bottom line

IndexNow is a low-cost, high-leverage addition for any site where freshness matters on Bing, Yandex, and the AI and search products built on them. Set up one key, hook submissions to real content changes, send canonical URLs in batches, and keep your sitemap as the source of truth. Do that, and you get faster pickup across a meaningful chunk of the search and AI-answer landscape, without burning crawl budget or pretending it'll move Google.