Submit URLs with IndexNow — verify your key first
Notify Bing, Yandex, Naver, Seznam, Yep and Amazon through IndexNow. We check your key file first, and show the response from each selected engine. Acceptance does not guarantee indexing.
Why the key check matters. Bing, Yandex and the global endpoint reply
202 Accepted to any well-formed key,
including one that was never uploaded — then discard the submission later without telling you. We fetch your key
file before submitting to catch missing or mismatched keys. A successful key check confirms what our request could retrieve; engine access and indexing decisions can still differ.
What is Instant IndexNow?
Instant IndexNow is a free IndexNow submission tool that verifies your domain key file before submitting, and distinguishes submission acceptance from indexing. Unlike the global endpoint, Bing and Yandex — which reply 202 Accepted to any well-formed key, even one that was never published, then discard the submission later without notification — Instant IndexNow fetches your {key}.txt the way a search engine does and confirms it contains your key before sending anything. It supports six supported engines via the global endpoint (api.indexnow.org) or per-engine direct submission to Bing, Yandex, Naver, Seznam.cz, Yep and Amazon, accepts up to 10,000 URLs per request, and needs no account for the free tier (200 URLs/day per IP).
What is IndexNow?
IndexNow is an open protocol introduced by Microsoft Bing and co-developed with Yandex. It lets a site owner tell participating search engines that a URL is new or has changed, instead of waiting for a crawler to notice. It affects discovery — how quickly an engine learns the URL exists. Whether the page then gets indexed still depends on the engine's own quality assessment.
Does this work for Google?
No, and no tool can make it. Google does not currently participate in IndexNow. Any service claiming to "submit to Google" via IndexNow is either using the Google Indexing API — which only accepts JobPosting and BroadcastEvent pages — or simply not doing what it says. For Google, use Search Console's URL Inspection tool and a healthy sitemap. Our Google indexing guide covers what actually helps.
Which engines participate?
Submitting to the global endpoint forwards your URLs to all of them in one request. Submitting to an engine directly tells you what that specific engine said.
| Engine | Where it matters | Key checked during request? |
|---|---|---|
| Bing | Global | No — replies 202 |
| Yandex | Russia, CIS | No — replies 202 |
| Naver | South Korea | Yes |
| Seznam.cz | Czech Republic | Yes |
| Yep | Privacy-focused, global | Yes |
| Amazon | Product search | Yes |
Engines that reply 202 validate your key asynchronously and give no further feedback, which is why we fetch the key file ourselves before submitting.
How it works
1. Get a key. Generate one here or use your own. It must be 8–128 characters of letters, numbers and dashes.
2. Publish the key file. Put a text file containing only the key at your domain root, e.g. example.com/your-key.txt. This is how an engine confirms you control the domain.
3. We check it. Before submitting we fetch that file and confirm it contains your key. If it does not, we tell you and submit nothing.
4. Submit. Paste URLs or upload a .txt/.csv, and see each engine's response.
What this saves you
- ✓The silent-failure problem. A 202 from Bing tells you nothing. We check your key file so a success here means something.
- ✓Host mismatches. URLs outside the submitted host are rejected by every engine. We catch that before sending.
- ✓Six endpoints, one form. No per-engine account or console.
- ✓Bulk input. Paste or upload thousands of URLs; duplicates removed automatically.
- ✓Doing it forever. Pro watches your sitemap and submits changes on its own.
Does an IndexNow success mean my page is indexed?
No. A key check verifies the file we retrieved, and an engine response describes the submission request. Neither proves that a page is in a search index. Check indexing separately in the search engine's webmaster tools.
| Response | Meaning and next step |
|---|---|
| 200 | Submission succeeded. Indexing still depends on the engine. |
| 202 | Received; key validation is pending. Keep the key file publicly accessible. |
| 403 | Key validation failed. Check the file location and contents. |
| 422 | Check URL ownership, host matching and the key format. |
| 429 | Rate limited. Follow Retry-After when supplied; avoid repeated immediate submissions. |
Sources: IndexNow protocol documentation and Google's Indexing API eligibility rules. Reviewed .
New to IndexNow? How it works · FAQ · API docs