indexnow · definition
IndexNow: telling search engines a page just changed
Publish a page and you wait for a crawler to notice. IndexNow is the ping that skips the wait, for the engines that take part. How the protocol works, what it does not promise, and where it fits after publishing.
IndexNow is an open protocol for telling participating search engines that a URL has been added, updated or removed, so they can recrawl it promptly instead of waiting to rediscover the change on their own schedule.
reviewed 2026-09-02 · by the IT Master editorial team · how we check facts
What IndexNow is in practice
IndexNow is a small HTTP call, not a service you sign up for. You generate a key, a random string of letters, digits and dashes, and host it as a plain text file at your site root, so requesting that file returns the key and nothing else. The file is your proof that you control the domain.
After that, submitting is one request. A single URL goes as a GET to an endpoint such as api.indexnow.org, carrying the URL and the key as query parameters. A batch goes as a POST with JSON holding the host, the key, the key location and a list of up to 10,000 URLs. Participating engines share submissions with each other, so you send once rather than once per engine.
The response codes matter more than they look. 200 means received. 202 means accepted while the key is still being validated. 403 means the key file did not check out. 422 means a URL in the list does not belong to the host you claimed. Anything else and your pings are going nowhere quietly.
IndexNow tells participating search engines that a URL changed. It does not ask them to index the page, it does not argue the page's quality, and it does not reach Google.
Why it matters in 2026
Discovery is the slowest part of publishing. A new page has to be found before it can be crawled, and it is normally found when a crawler returns to your sitemap or follows a link to it. On a site with a modest crawl allowance, that gap runs to days.
IndexNow closes the gap for the engines that take part, among them Bing, Yandex, Seznam and Naver, and it does so on a push rather than a schedule. That matters far more when you publish continuously than when you publish monthly, because every article, every refresh and every changed price is a URL with a short freshness shelf life.
- Bing's crawl is not only about blue links. Microsoft's assistant surfaces are built on the same web index, so being crawled there sooner has a second audience.
- Google is not a participant. For Google, discovery still runs on sitemaps, internal links and a site that is cheap to crawl.
Treat IndexNow as one push channel among several, never as the whole discovery plan. Automating the boring parts of SEO is exactly this kind of work.
How this engine handles it
Publishing is the trigger. When an article clears the validation gauntlet it goes live on your site with its schema, internal links and FAQ block, and the engine pings IndexNow for that URL. The change and the notification are the same event, so there is no separate queue and no button anyone has to remember to press.
The key file sits on your domain either way, because the protocol verifies the domain rather than the tool making the call. That is worth knowing before you compare tools: the channel belongs to your site, not to whoever is publishing into it. Articles themselves arrive through whichever route you connect, such as the WordPress plugin or a signed webhook.
Two limits worth stating plainly. IndexNow reaches participating engines only, so Google is outside its scope entirely. And a ping is a request to look, not a promise to index: a thin page submitted quickly is still a thin page. That ordering is the point of the checks running before anything is announced rather than after.
Common misunderstandings
That submitting indexes a page. IndexNow reports a change. The engine still decides whether to crawl, and after crawling whether the page earns a place in the index. Nothing in the protocol argues your case for you.
That it is a ranking signal. It is a discovery mechanism. Faster crawling can shorten the time until a page ranks at all, which is not the same as ranking better.
That it covers every engine. It covers the participants, and Google is not one of them, so a tool that implies IndexNow speeds up Google is making a claim worth checking.
That you should submit everything. Send URLs that actually changed. Bulk resubmission of a static site is noise, and engines are entitled to throttle a source that generates it.
That the key file is a one-off. It has to stay reachable at the location you declared. Move it, rename it during a redesign or bury it behind a redirect, and submissions start failing with a 403 that nothing on your site will mention. Re-check it after every migration, alongside your crawler access.
questions people ask
Does Google use IndexNow?
No. Google is not one of the participating engines, and its own Indexing API is documented for job postings and livestream markup rather than for general pages. For Google, discovery still comes from your XML sitemap and its lastmod dates, from internal links pointing at new pages, and from a site fast enough to crawl at depth. IndexNow is still worth doing, because Bing, Yandex, Seznam and Naver share submissions between them and Bing's index carries a second audience of its own. Just do not budget for a Google effect that will not arrive.
Will IndexNow improve my rankings?
Not directly. It shortens the delay between publishing a change and an engine seeing it, which is a crawling problem rather than a quality one. If your pages are already found within hours, the gain is small. If you publish often, or new pages sit unseen for days because your crawl allowance is thin, the gain is real but bounded: the page still has to earn its position once it has been crawled. Think of it as removing a delay, not as adding weight.
How do I set IndexNow up on my site?
Generate a key of at least eight characters, using letters, digits and dashes, save it as a text file named after the key itself, and upload it to your site root so it is served as plain text. Then send each changed URL to an IndexNow endpoint with the URL, the key and, if the file is not at the root, its location. Most people never write that request by hand: a CMS plugin, a CDN toggle or the publishing tool does it on save. Test once with a single URL and confirm you get a 200 or 202 back.
How often should I submit the same URL?
Once per real change. Submit when a page is published, when its content is meaningfully updated, and when it is removed so the engine can drop it. Do not resubmit on a schedule, and do not push your whole sitemap nightly, which is the pattern engines throttle. Fixing a typo is not worth a ping. Rewriting the section that answers the query is. There is no queue to jump here, so repetition buys nothing and costs the credibility of every future submission.
related
See what search engines and AI assistants find on your site
Free, no account. Type your address and we show you what is missing and what we would write first.