indexing.io
How it works Pricing Blog Sign in

Submit & index · IndexNow API access

IndexNow API Key Setup and One API for Bulk Submission and Index Status

Calling the IndexNow API directly is not hard. Generate a key, put it in a text file at your domain root, and POST a JSON list of URLs to api.indexnow.org. A developer can wire that into a CMS publish hook in an afternoon, and for one site that is often all you need.

Submit · monitor coverage · official methods only

Try

Indexed pages, week by week

Coverage report

78%

Coverage, up from 64%

41 min

Avg time to index

Week 1Week 4Week 8
Submitted through official channels Left to crawl on its own

What a check returns

Noindex Blocked in robots.txt Canonical elsewhere Ready to submit

Every URL gets a plain-English reason when a search engine will not index it, and the rest go out through the official channels.

Paste your sitemap and we count every URL it lists, then check a sample of your pages before we submit through the official Google Indexing API and Bing IndexNow.

We could not check that one

Crawlable

checked

Submitting via

Ready to submit

Need a fix first

We fetch the address you paste and read what a crawler sees · nothing is submitted to a search engine from this check

Index status itself comes from Search Console, which you connect on a plan · official Google Indexing API · Bing IndexNow · verified sitemaps · no spam, no PBNs

In short

The IndexNow API is a single HTTP endpoint that tells Bing, Yandex, Seznam, Naver and Yep a URL changed. You need a key file on your domain and a POST of up to 10,000 URLs. It confirms receipt, not indexing. Indexing wraps it in one API that also submits to Google and returns index status per URL.

The work starts when the integration has to keep working across many sites, for months, with someone asking whether it paid off. Keys disappear in migrations. One URL from the wrong host gets a whole batch rejected with a 422. A 429 shows up during a product import and nobody sees it. And a 200 response only means the engine received the list, so the question the business actually cares about, which of these pages are now in Bing and Google, is still unanswered.

Indexing gives you one authenticated API for that whole loop. You keep calling a single endpoint from your stack. We verify the IndexNow key for each site, filter out URLs from other hosts, submit to IndexNow and to Google through the Search Console property you connect, and record what happened to every URL afterward.

Google API IndexNow Sitemaps Coverage Re-crawl

Official methods only

White hat · no spam, no PBNs

Why it works

What your team gets with IndexNow API access

Key setup checked per site

We generate a 32-character IndexNow key for each site, tell you where the file goes, and fetch it as an anonymous visitor before the first submission. A login wall, firewall challenge or redirect is caught here, not as a 403 later.

One call, two engines

POST a list of URLs once. The same request goes to IndexNow, which shares it with every participating engine, and to Google through the Search Console property you connected. The response tells you how many each side accepted.

Status you can poll

A second endpoint returns every URL on a site with its crawl status, Google index state, Bing state, when it was submitted to each engine and how long it took to get indexed. Your dashboard or client report reads from that, not from a log file.

What it handles

Submitted, monitored and fixed, automatically

Indexing submits your URLs through the official Google Indexing API, Bing IndexNow and clean XML sitemaps, watches coverage across both engines, and flags any page that drops out with a plain-English reason so you can resubmit and get it back.

  • Bearer key issued in the dashboard, stored only as a hash on our side
  • Up to 500 URLs per submit call, filtered to the site's own host first
  • IndexNow key verified before anything is sent
  • Google submission through your own Search Console property
  • Per-URL Google and Bing index status with time to index
  • Plain-English reasons for 403, 422 and 429 responses
Coverage Live

Not indexed yet

/blog/seo-guide-2026 is discovered but not indexed

crawled, not indexed resubmit

thin content signal, queued for re-crawl via the Indexing API

1 Submitted to Google Indexing API OK
2 Pinged Bing via IndexNow OK
Google + Bing · one status Official · white hat

Why Indexing

One place to submit, monitor and fix coverage

Not a black-hat indexer that risks your site, not a free checker that only tells you the bad news. Indexing unifies official submission and live coverage monitoring, the white-hat way, across Google and Bing.

Submits the official way

Bulk-submit through the Google Indexing API, Bing IndexNow and clean XML sitemaps. We speed discovery and re-crawl using methods the engines support, never spam, PBNs or black-hat tricks.

Monitors coverage live

You do not refresh a search bar one URL at a time. Indexing watches which pages are in Google and Bing, catches anything that drops out, and tracks time-to-index across your whole site.

Diagnoses and resubmits

Every non-indexed page comes with a plain-English reason, then auto-resubmits through the official API so it gets another shot. Google still decides, but nothing waits in the dark.

At a glance

Calling IndexNow yourself versus calling it through Indexing

Both are legitimate. The direct API is free and enough for one site. The difference is everything that happens before and after the POST.

What you need IndexNow API called directly Indexing API
Key generation and hosting You generate a key and host the file yourself We generate the key; you host the file, and we verify it before the first submission
URLs per request Up to 10,000 per POST, according to IndexNow.org Up to 500 per call, split and filtered by host for you
URLs from the wrong host The whole batch is rejected with 422 Removed before sending, so the rest still go through
Google Not covered, Google does not use IndexNow Submitted through the Google Search Console property you connect
Index status after submission Not returned, a 200 only confirms receipt Returned per URL for Google and Bing, with time to index
Many sites One key and one integration per domain One API key for every site on your subscription
Price Free Agency plan, $119 a month billed annually

How do I use the IndexNow API?

