IndexNow and Indexing APIs: 2026 SEO Guide

IndexNow is an open-source push protocol that lets website owners instantly notify participating search engines about content changes—added, updated, or deleted—via a single API call. As of 2026, more than 80 million sites use IndexNow to submit over 5 billion URLs daily (Pressonify, Jan/Feb 2026). The protocol is supported by Bing, Yandex, Naver, Seznam.cz, Yep, and AmazonBot, but Google does not support IndexNow and has not signaled any near-term adoption (Pressonify; Search Engine Journal 2022). For Google-eligible content like job postings and live broadcasts, the Google Indexing API remains the only push alternative, with a limit of ~200 requests per day per project. This guide explains exactly what IndexNow can and cannot do, how to implement it, and how to combine it with other indexing methods for maximum coverage.

What IndexNow Is and Why It Matters in 2026

IndexNow was co-developed by Microsoft Bing and Yandex and launched in October 2021 under a Creative Commons Attribution-ShareAlike license (Wikipedia; iMark Infotech). The protocol solves a classic problem: traditional pull-based crawling can take 3–14 days on average to discover new or updated content (iMark Infotech). With IndexNow, a publisher notifies search engines the moment a change happens, and content often appears in search results within minutes to hours.

2026 Milestones:

• Over 80 million websites actively using IndexNow (Pressonify, Jan 2026).
• Daily URL submissions: 5+ billion, up from 3.5 billion in 2024 and 1.4 billion in September 2023 (Pressonify; Bing Blog Sep 2023).
• 22% of clicked URLs in Bing results originate from IndexNow-submitted content (December 2025), compared to 17% in 2024 and 12% in September 2023 (Pressonify; Wikipedia; Bing Blog Sep 2023).
• WordPress IndexNow plugins exceed 10 million active installations (Pressonify, Jul 2025).
• Cloudflare expanded IndexNow integration to all paid plans in Q4 2025 (Pressonify).
• Native support added for Shopify and Amazon shopping content in May 2025 (Wikipedia).

The protocol is free, requires only an API key hosted as a .txt file at the domain root, and supports both single-URL (GET) and batch (POST) submissions up to 10,000 URLs per request (indexnow.org/documentation; indexnow.org/faq).

Which Search Engines Support IndexNow (and Which Don’t)

Participating Search Engines (as of 2026):

• Microsoft Bing – co-founder; global search share ~4.98% (Searchlab 2026 via Jetfuel). IndexNow adopted since launch.
• Yandex – co-founder; ~60% market share in Russia.
• Naver – largest South Korean search engine (~55% share); adopted July 2023.
• Seznam.cz – dominant in Czech Republic (~25% share); adopted 2022.
• Yep – privacy-focused engine; adopted 2023; offers real-time indexing for verified publishers.
• Amazon – endpoint indexnow.amazonbot.amazon for AmazonBot crawler (indexnow.org/faq 2026).

Indirect Coverage via AI Search Engines: AI search engines such as ChatGPT Search, Microsoft Copilot, and Perplexity rely on Bing’s index. Therefore, IndexNow submissions that reach Bing also feed into these AI products. In March 2026, AI search referral traffic accounted for 0.9% of all web traffic, up 5x year-over-year (Jetfuel, citing Similarweb). ChatGPT alone had 900 million weekly active users as of February 2026 (Jetfuel, citing OpenAI). Microsoft launched an AI Performance Report in Bing Webmaster Tools in February 2026 to help track citations in Copilot (RankProof).

Engines That Do NOT Support IndexNow:

• Google – tested the protocol since October 2021 but has not adopted it as of May 2026 (Pressonify; iMark Infotech; Abdurrahman Simsek). Google relies on its Caffeine crawler, XML sitemaps, and the Google Indexing API (limited to JobPosting and BroadcastEvent structured data).
• DuckDuckGo – uses Bing’s index; indirectly benefits from IndexNow.
• Brave Search – independent index; no adoption.
• Baidu – China-only ecosystem; no support.

