Engine notification / not Google
IndexNow for Website Indexing: What It Is, How It Works, and Why It Still Matters
IndexNow is a protocol for notifying participating search engines that a URL was added or changed. It can speed discovery outside Google, but it is not a Google indexing button and it does not replace a sitemap, internal links, or quality work.
The short answer
Think of IndexNow as a change signal
Traditional discovery waits for an engine to find a changed page through crawling, a sitemap, or links. IndexNow lets a site tell participating engines that a specific URL deserves a fresh look. That makes it especially useful for frequently updated own-site pages, but only on engines in the IndexNow family.
Google is deliberately outside this route
IndexNow does not notify Google. For Google indexing, use a verified Search Console property, URL Inspection for priority pages, a current sitemap.xml, and a page that clears technical and quality checks. Do not report an IndexNow ping as a Google submission.
Where it applies
Which engines honor IndexNow?
The participating engines named here are Bing, Yandex, Seznam, and Naver. A site owner can send one URL-change notification rather than treating each engine as a separate manual queue. The benefit is operational: one clean signal reaches the network that uses it.
| Engine | IndexNow role | What to remember |
|---|---|---|
| Bing | Participating engine | Useful for Bing discovery and its Webmaster Tools ecosystem. |
| Yandex | Participating engine | Receives the same change notification path. |
| Seznam | Participating engine | Included in the participating engine set. |
| Naver | Participating engine | Included in the participating engine set. |
| Not supported | Use GSC, a sitemap, internal links, and an appropriate Google workflow instead. |
Why the route still matters
Bing's index has influence beyond Bing
IndexNow is easy to dismiss if your primary KPI is Google. That misses the broader discovery surface. ChatGPT search leans on Bing's index, so a current Bing-facing signal can matter when people discover a site through an answer engine as well as a conventional results page.
This is not an argument to abandon Google fundamentals. Keep your canonical pages accessible, publish a consistent sitemap, and use internal links that explain the site. Then use IndexNow as a focused notification when a page is added or changed. It complements your own-site indexing stack; it does not turn a weak page into a strong one.
Implementation / key + ping
How to implement IndexNow
The setup has two pieces: prove control of the key, then notify a participating engine when a URL changes. Follow the current instructions for your integration; the shape below is a compact mental model rather than a substitute for the protocol's own documentation.
Generate a key
Create an IndexNow key for the site. Keep the value stable for the integration and treat it as site configuration.
Publish the key file
Place a plain-text file containing the key at the required location on the site so the receiving service can verify control.
Notify the URL
Send the changed URL and key to the IndexNow endpoint after a publish or update event.
Watch the outcome
Check the participating engine's tools and keep Google on its separate Search Console path.
GET https://api.indexnow.org/indexnow?url=https%3A%2F%2Fexample.com%2Fpage&key=YOUR_KEY
# key file at the site root:
YOUR_KEYThe key file must contain the exact key value. Do not paste a real production key into public examples.
CMS routes
Plugins make the ping automatic
Many content-management systems offer an IndexNow plugin or built-in integration. The useful pattern is simple: a publish, update, or delete event calls the notification route after the key file is available. Confirm that the plugin is configured for the canonical URL and does not fire for every duplicate parameter variant.
Limits / honest expectations
A ping is not an index guarantee
IndexNow reports a URL change. It cannot override a blocked crawl, a noindex directive, a canonical pointing to another URL, or an engine's quality threshold. A successful notification means the message was sent through the supported route, not that the page is now searchable.
Pair notification with evidence
For your own site, keep the page in sitemap.xml, link to it internally, and inspect it in GSC for Google's state. Use IndexNow for the participating engines, and use a bulk indexer such as IndexChex when you need submission, verification, and scheduled rechecks at scale.
IndexNow questions
IndexNow FAQ
Does IndexNow work with Google?
No. Google does not honor IndexNow. The route here covers Bing, Yandex, Seznam, and Naver. For Google, use Search Console, a current sitemap, internal links, and pages that pass technical and quality checks.
Which search engines support IndexNow?
The participating engines named in this guide are Bing, Yandex, Seznam, and Naver. Notify once through the protocol rather than maintaining a separate manual ping for each named engine.
How do I set up IndexNow on my website?
Create a key, publish a text file containing that key at the required site location, and send a ping for a URL after it changes. Many CMS platforms offer a plugin or integration that handles the publish event for you.
Does IndexNow guarantee indexing?
No. It is a change notification, not an override of crawl, canonical, quality, or indexing decisions. Keep the sitemap and internal links healthy, and use Search Console or an indexer with verification when you need evidence of what happened.
Put the signal in the right sequence
Use the Indexing Diagnostic for blockers, then return to the ranked website indexing stack for a site-owner workflow that includes Google and Bing-family engines.