What is IndexNow and how to use it

What is IndexNow and how to use it: IndexNow is a protocol that tells participating search engines a URL was added, updated or deleted. Host a key file on your domain, then submit changed URLs by GET or POST, up to 10,000 per request.

Table of Contents

• What is IndexNow and how to use it in one minute
• How you prove you own the site with a key file
• How to use IndexNow step by step
• What IndexNow speeds up and what it does not
• IndexNow vs XML sitemaps vs waiting for a crawl
• Mistakes that waste your IndexNow submissions
• How to check IndexNow is working on your site
• Frequently Asked Questions
• The short version

What is IndexNow and how to use it in one minute

Search engines usually find changes by coming back to look. A crawler revisits your site on its own schedule, and your new page waits until it does. IndexNow reverses that. You publish, then you send a ping.

IndexNow: an open web protocol that lets website owners notify participating search engines when a URL is added, updated or deleted.

The ping is a plain HTTP request. It carries the changed URL and a key that proves you control the site. The search engine checks the key against a text file you host. Then it decides what to do with the URL.

To use IndexNow: (1) generate an 8 to 128 character hexadecimal key, (2) host it as {key}.txt on your domain, (3) submit each changed URL.

You only need to reach one participating endpoint. The IndexNow participating search engines page explains that the receiving service may share your notification with other participants. Each search engine advertises its own endpoint and protocol metadata. Check that page for the current list instead of trusting an old blog post. Yandex's IndexNow reference is one participant documenting the setup on its own site.

The official FAQ and documentation were updated in September and October 2026. Everything below follows that current text.

The job this takes off your plate is narrow. You stop waiting for a crawler to notice your new page. Whether the page then actually appears is a separate question, and tracking Google and Bing visibility in one place is how you answer it.

How you prove you own the site with a key file

Anyone could ping a search engine about any URL. The key file stops that. It's how the protocol confirms you control the host you're reporting on.

Key file: a UTF-8 plain-text file named {key}.txt that contains your API key and sits on your own host, so the search engine can fetch it and match it.

The rules come straight from the IndexNow documentation:

• The key is 8 to 128 hexadecimal characters (0 to 9, a to f).
• The file is named exactly after the key, with .txt on the end.
• The file contains the key and nothing else you'd need to explain.
• The usual location is the root, like https://example.com/{key}.txt. The documentation also describes other publicly accessible locations on the same host.

Generating a key takes one command. On a Mac or Linux terminal, openssl rand -hex 16 prints 32 hex characters, well inside the allowed range. Copy it, name the file after it, paste it inside.

Verification is mechanical. Yandex's documentation describes the API key as the value used to verify site management rights, matched against the key file contents. If the file and the key in your request don't match, the notification fails.

The key belongs to a host. You must send the key associated with the host you're notifying about. A key on example.com doesn't vouch for URLs on a different domain.

One loose end. A third-party site reports that a keyLocation field is now formally documented for POST requests, pointing to a key file outside the root. The official documentation cited here doesn't confirm that change. Treat it as unverified and keep your file at the root, where every reading of the spec agrees it works.

How to use IndexNow step by step

Once the key file is live, submitting is a few lines of work. Here's the full sequence.

1. Generate the key. 8 to 128 hex characters.
2. Create the file. UTF-8 plain text, named {your-key}.txt, containing the key.
3. Upload it. Site root is the safe choice.
4. Check access. Open the file URL in a private browser window. It must load without a login.
5. Wait for a real change. A page is published, materially changed or deleted.
6. Submit the full URL. Include protocol and hostname. https://example.com/pricing works. /pricing doesn't.

For a single URL, a GET request is enough. The general format from the IndexNow FAQ looks like this, with the target URL encoded:

https://<searchengine>/indexnow?url=https%3A%2F%2Fexample.com%2Fpage&key=YOUR_KEY

You can paste that into a browser for a test. In production, your CMS or a small script sends it.

For many URLs, use a POST request with a JSON body. The payload carries your host, your key and a list of URLs:

{
 "host": "example.com",
 "key": "YOUR_KEY",
 "urlList": [
 "https://example.com/new-post",
 "https://example.com/updated-guide"
 ]
}

Confirm the exact field names and endpoint against the official documentation before you ship it. Every URL in the batch should belong to the host whose key you're sending.

Up to 10,000 URLs fit in one POST request (IndexNow FAQ, 2026).

Most small sites never write this by hand. Many CMS platforms, hosts and plugins offer an IndexNow integration. Use one if you have it. Then check what it sends. An integration that fires on every save of every page creates noise the protocol asks you to avoid.

What IndexNow speeds up and what it does not

The common pitch says IndexNow gets your pages indexed fast. The official documentation says something narrower.

IndexNow is a notification. It is not a guarantee of crawling, indexing, ranking or an immediate change in search results. The FAQ and documentation both state this. The search engine still decides whether and when to crawl, index and rank the URL.

IndexNow guarantees indexing for none of the URLs you submit, and promises no ranking change (IndexNow documentation, 2026).