Future Adoption: At least two more regional search engines are expected to join in 2026 (Pressonify). The IndexNow partnership protocol is open to any engine with noticeable market presence and meaningful URL submission contribution (indexnow.org/searchengines).

How IndexNow Works: Protocol and Implementation

API Key Generation and Hosting

Generate a random key of 8 to 128 characters using lowercase a-z, uppercase A-Z, numbers 0-9, and hyphens (indexnow.org/documentation). Recommended: a 32-character hex string from openssl rand -hex 16 (trevorlasn.com). Example: 50283fcd8c764cfd9bd79a8b4002f647.

Host the key in a UTF-8 plain text file at the domain root:
https://yourdomain.com/your-key.txt
The file must contain only the key string. Alternatively, place it in a subdirectory and specify keyLocation with every submission, but all submitted URLs must begin with that path (indexnow.org/documentation). Ensure the file is publicly accessible without login; verify by opening in a browser (indexnow.org/faq). Set Cache-Control header with max-age under 1 hour so search engines re-validate frequently (Pressonify).

API Endpoints (2026)

You can submit to any one endpoint; the protocol shares the submission across all participating engines. Full list from indexnow.org/faq:

Engine	Endpoint
Global (shared)	https://api.indexnow.org/indexnow
Amazon	https://indexnow.amazonbot.amazon/indexnow
Bing	https://www.bing.com/indexnow
Naver	https://searchadvisor.naver.com/indexnow
Seznam.cz	https://search.seznam.cz/indexnow
Yandex	https://yandex.com/indexnow
Yep	https://indexnow.yep.com/indexnow

Submission Methods

Single URL (HTTP GET):
https://<endpoint>/indexnow?url=<url-encoded-full-url>&key=<your-key>

URL must be RFC-3986 percent-encoded (e.g., : → %3A, / → %2F). (indexnow.org/documentation)

Batch (HTTP POST):

• Max 10,000 URLs per request; exceeding returns 422 (indexnow.org/faq).
• Content-Type: application/json; charset=utf-8
• Payload includes host, key, urlList (array of full URLs), optional keyLocation.

Example:

{
  "host": "www.example.com",
  "key": "fa8c0a469da44e9b8f6a769f291829f5",
  "urlList": [
    "https://www.example.com/page1",
    "https://www.example.com/page2"
  ]
}

Response Codes

Code	Meaning	Action
200 OK	Submission received successfully	No further action; does not guarantee indexing.
202 Accepted	First submission while key validation is pending	Retry later if needed; subsequent submissions return 200.
400 Bad Request	Invalid format	Fix the request.
403 Forbidden	API key not found or invalid	Check key file and host.
422 Unprocessable Entity	URLs don't belong to host, key mismatch, or batch >10k	Adjust request.
429 Too Many Requests	Rate limit triggered	Implement backoff.

Sources: indexnow.org/documentation; indexnow.org/faq; stackoverflow.com

When to Submit – and When Not To

• Submit when: content is added, updated, or removed (new pages, price changes, product deletions, redirects, 404/410 pages, user-generated content updates) (indexnow.org/faq).
• Do not submit: unchanged URLs, all site URLs at once (unless after a migration/redesign), or retroactive submissions for content that changed before IndexNow setup.
• Frequency: Minimum 5 minutes between resubmissions for the same URL unless a meaningful change occurs (indexnow.org/faq). For user-generated content, submit incrementally (e.g., each review up to 20, then every 5 up to 100, every 10 up to 1000) (indexnow.org/faq).

IndexNow vs. Other Indexing Methods

