Why doesn't Google support IndexNow?

Google has tested IndexNow since 2021 but has not adopted it as of mid-2026. Google has not published a detailed public rationale; the practical takeaway for site owners is that IndexNow integration cannot replace Google's documented discovery workflows (sitemap submission via Google Search Console, organic crawl, manual Request Indexing). Continue to rely on those for the Google share of search traffic; treat IndexNow as complementary infrastructure for the Bing-Yandex-Naver-Seznam-Yep ecosystem.

Does IndexNow guarantee my pages get indexed?

No. IndexNow is a notification protocol: it tells participating engines that a URL has been added or updated. Each engine still independently decides whether to crawl, when to crawl, and whether to index. New domains in trust-gated states (notably Bing for new sites with no inbound links or established history) can submit hundreds of URLs via IndexNow and see no crawl movement; the protocol does not bypass quality, authority, or trust signals. Treat it as a fast notification channel, not a fast indexing channel.

How is IndexNow different from submitting a sitemap?

Sitemaps and IndexNow address different problems and complement each other rather than substituting. A sitemap is a pull-model manifest: 'here is my full URL inventory, fetch on your schedule'. IndexNow is a push-model notification: 'this specific URL just changed, please re-fetch'. Sitemap submission via Bing Webmaster Tools or Yandex Webmaster runs through a separate pipeline than IndexNow ping, and the two channels are independently scheduled. Best practice: submit a sitemap (pull) AND integrate IndexNow (push), so engines get both the complete inventory and per-change notifications.

How do I implement IndexNow?

