Bing IndexNow Protocol

IndexNow uses a simple key-based authentication model to verify ownership and prevent spam. The key is a text file hosted at a well-known location on the domain.

• Key generation: A unique alphanumeric string, typically 8-64 characters
• Verification file: Placed at https://<domain>/<key>.txt containing only the key itself
• Key reuse: A single key can be used for all URLs on a domain and across multiple subdomains
• Security: The key proves control of the server's root directory, acting as a lightweight domain verification method

A single IndexNow submission simultaneously notifies all participating search engines, eliminating the need to ping each engine individually. This is a core efficiency gain over legacy ping protocols.

• Participating engines: Microsoft Bing, Yandex, Seznam, Naver, and others
• Discovery mechanism: Search engines discover submissions via the shared IndexNow endpoint or by crawling the key file location
• Protocol: The submitting server calls one endpoint, and the notified engine shares the submission with other participating engines via a peer-to-peer mechanism
• Result: A single API call replaces multiple engine-specific pings, drastically reducing server overhead

For large-scale programmatic sites, IndexNow supports submitting multiple URLs in a single request, avoiding the overhead of individual HTTP calls.

• Endpoint: A dedicated bulk endpoint accepts a JSON payload
• Payload format: { "host": "example.com", "key": "your-key", "urlList": ["url1", "url2", ...] }
• Limits: Typically 10,000 URLs per request, though practical limits vary by engine
• Use case: Ideal for dynamic sitemap generation pipelines where a batch of new or updated URLs is produced atomically

Unlike sitemap polling, which operates on a fetch schedule, IndexNow triggers a near-immediate crawl of the submitted URL. This dramatically reduces the indexing latency from days to minutes.

• Latency: Submitted URLs are typically crawled within minutes, not hours or days
• Mechanism: The notification bypasses the standard sitemap fetch queue and places the URL directly into the crawl priority queue
• Contrast with sitemaps: Sitemaps are polled periodically; IndexNow is event-driven
• Impact: Critical for time-sensitive content like news, job postings, or flash sales where rapid indexing is a competitive advantage

IndexNow supports notifying search engines of URL deletions, enabling faster removal of outdated or sensitive content from search results than waiting for a natural crawl to discover a 404 or 410 status.

• Method: A POST request with a "type": "URL_DELETED" parameter in the JSON payload
• Use case: Removing pages that have been programmatically deprecated or contain outdated information
• Advantage: Prevents users from landing on dead pages and conserves crawl budget by signaling that a URL no longer needs to be crawled
• Integration: Can be wired into content deprecation pipelines to automate removal notifications

A sitemap generated dynamically via REST or GraphQL endpoints rather than a static file. This architecture is the ideal companion to IndexNow, as it ensures the URL inventory is always real-time. When a headless CMS publishes content, the API-first sitemap reflects the change instantly, and the IndexNow ping notifies search engines of the specific delta without waiting for a scheduled crawl.

A sitemap file containing only URLs that have been added, modified, or deleted since the last full generation. IndexNow effectively acts as a push-based delta sitemap, but at the individual URL level. While a delta sitemap still requires a crawler to fetch and parse the file, IndexNow bypasses this by proactively pinging the search engine's API endpoint.

The approximate number of URLs a search engine bot will crawl on a site within a given timeframe. IndexNow directly optimizes crawl budget by eliminating wasted requests on unchanged pages. Instead of a bot re-crawling an entire section to discover one new URL, the protocol signals the exact change, allowing the crawler to focus its finite resources on high-value, fresh content.

A generation architecture where content publishing events trigger immediate sitemap updates via webhooks or message queues. IndexNow integrates into this pattern by acting as the final notification step. A typical flow:

• CMS publishes a new article
• Webhook fires to rebuild the sitemap
• IndexNow API call is made to https://api.indexnow.org This eliminates the traditional polling delay between sitemap updates and discovery.

The process of standardizing URLs to a consistent format by stripping default ports, decoding safe characters, and lowercasing the scheme and host. IndexNow requires strict URL normalization before submission. A mismatch between https://example.com/page and https://example.com/page/ (trailing slash) can cause the notification to be ignored. Always apply RFC 3986 normalization to the canonical form before calling the protocol.

A Google-specific service that allows programmatic notification of individual URL updates, primarily for job postings and livestream content. Unlike IndexNow, which is an open protocol supported by Bing, Yandex, and Seznam, the Google Indexing API is a proprietary, single-engine solution with strict use-case limitations. For cross-engine compatibility, IndexNow is the broader standard.