Method	Speed	Coverage	Limits	Best For
IndexNow	Minutes to hours	Participating engines only (Bing, Yandex, Naver, Seznam, Yep, Amazon)	10k URLs/batch, 5-min re-submit interval	Frequently changing, high-priority content
Google Indexing API	Hours to days	Google, only for JobPosting and BroadcastEvent	~200 req/day/project; requires OAuth 2.0	Jobs and live events on Google
XML Sitemaps	Days to weeks	All major engines	50k URLs per sitemap, unlimited sitemaps	Full site inventory, long-term discovery
Google Search Console URL Inspection	Hours to days	Manual per-URL	No API; manual only	Debugging individual pages
RSS Feeds	Variable	Varies by engine	Not a primary indexing signal	News and blog updates

Key takeaway: IndexNow complements but does not replace XML sitemaps. Use IndexNow for speed on critical pages and sitemaps for comprehensive coverage. Every IndexNow submission counts toward your site’s crawl quota, but it signals importance and prioritizes crawling (indexnow.org/faq). Bing intends to reduce exploratory crawling on sites that use IndexNow (Bing Blog Oct 2021).

Integration Methods: From CMS to Custom Code

Native CMS and Platform Integrations

Many platforms now offer built-in IndexNow support:

• WordPress: Official plugin by Microsoft (Bing Blog); also integrated in Yoast SEO Premium, Rank Math, SEOPress, and Squirrly SEO. Over 10 million active installations by July 2025 (Pressonify). Squirrly automatically generates the API key and hosts the key file, lets you select which post types to auto-submit, and shows a history of the last 20 submissions (squirrly.co).
• Wix: Automatic for all premium Wix sites since September 2023; no action needed (Bing Blog Sep 2023).
• Shopify: Native integration added May 2025 (Wikipedia).
• Squarespace: Use third-party automation via Zapier or Make (Jetfuel).
• Duda: Built-in support since launch (Bing Blog Oct 2021).
• Webflow: Via third-party automation (Jetfuel).
• Joomla, Drupal, PrestaShop, OpenCart, Shopware, Typo3, Umbraco, MODX, XenForo, Bitrix24, Milestone: Extensions or modules available (indexnow.org/faq; Jetfuel).

CDN Level Integration

• Cloudflare: Expanded to all paid plans in Q4 2025 (Pressonify); announced at IndexNow launch (Bing Blog Oct 2021).
• Akamai: CDN-level integration announced at launch (Bing Blog Oct 2021).

SEO Tools with IndexNow Support

• Botify (FastIndex), OnCrawl, Onely, Yext (Bing Blog Oct 2021).

Custom Implementation with Code Examples

Python (using requests):

import requests

def notify_indexnow(url_list, key, host):
    endpoint = "https://api.indexnow.org/indexnow"
    data = {"host": host, "key": key, "urlList": url_list}
    response = requests.post(endpoint, json=data)
    print(f"IndexNow Status: {response.status_code}")

(from MCP-SEO)

Astro (build-time integration): Use the astro:build:done hook to read the generated sitemap and submit new/changed URLs in batches (trevorlasn.com).

Next.js (API route or build-time plugin): Create an API route in pages/api or the app directory that triggers on content publish events. Use a build-time script for statically generated pages.

Vue/Nuxt: Use Vue 3 composables or Nuxt server API endpoints.

React: A custom useIndexNow hook that fires on component mount when a shouldSubmit flag is true (trevorlasn.com).

Other frameworks: The same pattern applies to Angular, SvelteKit, Django, Flask, FastAPI, Express.js, Laravel, Rails, Spring Boot, ASP.NET Core (trevorlasn.com).

Important: The API key is public by design, so client-side submissions are possible, but you should protect any backend endpoint that proxies submissions with authentication and rate limiting (trevorlasn.com).

Best Practices for Production Use

Error Handling and Retry Logic