Two steps. First, generate an 8-128 character key composed of letters, numbers, and hyphens, then place a public-readable text file at your site root containing that key as content. The standard file path is / .txt (e.g. https://example.com/abc123.txt containing 'abc123'). This proves ownership when an engine fetches the key file for validation. Note: Bing's generator at bing.com/indexnow/getstarted defaults to a 32-character hex string, but the spec accepts any 8-128 character alphanumeric-plus-hyphens key. Second, send a POST or GET request to one of the IndexNow endpoints. The relay endpoint api.indexnow.org/indexnow forwards to all participants; you can also hit Bing's direct endpoint at www.bing.com/indexnow or Yandex's at yandex.com/indexnow for notification purposes (downstream crawl and index handling still differs by engine regardless of which endpoint received the ping). Most hosting providers and CMS plugins have IndexNow built in; Cloudflare's Crawler Hints feature automates the push on your behalf without code changes.

/terms/indexnow-protocol · 5 min read · intermediate

IndexNow Protocol

IndexNow is an open protocol for instant URL notification to participating search engines. Site owners deploy a public key file and POST changed URLs to a single endpoint; the receiving engine relays the notification to every other participant. Adopted by Bing, Yandex, Naver, Seznam, and Yep; not adopted by Google.

Citation status

ChatGPT0×Perplexity0×Claude0×Copilot0×Gemini0×

Last checked 2026-06-22

IndexNow is an open protocol for instant URL notification to participating search engines. Site owners deploy a public key file at their site root and POST changed URLs to a single endpoint; the receiving engine then relays the notification to every other participant. The protocol was launched on October 18, 2021 by Microsoft and Yandex¹. As of mid-2026 it is supported by Bing, Yandex, Naver (South Korea), Seznam (Czech Republic), and Yep (Ahrefs's search engine)². Google has tested IndexNow since 2021 but has not adopted it.

Status in 2026

IndexNow has become substantial infrastructure for the non-Google search ecosystem. Per IndexNow.org's 2026 metrics the protocol receives over 5 billion URLs daily across more than 80 million websites, and Microsoft reports (December 2025) that approximately 22% of clicked URLs in Bing originated from IndexNow submissions. Google has not adopted IndexNow as of mid-2026, so any IndexNow strategy must be paired with Google-specific workflows (sitemap via Google Search Console, manual Request Indexing) for the Google share of search traffic. For the Bing-backed ecosystem (Bing and public-web-grounded Microsoft Copilot), IndexNow is the canonical push channel.

A critical caveat: IndexNow is a notification, not a guarantee. Each receiving engine still independently decides whether to crawl, when to crawl, and whether to index. New domains in trust-gated states can submit hundreds of URLs and see no crawl movement; the protocol does not bypass quality, authority, or trust signals.

Working assumption (for IndexNow integration on a new domain): expect the protocol to provide notification reliability (your pings are received), not crawl reliability (each engine still applies independent scheduling and quality logic). Pair IndexNow with each engine's native sitemap submission channel; treat the two as independent signals. Do not interpret IndexNow ping volume as an indexing predictor.

How to apply

Two stages: implementation and integration discipline.

Implement the protocol once: generate an 8-128 character key (letters, numbers, hyphens) and place it as a public-readable text file at https://yourdomain.com/<KEY>.txt for ownership verification, then POST URL change notifications. The official relay at api.indexnow.org/indexnow forwards to all participants; direct endpoints (www.bing.com/indexnow, yandex.com/indexnow) accept the same payload. Most hosting platforms and CMS plugins bundle IndexNow; Cloudflare's Crawler Hints feature automates the push without code changes. See FAQ for the full implementation walkthrough.
Pair IndexNow with each engine's native sitemap submission: IndexNow is a push channel (per-URL change notification); sitemap is a pull channel (full inventory the engine fetches on schedule). The two pipelines are independently scheduled inside each engine's indexing system, so submitting both reduces single-channel risk. Submit your sitemap via Bing Webmaster Tools' Sitemaps section, Yandex Webmaster's Sitemaps section, Naver Webmaster Tools, and Google Search Console; deploy IndexNow once to cover the protocol-participating engines.
Trigger IndexNow ping at the right events: a sustainable IndexNow workflow pings on (a) new URL published, (b) substantive content update to an existing URL, (c) sitemap regenerated. Avoid pinging on every minor edit (header tweaks, typo fixes) since individual engines may rate-limit excessive pings and additional pings provide no benefit. For static-site setups, a CI step that runs IndexNow ping after deploy is the standard pattern.
Track IndexNow Insights in Bing Webmaster Tools: Bing exposes per-domain IndexNow submission counts and crawl status under Configuration > IndexNow. This view does not exist for Yandex / Naver / Seznam / Yep, so Bing Webmaster Tools is the only first-party diagnostic for whether your IndexNow integration is sending pings successfully.

What to skip:

Treating IndexNow as a replacement for sitemaps. The two address different problems and engines treat them as independent signals; dropping the sitemap to "rely on IndexNow" loses coverage for engines that batch-fetch sitemaps independent of per-URL pings.
Repeated IndexNow pings to "force" indexing of stuck URLs. The protocol does not bypass scheduling or quality logic. If Bing or Yandex has not crawled a URL after the initial ping, additional pings do not change downstream decisions; investigate the underlying signal (Bing Webmaster Tools URL Inspection, robots.txt audit, content quality, server response codes) instead.
Building IndexNow integration for Google coverage. Google does not participate; IndexNow integration provides zero signal to Google's indexing pipeline. Google coverage requires Google Search Console workflows (sitemap, Request Indexing) as separate work.

What remains contested or unverified

Several questions practitioner sources do not agree on or do not have public documentation for:

Whether IndexNow ping volume affects crawl priority at any participating engine. The protocol itself does not document priority semantics, and engines have not published whether per-domain ping rate influences scheduling decisions.
Whether ChatGPT search uses Bing's index as its sole or primary retrieval backend. OpenAI has not published a detailed pipeline documentation; published reporting (Search Engine Land, Ahrefs) describes Bing-grounded behavior at various points, but the specific routing between Bing index, OpenAI's own crawl, and other partnerships is not vendor-documented. The implication "IndexNow → Bing index → ChatGPT search coverage" is plausible but not verifiable from public documentation.
Google's specific rationale for not adopting IndexNow despite multi-year testing. Google has not published a position statement; community reporting describes various inferences but none are officially confirmed.

How it relates to other concepts

Crawl-side counterpart to AI crawler bots: AI crawler bots are the user agents engines use to fetch content; IndexNow is the protocol site owners use to notify those engines of changes. Together they describe the bidirectional handshake between site and engine.
Parallel metadata channel to llms.txt: llms.txt is a declarative file describing site structure; IndexNow is an active notification protocol for content changes. Different layers (descriptive metadata vs change notification), both practitioner-side.
Upstream of Microsoft Copilot citations for public-web-grounded Copilot experiences (Bing-receivable pings that crawl and index are a gating step). Also indirectly relevant to ChatGPT search and other Bing-grounded AI surfaces per third-party reporting, though OpenAI has not vendor-documented this pipeline. Brave Search and Perplexity use their own indexes; Google AI surfaces (AI Overview, AI Mode, AI Overview citation) use Google's index, which IndexNow does not feed.
Optimization-umbrella relevance: AI search optimization, answer engine optimization, and generative engine optimization all include IndexNow as an infrastructure step where their target engine ecosystem overlaps with IndexNow participants (relevant for Bing/Yandex/Naver/Seznam/Yep, irrelevant for Google/Brave).

Microsoft Bing announcement of IndexNow protocol launch, October 18, 2021. blogs.bing.com/webmaster/october-2021/IndexNow-Instantly-Index-your-web-content-in-Search-Engines. Co-announced by Microsoft and Yandex as an open protocol intended for any search engine to adopt. ↩
Per the IndexNow participants registry at indexnow.org/searchengines.json accessed 2026-05-25, seven participants are listed: the five consumer search engines (Microsoft Bing, Yandex, Naver (South Korea, joined 2023-07), Seznam (Czech Republic), Yep (Ahrefs)) plus Internet Archive and Amazonbot (crawl/archive participants rather than consumer search surfaces). The consumer search engine roster has been stable since 2024. Google has not adopted the protocol despite testing since 2021 and has not published a position statement. ↩

Part of Infrastructure· editorial cluster, not a semantic link

Cluster pillar: AI access control→

Also in this cluster: AI access control · AI crawler blocking · AI crawler bots · AIPREF (AI usage preferences) · LLMS.txt · +2 more

Mentioned in· auto-generated from other terms' related lists

FAQ

Why doesn't Google support IndexNow?: Google has tested IndexNow since 2021 but has not adopted it as of mid-2026. Google has not published a detailed public rationale; the practical takeaway for site owners is that IndexNow integration cannot replace Google's documented discovery workflows (sitemap submission via Google Search Console, organic crawl, manual Request Indexing). Continue to rely on those for the Google share of search traffic; treat IndexNow as complementary infrastructure for the Bing-Yandex-Naver-Seznam-Yep ecosystem.
Does IndexNow guarantee my pages get indexed?: No. IndexNow is a notification protocol: it tells participating engines that a URL has been added or updated. Each engine still independently decides whether to crawl, when to crawl, and whether to index. New domains in trust-gated states (notably Bing for new sites with no inbound links or established history) can submit hundreds of URLs via IndexNow and see no crawl movement; the protocol does not bypass quality, authority, or trust signals. Treat it as a fast notification channel, not a fast indexing channel.
How is IndexNow different from submitting a sitemap?: Sitemaps and IndexNow address different problems and complement each other rather than substituting. A sitemap is a pull-model manifest: 'here is my full URL inventory, fetch on your schedule'. IndexNow is a push-model notification: 'this specific URL just changed, please re-fetch'. Sitemap submission via Bing Webmaster Tools or Yandex Webmaster runs through a separate pipeline than IndexNow ping, and the two channels are independently scheduled. Best practice: submit a sitemap (pull) AND integrate IndexNow (push), so engines get both the complete inventory and per-change notifications.
How do I implement IndexNow?: Two steps. First, generate an 8-128 character key composed of letters, numbers, and hyphens, then place a public-readable text file at your site root containing that key as content. The standard file path is /<KEY>.txt (e.g. https://example.com/abc123.txt containing 'abc123'). This proves ownership when an engine fetches the key file for validation. Note: Bing's generator at bing.com/indexnow/getstarted defaults to a 32-character hex string, but the spec accepts any 8-128 character alphanumeric-plus-hyphens key. Second, send a POST or GET request to one of the IndexNow endpoints. The relay endpoint api.indexnow.org/indexnow forwards to all participants; you can also hit Bing's direct endpoint at www.bing.com/indexnow or Yandex's at yandex.com/indexnow for notification purposes (downstream crawl and index handling still differs by engine regardless of which endpoint received the ping). Most hosting providers and CMS plugins have IndexNow built in; Cloudflare's Crawler Hints feature automates the push on your behalf without code changes.

Sources & further reading

New terms shipped that week, plus one observation from the AI-citation tracker.

More about what you'll get

Last fact-checked 2026-05-25. Spotted an error or stale claim? See editorial methodology.

Changelog (3 entries)

2026-05-25: Small peer-review follow-up fixes. The Yandex observation now notes that 4 of the 5 disambiguation axes were applicable (edge cache state was not separately verified). Footnote citation updated against the official IndexNow participants registry (searchengines.json, accessed 2026-05-25), which lists seven participants: the five consumer search engines plus Internet Archive and Amazonbot. The consumer search engine roster has been stable since 2024 per public IndexNow updates. Cross-page back-links added for AEO, GEO, AI Search Optimization, AI Mode, and AI Overview citation.
2026-05-25: Same-day revision. Critical fact corrections: key spec is 8-128 alphanumeric characters plus hyphens, not 32-128 hex (32-hex is just Bing's generator default); Bing direct endpoint is www.bing.com/indexnow, not api.bing.com. Methodology revision: the same-domain observation is now framed as illustration of the protocol's documented interface-vs-scheduler separation, not independent evidence of trust gating (N=1 over 13 days does not isolate trust gating from new-domain cold-start, integration bugs, or other alternative causes). New 'What remains contested or unverified' section added.
2026-05-25: Initial publish: IndexNow is an open URL notification protocol launched 2021-10-18 by Microsoft and Yandex. As of 2026 it is supported by Bing, Yandex, Naver, Seznam, and Yep; Google has tested it since 2021 but has not adopted it. The entry documents protocol mechanics, current participants, the critical caveat that IndexNow is notification not guarantee, and a same-domain practitioner illustration (N=1, 13 days).