Generate a key of 8 to 128 characters (letters, numbers and dashes), save it in a UTF-8 text file named after the key, and host that file at your domain root. Then send a GET request with one URL and the key, or a POST with a JSON body holding host, key, keyLocation and urlList to https://api.indexnow.org/indexnow. A 200 or 202 response means the URL list was received.

With Indexing, the key step happens when you connect the site, and from then on you call our submit endpoint with the URLs. We send the IndexNow request with the right host, key and key location, and we send the same URLs to Google in the same call.

How do I get an IndexNow API key?

There is no account to register with. The key is any string you create that meets the format, and Bing's IndexNow page has a generate button that produces one for you. What makes it valid is the file: engines fetch https://yourdomain.com/your-key.txt and check that it holds the same key, which proves you control the domain.

Indexing creates a random 32-character key for each site you add and shows you the exact file name and location. We then request the file before the first submission and again whenever an engine refuses a batch, so a key that vanished in a redesign is caught on the day it happens.

  • Key length 8 to 128 characters
  • Characters a to z, A to Z, 0 to 9 and dashes only
  • File named after the key with a .txt extension
  • File at the root, unless you pass keyLocation for a subfolder

Is the IndexNow API free?

Yes. IndexNow is an open protocol and the participating engines do not charge for submissions. What you pay for with Indexing is the work around it: key verification, host filtering, the same submission to Google, per-URL index status, and one API for many client sites. API access is part of the Agency plan at $119 a month billed annually, or $239 month to month.

How many URLs can I submit to the IndexNow API at once?

IndexNow.org allows up to 10,000 URLs in one POST, and you can mix http and https URLs from the same host. A submission is all or nothing: if one URL in the list belongs to a different host, the engine answers 422 and none of the batch is accepted.

Our submit endpoint takes up to 500 URLs per call. We drop URLs that do not belong to the site first, send the rest, and count only accepted URLs against your monthly allowance. A rejected batch costs nothing.

What do IndexNow API response codes mean?

IndexNow.org documents six. 200 means the URL was submitted successfully. 202 means it was received and key validation is pending, which is normal the first time an engine sees your key. 400 is a malformed request. 403 means the key is not valid, usually because the key file cannot be fetched. 422 means a URL does not belong to the host or the key does not match. 429 means too many requests, which the protocol describes as potential spam.

Our API passes the meaning back in plain English in the message field, for example that the key file is not public or that Bing is rate limiting this host, so the developer reading the response knows what to fix without looking up the code.

Does the IndexNow API work for Google?

No. Google does not participate in IndexNow, so an IndexNow submission reaches Bing and the other partner engines but not Google. For Google, the routes are an accurate sitemap, internal links, and the Google Indexing API for verified property owners.

To be straight about the last one: Google documents its Indexing API for pages with JobPosting or BroadcastEvent in a VideoObject. Our API submits through it from the Search Console property you connect, respects Google's default quota of 200 publish requests a day per project, and then reads the real index status, because a submission is never a guarantee from any engine.

The three endpoints

Every request carries your key as a Bearer token in the Authorization header. A missing or unknown key returns 401, a plan without API access returns 403, and a lapsed subscription returns 402, the same gate the dashboard uses. Requests are limited to 120 a minute.

GET /api/v1/sites lists every site on the subscription with its coverage summary: URLs known, crawlable, blocked, indexed and not indexed in Google, the Bing equivalents, average time to index and the last scan time. GET /api/v1/sites/{id}/urls returns up to 1,000 URLs with their state. POST /api/v1/sites/{id}/submit takes a urls array and returns how many went to Google and how many to IndexNow.

Who uses the Indexing API

Agencies that manage IndexNow for dozens of client sites and want one integration instead of one per domain. Developers building programmatic or headless sites who publish thousands of pages and need to know which ones landed. In-house teams that feed index status into their own dashboards or client reports instead of exporting Search Console by hand.

If you run one site and only need Bing to hear about new posts, call IndexNow directly or use a plugin; it is free and it works. The API earns its price when you have many sites, care about Google too, and need proof of what was indexed.

Keep reading

Good questions

Questions about indexnow api access

The shared endpoint is https://api.indexnow.org/indexnow, and each participating engine also has its own, such as Bing's. A submission to any one of them is shared with all the others, so you only need to send each URL once.
At the root of your domain, named after the key with a .txt extension, for example https://example.com/your-key.txt. A file in a subfolder only authorizes URLs inside that folder, a common cause of 403 errors.
Each host needs its own key file, because ownership is proven per domain. With Indexing you still use a single API key for your account, and we manage a separate IndexNow key for each site behind it.
No. A 200 or 202 only confirms the engine received the URL. IndexNow.org says submitting a URL does not guarantee immediate indexing. Our API returns the index status per URL afterward, for Google and Bing.
No. IndexNow only accepts URLs verified by a key file on the same host, and Google only accepts Indexing API calls from verified property owners. The Indexing API works for sites you own or manage for clients.
The Agency plan, $119 a month billed annually or $239 month to month, with about 150,000 URLs a month across many sites, white label reports and priority support.
There is no official library, because the protocol is one HTTP request. Any HTTP client works. Our API is the same: plain JSON over HTTPS with a Bearer token, so a few lines of requests or fetch are enough.

Explore more

More ways teams get every page indexed

Wire it once, cover every site

Create an Agency account, add your sites, issue an API key in the dashboard and point your publish hook at one endpoint. Indexing handles the IndexNow keys, the Google submission and the index status that proves it worked.

See pricing

Google Indexing API · Bing IndexNow · sitemaps · coverage monitoring · official methods only