• Retryable status codes: 408 (timeout), 429 (rate limit), 500, 502, 503, 504 (server errors). Use exponential backoff with jitter: first retry after 1–2 seconds, then double each time (2s, 4s, 8s...) up to 3–5 max retries (Derrick App; Digital Applied; Zuplo; GetKnit).
• Non-retryable codes: 400, 401, 403, 404, 422 – fix the request and do not retry.
• For 429 responses, honor the Retry-After header if present; otherwise use backoff.
• Implement a circuit breaker: stop retrying after max attempts and fall back to logging or queuing.
• Idempotency: Avoid duplicate submissions on retries by using an idempotency key (e.g., a UUID) in the request header if your submission endpoint proxies to IndexNow (Digital Applied).

Rate Limiting

• The IndexNow API may return 429. Track submission success in Bing Webmaster Tools.
• No explicit daily limit beyond the 10,000-per-batch and 5-minute resubmission guidelines, but aggressive submission may trigger throttling. Monitor the IndexNow Insights Report for your site (Wikipedia; iMark Infotech).
• If building your own submission service, consider using token bucket or sliding window algorithms for smooth traffic (Zuplo 2026 Guide). Return clear rate limit headers and provide dashboard visibility.

Security

• API key exposure: The key file is public; protection comes from controlling usage in your application. Store the key in environment variables; never commit to Git (trevorlasn.com).
• Key rotation: Generate a new key, replace the old file, start submitting with the new key, then wait 24–48 hours before deleting the old file (indexnow.org/faq; trevorlasn.com).
• Protect your submission endpoint: If you create a backend endpoint that calls IndexNow on behalf of users, secure it with authentication (API keys, OAuth, JWT), rate limiting, request validation, and logging (trevorlasn.com).
• Inter-engine security: Search engines use RSA public-key cryptography and SHA256 hashing to verify forwarded notifications (indexnow.org/searchengines). This doesn’t affect your implementation.

Monitoring

• Bing Webmaster Tools IndexNow Insights Report: Shows submission volume, status, and diagnostics (Wikipedia; iMark Infotech).
• Bing Webmaster Tools AI Performance Report (Feb 2026): Tracks citations in Microsoft Copilot (RankProof).
• Custom logging: Log timestamp, URL, response code, error message, and request ID for every submission. Set up alerts for frequent 429s or failures (trevorlasn.com).

IndexNow in the Age of AI Search

Because Bing powers several AI search experiences, IndexNow submissions can indirectly improve visibility in these channels:

• ChatGPT Search uses Bing’s index (Pressonify; Jetfuel).
• Microsoft Copilot citations are trackable via the new AI Performance Report in Bing Webmaster Tools (RankProof).
• Perplexity AI also draws from Bing’s index.

As AI search referral traffic grows (0.9% of all web traffic in March 2026, up 5x year-over-year), IndexNow becomes a tool for ensuring your new content is fresh in the index that feeds these AI systems. This is especially relevant for news, real-time events, and frequently updated commerce sites.

Decision Tree for Large Sites: When to Use IndexNow, Sitemaps, and Google Indexing API

For a large site with thousands of pages, choose the right combination:

1. For all pages → Use XML sitemaps (foundation for long-term discovery).
2. For new or updated pages that need fast indexing (Bing, Yandex, etc.) → Use IndexNow. Prioritize product pages, time-sensitive content, and pages that drive revenue.
3. For job listings or live events → Use Google Indexing API (if eligible) and IndexNow for Bing.
4. For deleted or redirected pages → Submit via IndexNow to accelerate removal from participating engines.
5. For changes that happen less frequently (e.g., monthly blog posts) → Rely on sitemaps; IndexNow optional.
6. For user-generated content (reviews, comments) → Submit incrementally following IndexNow’s guidance (see above).
7. Never submit unchanged URLs – this wastes crawl budget and may trigger rate limiting.

Example workflow for an ecommerce site:

• Sitemap for all products (updated daily).
• IndexNow for products that change price, stock, or have new versions.
• Google Indexing API for job postings (if applicable).
• Monitor Bing Webmaster Tools for IndexNow health and AI citations.

