Content that isn't indexed doesn't exist in search. Yet for most teams, the gap between publishing and discovery is measured in days β sometimes weeks. IndexNow changes that equation significantly for participating search engines.
What is IndexNow?
IndexNow is an open protocol that allows website owners to instantly notify search engines whenever content is created, updated, or deleted. Instead of waiting for a crawler to periodically revisit your pages, you push a signal directly β and the engine prioritises discovery of that URL.
The protocol was developed jointly by Microsoft and Yandex and is now supported by Bing, Yandex, Seznam, Naver, and other search engines. Critically, submitting to one participating engine typically notifies all others via a shared signal propagation system.
A single IndexNow submission can notify multiple search engines simultaneously, reducing the operational overhead of managing separate submission queues per engine.
How it compares to sitemap submission
| Method | Typical Discovery Time | Overhead | Real-time? |
|---|---|---|---|
| Organic crawl | 1β14 days | None | No |
| Sitemap ping | 24β72 hours | Low | No |
| GSC Indexing API | < 1 hour (quota limited) | Medium | Near real-time |
| IndexNow | < 30 minutes (typically) | Low | Yes |
Implementation basics
Setting up IndexNow requires generating an API key, hosting a verification file at the root of your domain, and then submitting URLs via a simple HTTP POST request to any participating engine's endpoint.
# Submit a single URL via IndexNow
curl -X POST "https://api.indexnow.org/IndexNow" \
-H "Content-Type: application/json; charset=utf-8" \
-d '{
"host": "yourdomain.com",
"key": "your-api-key",
"keyLocation": "https://yourdomain.com/your-api-key.txt",
"urlList": [
"https://yourdomain.com/new-page",
"https://yourdomain.com/updated-post"
]
}'The endpoint returns HTTP 200 on success, 202 on queued (processing), 400 on bad format, or 422 on URL validation failure. Building retry logic around these status codes is important for production pipelines.
Limitations to be aware of
- βIndexNow does not guarantee indexing β it signals crawl priority, not crawl outcome
- βGoogle is not currently a participating engine; GSC Indexing API remains necessary for Google
- βHigh-frequency URL churn (thousands of submissions per hour) may trigger rate limiting
- βKey verification must remain accessible; hosting changes can silently break submissions
Combining IndexNow with GSC API
For comprehensive indexing coverage, the most effective approach combines IndexNow (for Bing and others) with GSC Indexing API (for Google). SEOVentra manages both pipelines with unified queue management, retry logic, and per-URL status tracking β so you always know the indexing state of every URL across every engine.
visibility score
See how discoverable your content is to AI search engines β free, no card required.
Start free β