So what does it actually shorten? Discovery. The protocol is designed to reduce dependence on periodic crawling for finding out that something changed. Your page skips the wait for a crawler to stumble onto it. It doesn't skip the quality decision that comes after.

That distinction changes what you should expect. If a page is thin, duplicated or blocked, a ping only gets it judged sooner. The documentation is explicit that IndexNow doesn't replace normal crawling, indexing systems, canonicalization, robots directives or sitemaps. A URL that points its canonical somewhere else, or carries a noindex directive, still plays by those rules after you submit it.

The honest summary for a small business owner: IndexNow removes one source of delay you don't control. The rest is still the page itself. Clear answers, correct canonicals, nothing blocked by robots.txt.

One more limit. Submitting a URL once doesn't lock it into the index permanently. The protocol makes no promise about continued inclusion. If you change the page materially later, you submit it again.

IndexNow vs XML sitemaps vs waiting for a crawl

People often ask whether IndexNow replaces a sitemap. It doesn't. They answer different questions. A sitemap describes what exists. IndexNow reports what just changed.

Run IndexNow and a sitemap together. The sitemap keeps the full map current. IndexNow flags the specific URLs that just moved. Crawling still happens underneath both.

Mistakes that waste your IndexNow submissions

Most problems with IndexNow come from treating it as a firehose. Do NOT submit every URL on every deployment. The official guidance is to notify only when a URL is actually added, materially updated or deleted. Pinging unchanged pages tells search engines nothing new and turns your notifications into noise.

Here are the other mistakes worth checking for.

The key file is unreachable. Staging passwords, security plugins and bot challenges can block the file. If the search engine can't fetch it without authentication, verification fails silently on your side.

Relative URLs. The protocol requires fully qualified URLs with protocol and hostname. A path on its own isn't valid.

The wrong key for the host. Each host verifies against its own key file. Sending your main domain's key for a URL on another domain doesn't pass.

Forgetting deletions. IndexNow covers removed URLs too. When you delete a page, submitting that URL tells search engines the change happened instead of leaving them to find a dead link later.

Dropping the sitemap. IndexNow reports changes. It doesn't describe your full site. Keep the sitemap.

Expecting a ranking lift. The protocol is a discovery mechanism. Pages rank on what they say and how they're built.

If you publish on a schedule, tie the ping to the publish event itself, not to the deploy. That keeps submissions matched to real changes. Our practical playbooks cover publishing routines for small teams if you're setting that rhythm up from scratch.

How to check IndexNow is working on your site

You don't need special software to confirm the basics. Four manual checks cover it.

1. Load the key file. Open https://yourdomain.com/{key}.txt in a private window. You should see the key, with no login prompt and no redirect.
2. Compare the contents. The text in the file must match the key in your requests exactly.
3. Read the response. When you submit, the endpoint returns an HTTP status code. Look up its meaning in the official documentation instead of assuming success.
4. Check your server logs. Search engines verify by retrieving your key file. A request for that file after a submission shows the check happened.

If all four pass, the notification side is done. What happens next is the search engine's call.

That's the part we built ADpilot to measure. It writes SEO articles in your voice, waits for your approval, publishes to your blog, and tracks Google, Bing and AI search visibility in one place. Our AI blog writer handles the drafting side of that loop. What ADpilot does not do is turn IndexNow into a promise. No tool can force a search engine to index a page.

Frequently Asked Questions

Does Google support IndexNow?

We can't confirm Google participation from the IndexNow sources cited in this article. The current list of participants lives on the official IndexNow search engines page, so check it directly. Either way, keep submitting your sitemap through Google's own tools.

Can one IndexNow key cover several domains or subdomains?

Each host verifies against the key file it hosts, and you must send the key associated with the host you're notifying. The safe setup is a key file on every host you submit URLs for. Treat a subdomain as its own host.

Does fixing a typo count as an update worth submitting?

The guidance asks for notifications on material updates. A corrected price, a new section or a changed answer qualifies. Fixing one misspelled word usually doesn't change what the page tells a reader, so skip the ping.

Is IndexNow worth setting up on a small business site?

Yes, if your CMS or host offers an integration, because setup is a key file and a toggle. Small sites that publish rarely won't see a dramatic change, since crawlers find a handful of pages easily. For most owners asking what is IndexNow and how to use it, the real win is removing one delay for each new post.

Does IndexNow help my pages show up in AI answers?

The IndexNow documentation makes no claim about AI assistants. It notifies participating search engines that a URL changed, and nothing more. Anyone asking what is IndexNow and how to use it for AI visibility should treat it as one small input, with the page content doing the real work.

The short version

That's what is IndexNow and how to use it: a direct ping that tells participating search engines your page changed. Host an 8 to 128 character hex key as {key}.txt at your root, submit full URLs by GET or POST, and only when a page is added, materially updated or deleted. It shortens discovery, not the indexing decision. Keep your sitemap and keep improving the pages themselves.

Check how findable your site is, free: adpilot.ee/tools/findability-check