Troubleshooting and Monitoring

Common Errors and Fixes

Error	Likely Cause	Solution
403 Forbidden	API key mismatch or key file inaccessible	Verify key file loads in browser; check the key string and file host.
422 Unprocessable Entity	URLs don’t match host, batch too large, key mismatch	Ensure all URLs begin with the same host as submitted; split batches of >10k.
429 Too Many Requests	Too many submissions too quickly	Implement backoff; check Bing Webmaster Tools for rate limit info.
200/202 but URL not indexed after days	Content quality, site trust, or crawl budget issues	Check Bing Webmaster Tools for crawl errors; ensure your site is otherwise healthy.
False 200 with invalid key	Redirects from key file to another page	Ensure key file returns HTTP 200 without redirection; disable follow redirects in testing. (stackoverflow.com)

Verification Steps

• Test with curl against the global endpoint:

  curl -X POST "https://api.indexnow.org/indexnow" \
    -H "Content-Type: application/json; charset=utf-8" \
    -d '{"host":"www.example.com","key":"your-key","urlList":["https://www.example.com/test"]}'
  

  Observe response code (should be 200 or 202).
• Verify key file accessibility: https://yourdomain.com/your-key.txt should return HTTP 200 with only the key string.
• Check Bing Webmaster Tools IndexNow Insights Report for submission history and errors.

FAQ

Q: Does IndexNow work for Google?
A: No. Google does not support IndexNow and has not announced plans to adopt it as of May 2026. Use XML sitemaps and the Google Indexing API (for eligible content) for Google coverage.

Q: Can I use IndexNow alongside the Google Indexing API?
A: Yes. They serve different purposes: IndexNow for multiple engines (Bing, Yandex, etc.) and Google Indexing API for job postings and live events on Google.

Q: Is IndexNow safe for SEO? Does it have spam risks?
A: IndexNow is safe. The API key is public, but search engines validate that the key file is on your domain. Submitting URLs from other domains is not possible. Over-submission (e.g., submitting unchanged URLs repeatedly) can trigger rate limiting and waste crawl budget. Follow the submission guidelines to avoid issues.

Q: What is the maximum number of URLs I can submit at once?
A: 10,000 URLs per batch. For more, split into multiple requests with a gap between them.

Q: How quickly will my URL appear in search results after an IndexNow submission?
A: Bing typically crawls within 1–3 days after the ping, with some demonstrations showing indexing in about 8 minutes (Incremys, citing Abondance 2025). Yandex and other engines are similarly fast. Speed depends on site authority, server response time, and submission volume.

Q: Do I need to submit all my URLs to IndexNow?
A: No. Only submit URLs that have changed or are new. Submitting the entire site at once may trigger rate limiting and is unnecessary.

Q: How do I monitor IndexNow performance?
A: Use Bing Webmaster Tools IndexNow Insights Report for submission stats and errors. Also log submissions yourself for internal tracking.

Summary and Next Steps

IndexNow is a practical, low-effort way to speed up indexing on Bing, Yandex, Naver, Seznam, Yep, and indirectly AI search engines. It is not a replacement for Google’s indexing pipeline, nor is it a silver bullet for poor content quality. But for sites with frequently updated content, implementing IndexNow alongside traditional sitemaps is a best practice in 2026.

Quick-Start Checklist:

• Generate a random API key (32+ characters).
• Host the key file at https://yourdomain.com/<key>.txt.
• Verify the file is publicly accessible and returns HTTP 200.
• Choose an endpoint (e.g., api.indexnow.org).
• Integrate submission logic into your CMS or custom pipeline.
• Test with a single URL using curl or a browser.
• Monitor Bing Webmaster Tools IndexNow Insights Report.
• Set up key rotation (e.g., every 6 months).
• Consider pairing with Google Indexing API for eligible content.

For further reading, see the official IndexNow documentation and the Bing Webmaster Tools guide.