Whether you are publishing a fresh product page, correcting a broken price, or removing a discontinued catalog item, the traditional search index model can leave you waiting days or even weeks before crawlers discover your changes.1 Meanwhile, competitors with older but already-indexed pages rank above your fresh content. The IndexNow protocol was built to reduce that delay. Instead of hoping a crawler finds your changes on its next scheduled pass, you push a direct notification to participating search engines. This article walks through how the protocol works, how to submit URLs from the browser without installing a CMS plugin or backend service, and how to confirm every submission actually landed.
Why IndexNow Exists and How It Works
Search engines have always relied on a passive pull model: their crawlers visit your site on a schedule they control, discover new or changed pages, and add them to the index. Because these proprietary crawler schedules remain entirely opaque, time-sensitive product launches and breaking news updates can sit invisible for days simply because a crawler has not prioritized your domain. For small sites with limited crawl frequency, the wait stretches even longer, and this structural delay directly harms organic traffic during critical launch windows.
While traditional search engines depend on this reactive discovery model, IndexNow flips the dynamic entirely by establishing an active push mechanism. Instead of waiting for a crawler to discover your changes, you push a notification the moment content goes live. A single HTTP POST request to the shared global endpoint at api.indexnow.org sends your ping through the protocol’s participating engines. You don’t need separate integrations for Bing, Yandex, Naver, or any other participant. One call reaches them all.2 This is the core idea behind CapyToolkit’s approach to browser-based tools that process everything locally: you stay in control of your data, and the protocol handles the distribution.
Microsoft Bing and Yandex co-authored the protocol, establishing an open standard that Naver, Seznam.cz, Amazon, Yep, and Internet Archive have since joined.13 It is an open specification, not a proprietary API locked behind a single vendor’s dashboard. That openness is what makes a browser-based submitter possible in the first place.
How the IndexNow Protocol Works
Every IndexNow submission carries two things: an API key and a list of URLs. The API key ties your submission to a verification file hosted at your domain root: a plain text file named after the key (for example, mykey123.txt) containing only the key string. Search engines fetch that file to confirm you control the domain before accepting any URL pings from you.4
The submission itself is a simple HTTP POST to https://api.indexnow.org/indexnow. The body includes your key, the host you’re submitting for, and the URL list. The endpoint then fans out the notification to each participating engine. With each engine processing the ping independently, indexing speed naturally varies.4
Search engines treat IndexNow pings as a crawl priority signal, not a guarantee of indexing.15 The search engine still evaluates content quality, relevance, and its own algorithmic criteria before adding the page to the index. Think of IndexNow as ringing the doorbell rather than forcing your way inside.
Search Engines Reached via IndexNow
Submitting to the shared global endpoint notifies all participating engines in one call. You do not need separate submissions for each engine; the protocol handles distribution automatically.3 To help you track where your submissions travel, the following table outlines each participating engine and the response behavior to expect:
| Engine | Response Behavior | Notes |
|---|---|---|
| Bing | Varies by crawl queue | Microsoft co-authored the protocol |
| Yandex | Varies by crawl queue | Yandex supports submissions for new, updated, or deleted pages |
| Naver | Varies by crawl queue | Listed as a participating IndexNow engine |
| Seznam.cz | Varies by crawl queue | Listed as a participating IndexNow engine |
| Amazon | Varies by crawl queue | Listed as a participating IndexNow engine |
| Yep | Varies by crawl queue | Listed as a participating IndexNow engine |
Indexing speed varies by engine and by the individual page’s quality signals. A well-structured, canonical page with clean markup may be crawled and indexed faster than a thin or duplicate-heavy one.5 The key advantage is that you’ve moved from passive waiting to active notification.
First Submission Walkthrough
CapyToolkit’s IndexNow submitter pushes URLs to search engines from the browser with no backend, no CMS plugin, and no SaaS account needed. You open the tool, provide your URLs, and click submit. Everything, from sitemap fetching and URL extraction to batching and the actual HTTP requests, happens client-side.
To put this client-side workflow into practice, start by feeding URLs into the tool using one of three input methods: Paste URLs directly into the textarea, one per line. Drop a sitemap XML file onto the drop zone and let the tool extract every URL automatically. Or upload a plain .txt file with one URL per line. All three inputs are combined into a single submission queue.
The tool processes URLs in batches of 50 with a five-second delay between each batch. That pacing keeps requests conservative and makes 429 responses easier to spot.4 A live progress indicator shows each batch as it fires, and the results table records the HTTP response code per batch so you can see at a glance what landed and what didn’t.
Setting Up the Verification Key
Before any search engine accepts your submissions, it needs proof you control the domain. That proof is a verification file at your domain root: a plain text file named after your API key. If your key is mykey123, the file must be accessible at yourdomain.com/mykey123.txt and contain only the key string itself.
The tool ships with a shared CapyToolkit key pre-filled. To use it, click “Download Verification File” and upload the resulting .txt file to your domain root via FTP, SFTP, or your hosting control panel. Place it once and it stays. Every future submission using that key will pass verification as long as the file remains accessible.
If you prefer your own key, replace the key value in the tool’s input field with a string between 8 and 128 characters using letters, numbers, or dashes. Then create a plain text file named after your key, put the key value inside it, and upload it to your domain root. The same file-naming rule applies: key abc12345 means a file at yourdomain.com/abc12345.txt containing abc12345.4
Use the shared key for quick testing or one-off submissions. Switch to your own key if you’re running regular submissions for a production site. It keeps your verification independent of any third-party tool.
What to Submit and When
Submit whenever content changes in a way that matters to visitors or search engines. The most common triggers include:
- New blog posts or articles going live
- Product pages added, updated, or removed
- Price or availability changes on existing product pages
- Rewritten descriptions, titles, or meta content
- Permanently deleted pages you want de-indexed
Submitting deleted URLs is a step most site owners skip. When you remove a product or take down a page, the old URL still exists in search engine indexes. Visitors click it and hit a 404. Sending an IndexNow ping for the deleted URL signals engines to stop indexing it, which cleans up your search presence faster than waiting for the crawler to discover the 404 on its own.
Avoid resubmitting pages that haven’t changed. Repeated pings for static content add noise without a clear benefit. Quality over volume. Every ping should represent a real change.
For large sites, the sitemap input is the most efficient path. Paste your sitemap URL, let the tool crawl and extract every listed URL, then submit them all in batches. If you need to submit multiple URLs to search engines in batches, the tool handles the batching and rate limiting automatically.
Common Submission Mistakes
Submitting URLs from multiple domains in a single batch is the most common error. IndexNow ties each submission to a single host, inferred from the first URL in the list. If you paste URLs from site-a.com and site-b.com together, the tool will submit all of them under site-a.com’s host, and the site-b.com URLs will fail verification. Run a separate submission for each domain.
Another frequent pitfall involves submitting every product variant URL instead of canonical URLs, especially for e-commerce stores. A product with ten color and size variants generates ten URLs, but they all share the same canonical tag. Submitting all ten produces duplicate-resolution overhead for zero indexing benefit. Submit only the canonical product URL.
Failing to place the verification file before submitting is a hard failure. Without the key file at your domain root, every participating engine will reject your pings with a 403.4 Upload the file first, confirm it’s accessible by visiting the URL in a browser, then submit.
Other pitfalls to watch for:
- Submitting URLs with session IDs or tracking parameters that create duplicate content
- Pinging URLs that redirect (
301/302) instead of the final destination URL - Ignoring
429responses and continuing to hammer the endpoint at full speed
Reading the Response Codes and Verifying Success
The results table in the tool shows the HTTP response code for each batch. Here’s what each code means:
200OK: The submission was accepted and processed. This is the ideal response.4202Accepted: The search engine has accepted your submission payload, but key validation is still pending as it queries your root directory to verify ownership of the domain.4400Bad Request: The submission payload was malformed. Check that your key is valid and the URL list is properly formatted.4403Forbidden: Key verification failed. The search engine couldn’t fetch your verification file, or the key in the file doesn’t match the key in your submission. Confirm the file is at the correct URL and contains only the key string.4422Unprocessable Entity: The submitted URLs do not belong to the declared host, or the key format fails to match the protocol’s schema specifications. Check that all URLs in the batch share the same domain.4429Too Many Requests: You’ve hit the rate limit. Slow down the batch frequency.4500Internal Server Error: A server-side issue at the IndexNow endpoint. Wait and retry.6
A 200 or 202 means your submission landed. Anything else needs attention before you consider the job done. For a deeper understanding of what each HTTP status code means, the MDN reference on what every HTTP status code means and when servers return each one covers every standard response.6
When a Browser Submitter Beats a CMS Plugin
CMS plugins are the standard path for platforms that support them. WordPress, Shopify, Wix, and others have IndexNow plugins that auto-submit URLs on publish and update events. If your platform has a well-maintained plugin and your content flows through normal CMS lifecycle events, use the plugin.
But plenty of situations fall outside that happy path. Static sites built with Hugo, Jekyll, or Astro have no CMS to hook into. Custom backends, whether Node, Django, Go, or anything hand-rolled, don’t have plugin ecosystems for IndexNow. In these cases, a browser-based submitter is the fastest way to push URLs without writing custom integration code.
Bulk operations are another gap. CSV imports, site restructures, and mass product deletions bypass CMS event hooks. A plugin won’t fire when you import 500 products via spreadsheet. A browser submitter lets you extract the new URLs and push them in a single batch, no code required.
Then there’s the privacy angle. When you use a CMS plugin or a third-party SaaS indexing service, your URL list passes through their servers. For internal tools, pre-launch pages, or any URL list you’d rather not share, a client-side submitter keeps everything on your machine, with no uploads, no server, and no third-party ever seeing your URLs or submission patterns.
The official IndexNow protocol specification covering the full HTTP request format, key verification flow, and endpoint behavior explains the underlying mechanics.2 For a broader introduction to why the protocol matters and how it fits into modern SEO workflows, a practical walkthrough of how IndexNow speeds up URL indexing compared to passive crawler discovery is a solid read. And if you’re dealing with deleted URLs that need to drop out of search results, the same submission workflow applies. Just make sure the old URL returns a 410 or 301 before you ping it.6
- 1.
Microsoft Bing Webmaster Tools team, “IndexNow - Instantly Index your web content in Search Engines,” bing.com, October 2021. https://blogs.bing.com/webmaster/october-2021/IndexNow-Instantly-Index-your-web-content-in-Search-Engines
- 2.
Microsoft Bing Webmaster Tools, “How to add IndexNow to your website,” bing.com, accessed June 2026. https://www.bing.com/indexnow/getstarted
- 3.
IndexNow.org, “Documentation for search engines,” indexnow.org, accessed June 2026. https://www.indexnow.org/searchengines
- 4.
IndexNow.org, “Documentation,” indexnow.org, accessed June 2026. https://www.indexnow.org/en_gb/documentation
- 5.
Yandex, “IndexNow protocol support,” yandex.com, accessed June 2026. https://yandex.com/support/webmaster/en/indexing-options/index-now
- 6.
IANA, “Hypertext Transfer Protocol (HTTP) Status Code Registry,” iana.org, September 2025. https://www.iana.org/assignments/http-status-codes
