# IndexNow: How to Set Up Your API Key, Test It and Ping Bing (and Why Google Does Not Use It)

> IndexNow explained: set up your API key, test it with a free IndexNow checker, ping Bing and other engines, and see why Google does not use IndexNow.

Canonical: https://abacklaunch.com/blog/indexnow-guide
Last updated: 2026-11-21

By Devvrat Hans, Founder. 9 min read. Published 2026-11-21.

IndexNow is an open protocol that lets a website tell search engines the moment a URL is added, updated or deleted, with one HTTP request, instead of waiting for a crawler to notice. You prove the site is yours with a key: a small text file at the root of your domain. One ping is shared with every participating engine, including Bing, Yandex, Seznam, Naver and Yep. Google does not use IndexNow. To check your key file is live and get the exact request to send, use the free [IndexNow checker](https://abacklaunch.com/tools/indexnow-tester).

For a startup, IndexNow is one of the cheapest technical SEO wins there is. Setup takes ten minutes, it costs nothing, and new pages can be picked up by Bing and the other engines within hours rather than days. It does not replace your sitemap, and it does nothing for Google, which is why you need both.

This guide covers how [IndexNow](https://abacklaunch.com/glossary/indexnow) works, which engines support it, the honest answer to "does Google use IndexNow", how to create and host your IndexNow API key, how to test it, how to submit URLs, and how to fix the errors people hit.

## How IndexNow works

Microsoft Bing and Yandex launched IndexNow in October 2021. The protocol has three parts:

1. **A key.** A string you choose, such as a random 32-character hex value.
2. **A key file.** A text file named after the key (`your-key.txt`), containing only the key, served from your site. When an engine receives a ping, it fetches this file to confirm the request came from the site owner.
3. **A ping.** A request to an IndexNow endpoint listing the URLs that changed. Participating engines share submissions with each other, so you send it once.

Search engines normally find changes by recrawling pages on their own schedule, guided by sitemaps and links. IndexNow flips that: you push the change to them. Each engine still decides whether and when to crawl the URL and add it to its index (see [indexing](https://abacklaunch.com/glossary/indexing)). A successful ping means "received", not "indexed".

## Which search engines support IndexNow?

| Engine | Supports IndexNow? | Notes | |
| Microsoft Bing | Yes | Co-founded the protocol. Bing's index also powers Yahoo search and other search partners | |
| Yandex | Yes | Co-founded the protocol | |
| Seznam.cz | Yes | The main Czech search engine | |
| Naver | Yes | The largest search engine in South Korea | |
| Yep | Yes | Ahrefs' search engine | |
| Amazon, Internet Archive | Listed | IndexNow's own list of recipients now also names Amazon's crawler and the Internet Archive | |
| Google | No | Not a participant; uses sitemaps and its own crawling | |

The list changes over time; the current one is on [indexnow.org](https://www.indexnow.org/). You do not need to ping each engine separately: the shared endpoint (or any single participating engine) passes the submission on to the others.

## Does Google use IndexNow?

No. Google said in late 2021 that it would test the protocol, but it has never joined: it is not on IndexNow's list of participating engines, and Google has never announced support. Pinging IndexNow has no effect on Google.

For Google, use the tools Google supports:

- **An XML sitemap** with accurate `lastmod` dates, submitted in Search Console. Google uses `lastmod` when it is consistently truthful. The [XML sitemap guide](https://abacklaunch.com/blog/xml-sitemap-guide) covers how to get it right, and the [sitemap checker](https://abacklaunch.com/tools/sitemap-checker) tests yours.
- **URL Inspection in Search Console** to request indexing of a single important page.
- **Internal links** from pages Google already crawls often, such as your home page.

Our guide on [how to get a website indexed by Google](https://abacklaunch.com/blog/how-to-get-website-indexed-by-google) covers the full process. Treat IndexNow as the fast lane for every other engine, and the sitemap as the lane for all of them, Google included.

## Your IndexNow API key

The "IndexNow API key" is not something you request from anyone. You make it up, host it, and use it in your pings. The rules:

- **Length:** 8 to 128 characters.
- **Characters:** letters (a to z, A to Z), digits and dashes. A random hexadecimal string, like the ones our tool generates, is the safest choice.
- **File name:** the key followed by `.txt`.
- **File content:** the key and nothing else, saved as UTF-8.
- **Location:** the root of your host, such as `https://example.com/your-key.txt`. If you host it elsewhere on the same host, include its URL as `keyLocation` in every ping.

The key is public by design. Anyone can read the file, and that is fine: the key only lets someone submit URLs on your own host, which tells engines nothing they could not discover anyway. This site works the same way. Aback Launch hosts its key at the root of the domain and pings IndexNow when a launch page goes live or changes, after the page is saved, so a slow engine can never hold up a founder's update.

## How to set up IndexNow, step by step

1. **Generate a key.** Open the [IndexNow tester](https://abacklaunch.com/tools/indexnow-tester) and press Generate, or create any valid string yourself.
2. **Create the key file.** A file named `<key>.txt` whose only content is the key.
3. **Upload it to your site's root.** On most frameworks that means the `public` or static folder. On a site builder, use its file hosting or its built-in IndexNow setting if it has one.
4. **Test it.** Enter your site and key in the IndexNow checker. It fetches `https://yoursite.com/<key>.txt` and checks that the file answers 200, that it contains exactly the key, and that it is served as `text/plain`.
5. **Send your first URLs.** Paste them into the tool to get a ready curl request, or use the formats below. The tool shows the request for you to run; it does not submit URLs itself, so you stay in control of what is sent.
6. **Automate it.** Ping on publish, update and delete from your CMS or deploy pipeline.

### Submitting one URL

A single URL can be sent with a simple GET request. URL-encode the page address:

```
https://api.indexnow.org/indexnow?url=https%3A%2F%2Fexample.com%2Fnew-page&key=YOUR_KEY
```

### Submitting many URLs

For several URLs, send a POST with a JSON body. One request can carry up to 10,000 URLs, all on the same host as the key:

```
curl -X POST "https://api.indexnow.org/indexnow" \
 -H "Content-Type: application/json; charset=utf-8" \
 -d '{
"host": "example.com",
"key": "YOUR_KEY",
"keyLocation": "https://example.com/YOUR_KEY.txt",
"urlList": [
"https://example.com/new-page",
"https://example.com/pricing"
]
}'
```

### What the response codes mean

| Code | Meaning | What to do | |
| 200 | OK: the submission was received | Nothing | |
| 202 | Accepted: received, key validation pending | Normal on a first submission; keep the key file in place | |
| 400 | Bad request: invalid format | Check the JSON, the encoding and the parameter names | |
| 403 | Forbidden: the key is not valid, such as the file or the key in it not being found | Run the IndexNow checker on your key file | |
| 422 | Unprocessable: URLs do not belong to the host, or the key does not match | Send only URLs on the key's host; check `www` versus no `www` | |
| 429 | Too many requests | Slow down; send changed URLs only, in batches | |

## When to ping, and when not to

- **Ping when a page is published.** New landing pages, blog posts, launch pages, docs.
- **Ping when a page changes meaningfully.** A new price, a rewritten section, new data. Not a typo fix or a timestamp change.
- **Ping when a page is deleted.** The protocol covers deleted URLs too, so engines recrawl and see the 404 or 410 sooner.
- **Do not ping every URL every day.** Resubmitting unchanged pages wastes requests, spends engines' [crawl budget](https://abacklaunch.com/glossary/crawl-budget) on pages that did not change, and can get you rate limited.
- **Do not ping URLs that are blocked or noindexed.** Check them against your rules with the [robots.txt tester](https://abacklaunch.com/tools/robots-txt-tester) first; there is no point asking an engine to crawl a page you told it to skip.

## Bing and IndexNow

Bing is the main reason to use IndexNow for most sites. Bing Webmaster Tools shows the URLs it received through IndexNow, alongside its other crawl and indexing reports, so you can confirm submissions are arriving. Many platforms already speak the protocol: several WordPress SEO plugins support it, Microsoft publishes an IndexNow plugin for WordPress, and Cloudflare's Crawler Hints feature sends IndexNow signals for sites on its network. If your platform does it for you, check that it is turned on and that the key file it created passes the checker.

For a custom stack (a Next.js app, a static site with a deploy hook), the pattern is small: after a page is saved or deployed, collect its URLs and send one POST, without letting a failure block the save. That is the pattern this site uses.

## Troubleshooting the key file

| Symptom in the checker | Likely cause | Fix | |
| The key URL answers 404 | The file is not at the root, or it is on a different host (www or not) | Upload to the root of the exact host you submit URLs for | |
| The file exists but does not contain exactly the key | Extra text, a different key, or your app returns its HTML shell for unknown paths | Serve the file as a real static file containing only the key | |
| Served as text/html instead of text/plain | A catch-all route or a CMS page is answering | Serve it as a static asset with a `.txt` extension | |
| The check redirects or times out | Redirect rules or bot protection on the root | Exclude the key file from redirects and challenges | |

Single-page apps are the most common culprit: the server answers every path with the same HTML and a 200, so the key URL "works" but contains HTML. The [HTTP header checker](https://abacklaunch.com/tools/http-header-checker) shows exactly what status and content type the URL returns.

## FAQ

### What is IndexNow?

IndexNow is an open protocol for telling search engines that a URL on your site was added, updated or deleted. You host a key file to prove ownership and send the changed URLs to an IndexNow endpoint, and every participating engine, including Bing, Yandex, Seznam, Naver and Yep, receives the submission.

### Does Google use IndexNow?

No. Google said in 2021 that it would test the protocol but has never joined, and it is not on IndexNow's list of participating search engines. For Google, keep an accurate XML sitemap, submit it in Search Console, and use URL Inspection for important new pages.

### How do I get an IndexNow API key?

You create it yourself. Choose or generate a string of 8 to 128 letters, digits and dashes, save it in a UTF-8 text file named after the key with a.txt extension, and upload the file to the root of your site. Then use the same key in every submission.

### How do I check if IndexNow is working?

Run an IndexNow checker on your site and key: it confirms the key file is live, contains exactly the key and is served as plain text. Then send a URL and look for a 200 or 202 response, and check Bing Webmaster Tools, which shows the URLs it received through IndexNow.

### Is IndexNow worth it?

For most sites, yes. It takes minutes to set up, costs nothing, and gets new and changed pages in front of Bing and other engines faster. Its limits are that Google ignores it and that a submission is a hint, not a guarantee of indexing.

### How many URLs can I submit with IndexNow?

Up to 10,000 URLs per POST request, all on the same host as the key. Submit only URLs that are new, have changed meaningfully or were deleted, rather than resubmitting your whole site.

## Set it up once, ping on every change

IndexNow is a ten-minute job with a lasting payoff for every engine except Google. Generate a key, upload the file, confirm it with the free [IndexNow checker](https://abacklaunch.com/tools/indexnow-tester), and wire the ping into your publishing flow. Then keep your sitemap honest for Google, and both lanes are covered.

## Related

- [App Store Optimization (ASO): Keywords, Title, Subtitle and Screenshots for iOS and Google Play](https://abacklaunch.com/blog/app-store-optimization-guide)
- [Broken Link Checker Guide: How to Find and Fix Broken Links, 404 Errors and Broken Backlinks](https://abacklaunch.com/blog/broken-link-checker-guide)
- [Core Web Vitals: LCP, INP and CLS Explained, How to Test Them and How to Improve Them (2026)](https://abacklaunch.com/blog/core-web-vitals-guide)
- [All founder guides](https://abacklaunch.com/blog)
