IndexNow Protocol

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 adoption metrics, the protocol receives over 5 billion URLs submitted daily across more than 80 million websites, and Microsoft has reported (per Bing's December 2025 report) that approximately 22% of all clicked URLs in Bing search results originated from IndexNow submissions.

The notable gap is Google. As of mid-2026 Google has not adopted IndexNow. The practical consequence is that any IndexNow strategy must be paired with Google-specific workflows (sitemap via Google Search Console, manual Request Indexing) to cover the Google share of search traffic. For the Bing-backed ecosystem, including Bing and public-web-grounded Microsoft Copilot, IndexNow is the canonical push channel. It may also indirectly help surfaces that incorporate Bing-powered retrieval, though vendor-specific pipelines should not be assumed without explicit documentation.

A critical caveat is that IndexNow is a notification, not a guarantee. The protocol tells participating engines that a URL changed; the 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 via IndexNow and see no crawl movement; the protocol does not bypass quality, authority, or trust signals.

Same-domain illustration (aisearchglossary.com, 2026-05-13 to 2026-05-25, N=1 over 13 days): the site pushed 238 URLs via IndexNow over its first 13 days. Two engines participating in the same protocol returned different scheduler behavior:

• Bing: 1 URL indexed (the homepage), 1 URL crawled. Sitemap re-submission status remained in Processing for 24+ hours; AI Performance dashboard shows zero citations.
• Yandex: two confirmed real-user SERP clicks (per the 5-axis disambiguation framework documented in 2026-05-20_external-traffic-confirmed.md: visitors with Russian IPs, yandex.ru referrer, real browser UA, non-founder routine paths) on Day 13 (2026-05-25), suggesting Yandex indexed at least a handful of URLs and surfaced them in Russian-language search results.

This is an illustration of what the IndexNow specification itself states (each engine decides crawl scheduling independently), not independent evidence of a "trust gating" mechanism. Thirteen days is short for a new domain to overcome Bing cold-start regardless of IndexNow pings, and integration bugs, server errors, robots.txt issues, or other content-quality signals could also explain Bing's non-movement; this single observation does not isolate trust gating from those alternative causes. The Bing-vs-Yandex comparison is also asymmetric (Bing diagnostic metrics vs Yandex traffic outcomes are different surfaces), so the divergence should not be read as "Yandex outperformed Bing on identical inputs" without comparable indexing metrics from both sides.

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 composed of letters (a-z, A-Z), numbers (0-9), and hyphens (Bing's generator at bing.com/indexnow/getstarted defaults to a 32-character hex string, but the spec accepts any conformant length and character set). Place a public-readable text file at https://yourdomain.com/<KEY>.txt with the key as content (this is the ownership proof an engine fetches to validate your submissions), then POST URL change notifications to one of the participating endpoints. The official relay at api.indexnow.org/indexnow forwards to all participants; direct endpoints at www.bing.com/indexnow and yandex.com/indexnow accept the same payload format for notification purposes (downstream crawl and index handling still differs by engine regardless of which endpoint received the ping). The POST body specifies host, key, key location, and URL list. Hosting platforms and CMS plugins commonly bundle IndexNow integration; Cloudflare's Crawler Hints feature automates the push on your behalf without code changes, recommended for any Cloudflare-fronted site that does not need finer-grained control.
• 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 the same-domain observation above (Bing non-movement after 238 pings over 13 days) reflects trust-gating specifically, normal new-domain cold-start independent of IndexNow, or some combination of integration / quality / server-side issues that were not exhaustively ruled out. The observation is best read as consistent with multiple hypotheses rather than confirming any one.
• 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 document the user-agent strings AI engines use when fetching site content; IndexNow documents 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 for AI bots; IndexNow is an active notification protocol for content changes. Both are practitioner-side mechanisms for influencing how engines discover and prioritize content, but they operate at different layers (descriptive metadata vs change notification).
• Upstream of Microsoft Copilot citations for public-web-grounded Copilot experiences. Microsoft Copilot's public-web-grounded surfaces use the Bing index as their primary source pool, so Bing-receivable IndexNow pings that result in successful crawl and index are an upstream gating step for those Copilot citations. Microsoft 365 Copilot, Copilot Studio, and enterprise connectors draw from different data sources (internal tenant data, configured connectors) and are not affected by public-web IndexNow integration.
• Indirect relevance to ChatGPT search and other Bing-grounded AI surfaces: reporting describes ChatGPT search using Bing as one retrieval backend, so the same IndexNow → Bing index path that gates Copilot may also indirectly affect ChatGPT search coverage. OpenAI has not vendor-documented this pipeline, so the relevance is inferred from third-party coverage rather than confirmed. Brave Search and Perplexity use their own indexes, so IndexNow does not affect them. Google AI surfaces (AI Overview, AI Mode) 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 a recommended infrastructure step where their target engine ecosystem overlaps with IndexNow participants. The recommendation is engine-specific (relevant for Bing/Yandex/Naver/Seznam/Yep, irrelevant for Google/Brave).
• Reporting counterpart: AI Overview citation and similar Google-AI-surface tracking work entirely outside the IndexNow ecosystem because Google does not participate. Site owners targeting Google AI surfaces should track via Google Search Console; IndexNow integration provides no signal there.