Search engines find pages by crawling. A crawler visits your site on its own schedule, so a page you publish this morning can sit undiscovered for days. IndexNow changes that order. It lets you tell participating search engines the moment a URL is added, updated, or deleted, instead of waiting to be found.
This gap frustrates almost every client we work with. They ship a new landing page, refresh a pricing page, or fix a service page, and then nothing happens. The page is live. The sitemap is updated. And still the search result shows the old title for another week.
IndexNow is one of the few tools that attacks that specific delay. It is not a ranking trick and it will not fix thin content. It is a notification pipe. We think it is worth setting up on most sites, and we also think it is oversold. Here is the honest version.
IndexNow is an open protocol that lets a website owner ping search engines about content changes. The official site at indexnow.org describes it as an easy way for website owners to instantly inform search engines and web crawlers about the latest content changes. Microsoft Bing calls it a free, open-source protocol on its own IndexNow page.
The idea is simple. Instead of a crawler guessing when your page changed, your site raises its hand. You send one small request that names the URL. The search engine then knows to prioritise a fresh crawl of that address.
IndexNow is published under a Creative Commons Attribution-ShareAlike licence, according to indexnow.org. That matters more than it sounds. It means no single company owns the pipe, which is why several search engines were able to adopt the same format instead of each building a private API.
The participant list published on indexnow.org names Microsoft Bing, Naver, Seznam.cz, Yandex, and Yep. Those five are the engines that accept IndexNow submissions today. Submitting to one of them is enough, because indexnow.org states that a submission sent to one participating endpoint is shared across all IndexNow-enabled search engines.
That sharing rule is the part most people miss. You do not need five integrations. You send one request and the protocol fans it out. For a studio managing a lot of sites, that is the difference between a workable process and a chore nobody keeps up with.
The engines on that list also cover real markets. Naver is a major search engine in South Korea and Seznam.cz is a major one in the Czech Republic. If a client sells into either market, IndexNow stops being a nice-to-have and starts being a direct channel to the engine their buyers actually use.
No. Google does not appear on the participant list published at indexnow.org, which names Microsoft Bing, Naver, Seznam.cz, Yandex, and Yep. Google runs its own separate Indexing API, and Google restricts that one heavily. So IndexNow will not speed up Google indexing for a normal marketing site.
It is worth understanding how narrow Google's alternative is. Google's own Indexing API documentation states that the Indexing API can only be used to crawl pages with either JobPosting or BroadcastEvent embedded in a VideoObject. That is job listings and livestream video. It is not a general purpose tool for your blog or your service pages.
So for Google, you are still working the normal way. You publish, you keep a clean sitemap, and you watch coverage in Google Search Console. We wrote about that workflow in our guide to using Google Search Console to improve your rankings, and nothing about IndexNow replaces it.
You generate a key, host that key as a text file on your domain, and then send a request naming the changed URL. The key proves you own the site. Per the indexnow.org documentation, the key must be 8 to 128 characters using lowercase letters, uppercase letters, numbers, and dashes.
The key file rule is strict and simple. The documentation says to host a file named with your key and a .txt extension, usually at the root of the site, so it can be read at your domain followed by that filename. The file contains the key and nothing else. If a search engine cannot read that file, the submission fails.
Submitting a single URL is a plain web request. The documented format is the search engine host, then /indexnow, then the changed URL and your key as parameters. There is also a bulk format that posts JSON containing your host, your key, an optional key location, and a list of URLs.
The response codes are documented too, and they are useful for debugging. A 200 means the submission worked. A 202 means it was received while the key is still being validated. A 403 means the key was invalid or the key file could not be found. A 422 means the URLs do not match the host. A 429 means you hit a rate limit.
The indexnow.org documentation sets the ceiling at 10,000 URLs per POST request. For almost every business website, that is far more headroom than you will ever need. The practical limit is not the cap. It is the guidance that every submission counts toward your site's crawl quota.
The indexnow.org FAQ also notes that each participating search engine sets its own daily submission thresholds, and it recommends waiting at least five minutes between updates before resubmitting the same URL. That is the rule people break first. They wire IndexNow to fire on every save, and a single afternoon of editing turns into dozens of pings for one page.
Our rule is to submit on publish and on meaningful update, never on autosave. A meaningful update means the title changed, the body changed, or the page was removed. Anything smaller is noise, and noise is what gets you a 429.
Yes, but with realistic expectations. IndexNow costs almost nothing to set up and it genuinely speeds up discovery on Bing, Yandex, Naver, Seznam.cz, and Yep. It will do nothing for Google. So treat it as a cheap addition to your setup, not as the answer to a Google indexing problem.
There is a second reason we lean toward setting it up. Bing's index feeds more than Bing. Answer engines and AI assistants increasingly pull from multiple indexes, and being discovered faster in a non-Google index is not a wasted signal. We are careful not to overclaim here, because the exact plumbing behind each AI product is not public. But faster discovery in a real index has never hurt a client.
What IndexNow will not do is rescue a page nobody wants to rank. Discovery and ranking are different problems. If your page is thin, duplicated, or aimed at a query you have already covered elsewhere, telling five search engines about it faster just gets it ignored faster.
Most teams never touch the API. If your site runs behind Cloudflare, you can turn on Crawler Hints in the dashboard. Cloudflare's own documentation states that Crawler Hints supports IndexNow, which allows websites to notify search engines whenever content on their website is created, updated, or deleted.
Cloudflare's docs describe Crawler Hints as using Cloudflare cache signals to tell search engines when your content has likely changed, so they crawl your site at the right time instead of guessing. Enabling it is a toggle on the cache configuration page, not a build task. For a lot of clients, that is the entire implementation.
The other no-code route is a plugin or built-in integration. The indexnow.org FAQ points to integrations across common platforms including WordPress, Shopify, and Wix. Microsoft's IndexNow page also showcases large adopters including LinkedIn, eBay, GitHub, Wix, and USA Today, which is a reasonable signal that the protocol is stable enough to build on.
On builds where we control the deploy pipeline, we prefer firing the submission at publish time from the same job that rebuilds the site. That keeps one source of truth. The page goes live and the ping goes out in the same step, so the two can never drift apart.
The three failures we see most are a missing key file, submitting URLs that do not belong to the host, and pinging far too often. Each one maps to a documented error code. A 403 points at the key file. A 422 points at a host mismatch. A 429 points at rate limiting.
The key file mistake usually happens after a migration. The site moves, the root file does not come with it, and every submission starts failing silently because nobody is reading the response. If you automate submissions, log the status code. An integration that fails quietly is worse than no integration.
The host mismatch error catches teams running multiple domains or a staging subdomain. The URLs you submit have to sit on the host you named in the request. Sending a staging URL from a production key is a fast way to get nothing indexed and no explanation.
The last mistake is philosophical. Teams treat IndexNow as a substitute for a sitemap. It is not. You still want a clean, accurate sitemap, and we covered how to get that right in our piece on what an XML sitemap is and how to get it right. IndexNow is the fast lane. The sitemap is still the map.
It can, indirectly. Cloudflare frames Crawler Hints as a way for search engines to crawl at the right time instead of guessing, which reduces pointless crawling of pages that have not changed. Fewer wasted crawls means more crawler attention available for the pages that did change.
We want to be precise about the claim. IndexNow does not hand you extra crawl allowance. It gives crawlers better information about where to spend the allowance they already give you. On a small brochure site that difference is invisible. On a large catalogue or a content library with thousands of URLs, better targeting is real.
Whether that matters for your site depends on scale, and most sites worry about this far too early. We unpacked when it is genuinely worth your attention in our article on whether crawl budget actually matters for your website. For most businesses, the answer is still no.
If you are already on Cloudflare, yes, because it is a toggle and it takes minutes. If you are not, set it up the next time you touch your deploy pipeline. It is a small, permanent improvement to how fast several real search engines learn about your work. It is not urgent and it is not optional forever.
What we would not do is reorder your roadmap for it. Faster discovery on Bing, Yandex, Naver, Seznam.cz, and Yep is a genuine win, but it sits well below writing pages worth finding and shipping a site that loads fast. Do those first. Then add the pipe.
If you want a second pair of eyes on your indexing setup, or you are not sure whether your pages are even being found, we are happy to walk through it with you. Let us know what you are working on over at phoenix.studio and we will tell you honestly whether IndexNow is worth your afternoon.
Tell us where you want to go. We'll tell you how we'd get you there.