IndexNow URL Submitter

What is IndexNow?

IndexNow is an open protocol backed by Microsoft Bing, Yandex, Naver, Seznam.cz, and other major search engines. It lets website owners notify search engines the moment a page is published, updated, or removed, and a single API call to the shared global endpoint distributes the ping to every participating engine at once so you no longer depend on crawlers discovering the change on their own schedule.¹ The protocol is well-established across major platforms, including WordPress, Shopify, Joomla, and Drupal, where native integrations, plugins, or extensions handle the submission flow automatically. For sites that manage their own infrastructure, CapyToolkit's IndexNow URL Submitter handles submissions through a browser interface with no backend configuration required, so you can submit URLs without touching your server or CMS.²

Why faster indexing matters for your site

Without IndexNow, search engines discover new or updated pages by crawling your site on their own schedule. That schedule is unpredictable. A new product page, a corrected price, or a deleted post can sit undiscovered for days or even weeks. In competitive search categories, that delay gives other sites a window to rank ahead of your updated content.

IndexNow shifts the dynamic: instead of waiting for a crawler, you push a direct notification, and search engines treat IndexNow pings as a crawl priority signal so submitted URLs are typically revisited much faster than unnotified ones. Crawl budget is the other side of the equation. Search engines allocate a finite number of crawl requests per site per day, and without IndexNow much of that budget can be spent re-checking pages that have not changed. With IndexNow, you direct crawl activity toward pages that actually need attention, which reduces unnecessary crawl load and helps important pages cycle through indexing faster.³

The sites that benefit most are e-commerce stores updating inventory and prices daily, news and media sites publishing time-sensitive articles, SaaS product pages tracking feature releases, and any site that adds or modifies content in bulk. If you publish time-sensitive material such as limited-time offers or event announcements, the gap between publishing and indexing is often the difference between capturing traffic and missing it entirely.

The shared key model

Each IndexNow submission includes an API key and a pointer to a verification file stored at your domain root.¹ The verification file is a plain text file named after the key (for example, capytoolkit.txt) containing only the key value.² Search engines fetch that file to confirm you control the domain before accepting URL submissions. Place it once and it stays in place for all future submissions.

Switching to a private key

This tool uses a shared CapyToolkit key by default. To use it, download the verification file and upload it to your domain root, where the file is named after the key value. If you prefer your own key, replace the value in the key field, then create a plain .txt file named after your key containing the key value, and upload it to your domain root.

When and what to submit

Submit whenever content changes in a way a visitor or search engine would care about: a new blog post goes live, a product description is rewritten, a price or availability changes, or a page is permanently removed. Submitting deleted URLs is particularly useful because it signals search engines to stop indexing that page quickly, which helps with discontinued products, outdated event pages, and any content you have taken down.

Avoid resubmitting pages that have not changed, since repeated pings for static content may be treated as noise and some engines may reduce how much weight they give to future submissions from your domain. Quality of submissions matters more than volume, so focus on pages where the content has genuinely changed since the last ping. For large sites, the sitemap input is the most efficient path: paste your sitemap URL, let the tool crawl and extract all URLs, then submit them in batches of 50 with a five-second delay between batches that respects IndexNow rate limits and avoids 429 responses.

Search engines reached

Submitting to the shared global endpoint at api.indexnow.org notifies all currently participating search engines in a single API call, including Bing, Yandex, Naver, Seznam.cz, Amazon, and Yep. You do not need to send separate submissions to each engine because the IndexNow protocol distributes the ping automatically to every participant in the shared network, which keeps your submission workflow simple regardless of how many engines are participating at any given time.

How engine participation works

Participating engines process IndexNow notifications independently, so indexing speed may vary by engine and by the crawl priority each one assigns to your domain. Some engines apply IndexNow pings immediately to their crawl queue for faster processing, while others batch incoming notifications and process them during periodic crawl windows depending on their internal scheduling and crawl budget constraints.

The protocol does not guarantee instant indexing, but it does guarantee that every participating engine receives the same notification at the same time, which is a significant advantage over waiting for organic discovery. Once the notification arrives, each engine applies its own quality signals and crawl budget rules, so the time between submission and actual indexing depends on factors outside the protocol itself.⁴

Rate limits, response codes, and submission strategy

IndexNow accepts up to 10,000 URLs per submission call and permits multiple calls per day per host. The shared global endpoint at api.indexnow.org imposes rate limits that vary by engine and are not published as fixed numbers, but production behaviour shows that batches of 50 URLs with a five-second pause between batches stays comfortably within normal limits.⁵ This tool applies that pacing automatically.

Reading IndexNow response codes

Reading the response codes tells you what actually happened with each batch. A 200 response confirms the URLs were received and queued for crawling. A 202 means the submission was accepted but not yet processed; this is normal for first-time or high-volume submissions and does not require resubmission. A 400 Bad Request usually signals a malformed URL in the batch or an incorrect host field: check that your URLs are absolute, use HTTPS where your site does, and share the same root domain as your verification file. A 403 Forbidden means key validation failed, which points to the verification file being missing, containing the wrong content, or unreachable at the expected path on your server.⁵

For ongoing submission workflows, aligning your IndexNow calls with your CMS publish events gives the best results. A post published at 09:00 should trigger a submission at 09:00, not at the next scheduled batch run at midnight. The protocol is designed for real-time notification; submitting stale URLs hours after a change reduces the practical benefit over waiting for an organic crawl. Reserve sitemap-based bulk submissions for site migrations, domain moves, or the initial setup after placing your verification file for the first time. CapyToolkit's IndexNow Submitter handles sitemap parsing, URL deduplication, and batch pacing in one session, so you can run a full site submission without scripting or server access.