indexing.io
How it works Pricing Blog Sign in

Check & monitor · Index checker API

Google Index Checker API for Bulk Index Status Checks Across Agency Sites

Most people who search for an index checker API already have the list. It is a sitemap with 40,000 product URLs, a spreadsheet of client pages, or a nightly export from a CMS, and the job is to find out which of those URLs Google actually has, without a person opening Search Console and inspecting them one by one.

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

A Google index checker API tells your code whether each URL is in Google's index, so you stop pasting URLs into Search Console one at a time. There are two kinds: APIs that read Google's own URL Inspection data for sites you have verified, and APIs that run site: searches against any URL. Indexing does the first, across every site on your plan, and also submits the missing URLs. If you need to check backlinks on sites you do not own, a site: based API is the right tool.

The catch is that "is this URL indexed" can be answered two very different ways, and vendors rarely say which one they use. One way asks Google directly through the Search Console URL Inspection API, which only works for properties you have verified but returns Google's own verdict, including the reason a page was left out. The other way runs a site: or inurl: search for the URL and reports whether it came back, which works on any URL on the web but is an inference from search results rather than an answer from the index.

Indexing is built on the first method. You connect each site through Search Console, we scan the sitemap, read the index state of every URL from Google, record when each one first appeared, and expose all of it through a REST API on the Agency plan. The same API submits the URLs that are missing, so the check and the fix live in one integration instead of two vendors and two bills.

Google API IndexNow Sitemaps Coverage Re-crawl

Official methods only

White hat · no spam, no PBNs

Why it works

What your team gets with Index checker API

Google's verdict, not a guess from search results

Index state comes from the Search Console URL Inspection API, so a missing page arrives with Google's own coverage state, such as Crawled, currently not indexed, rather than a bare yes or no.

Every site on the plan behind one key

One Bearer key lists every site on the subscription with totals for known, crawlable, blocked, indexed and not indexed URLs, plus the average time to index.

The check and the fix in one call path

The same API that reports a URL as not indexed accepts it back for submission through Google's Indexing API and IndexNow for Bing, up to 500 URLs per request.

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.

  • Returns index state, coverage state and last check time for every URL, as JSON
  • Summarises each client site: known, crawlable, blocked, indexed and not indexed counts
  • Records time to index per URL, from first submission to first seen in the index
  • Submits missing URLs to Google and Bing from the same key, within your plan allowance
  • Stops answering the moment a subscription lapses, so a leaked old key is worthless
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

Google index checker APIs compared, by how they actually check

Figures read from each vendor's own site in September 2026. The method column matters more than the price column: it decides which URLs a tool can check at all and how much you should trust a negative answer.

API How it decides a URL is indexed Which URLs it can check Published pricing
Google URL Inspection API Asks Google's index directly and returns the coverage state Only properties you have verified in Search Console Free. 2,000 queries a day and 600 a minute per property, one URL per call
Indexing (this API) Reads the URL Inspection API for every URL in your sitemaps, rechecked at most once a day Sites you connect through Search Console Agency plan, $119 a month billed annually, about 150,000 URLs a month, includes submission
IndexedAPI Runs a site: and an inurl: search and counts the URL as indexed if either returns it Any URL, including backlinks on sites you do not own Pay as you go, from $0.0007 per URL, 250 trial credits, credits do not expire
IndexCheckr Its own Google checks, with recurring rechecks and alerts Any URL, including backlinks Credits only: $15 for 2,000 checks down to $1,300 for 1,000,000, one shared pool for the team
indexchecker.io Says it queries Google's index and returns JSON with a timestamp Any URL Tiers of 1,000, 10,000 and 50,000 or more calls a month. Prices not shown on its API page

Is there an API to check if a URL is indexed by Google?

Yes, Google publishes one, and it is free: the URL Inspection method of the Search Console API. You send it a URL and the property it belongs to, and it returns the same verdict you would see in the Search Console interface, including whether the URL is on Google, the coverage state, the last crawl time and the canonical Google selected. Google publishes the quota as 2,000 queries per day and 600 per minute for each property.

The limits are what push most teams to a paid layer. It inspects one URL per call, there is no batch endpoint, and it only answers for properties you are a verified user of. For a single site with a few hundred pages that is plenty. For an agency with thirty client sites and a combined 200,000 URLs, somebody has to write the scheduler, rotate across properties, store the history, and decide which URLs to recheck first. That orchestration is the product you are actually shopping for.

There is one thing the Search Console API cannot do at all, and it surprises people: no endpoint in it submits a URL for indexing. It reads, and it manages sitemaps, but it will never push a page back to Google. That is why a checker on its own only gets you a longer list of problems.

  • Free, from Google: the URL Inspection method of the Search Console API.
  • Published quota: 2,000 queries a day and 600 a minute per property.
  • One URL per call, verified properties only, no batch endpoint.
  • No Search Console endpoint submits a URL for indexing.

Site operator checks versus the URL Inspection API, which should you trust?

They answer slightly different questions, and choosing the wrong one produces confident wrong answers. A site: or inurl: check asks whether Google will show this URL for a search that targets it. The URL Inspection API asks whether this URL is in Google's index. Most of the time the answers agree. When they disagree, it is usually because a page is indexed under a different canonical, or because search results for operator queries are not a complete listing of the index.

IndexedAPI is unusually candid about its method, which is a point in its favour: it runs both a site: and an inurl: search and counts the URL as indexed if either one returns it. Running two tests and accepting either is a reasonable way to cut false negatives, and it works on any URL anywhere, which the URL Inspection API never will.

So the choice follows from whose URLs they are. For pages on sites you own or manage, read Google's own verdict, because it tells you why a page is missing and not just that it is. For backlinks on other people's sites, you have no Search Console access by definition, so a search-based checker is the only option, and it is a good one.

  • URLs you own or manage: use the URL Inspection API and get the reason as well as the answer.
  • Backlinks on sites you do not own: only a search-based checker can see them.
  • A page indexed under a different canonical can fail a site: check and still be in the index.
  • Ask any vendor which method it uses before you trust its negatives.

What does the Indexing API return for each URL?

Two read endpoints and one write endpoint, all authenticated with a Bearer key you issue from the dashboard. GET /api/v1/sites lists every site on the subscription with its sitemap, whether Search Console is connected, and counts for known, crawlable, blocked, indexed and not indexed URLs, plus the average time to index in minutes and the time of the last scan. It also returns your plan allowance and how many URLs have been submitted to Google and to IndexNow this period.

GET /api/v1/sites/{id}/urls returns the per URL detail, up to 1,000 rows per call: the crawl status and its plain-English label, the reason a URL is not crawlable, the index state, Google's coverage state wording, when it was last checked, when it was submitted to Google and to IndexNow, and the measured time to index. POST /api/v1/sites/{id}/submit takes up to 500 URLs and sends them to Google's Indexing API and, where your IndexNow key is verified, to Bing.

Requests are limited to 120 a minute per client, which is far above what a nightly sync needs. A key only works while the subscription on it is active, so an old key in a forgotten script stops answering instead of quietly leaking client data.

  • GET /api/v1/sites: per site totals, allowance and submissions this period.
  • GET /api/v1/sites/{id}/urls: per URL index state, coverage state and time to index.
  • POST /api/v1/sites/{id}/submit: up to 500 URLs to Google and IndexNow.
  • Bearer key from the dashboard, 120 requests a minute, dead the day a plan lapses.

How much does a bulk index checker API cost?

It depends almost entirely on what you are paying for, so compare like with like. Search-based checkers price per check. IndexedAPI advertises rates as low as $0.0007 per URL. IndexCheckr sells credits from $15 for 2,000 checks, which is $0.0075 a check, down to $1,300 for 1,000,000, about $0.0013. At those prices, checking 100,000 URLs once costs somewhere between about $70 and $750, and a monitoring schedule multiplies that by every recheck.

An inspection-based service prices differently because the checks themselves come from Google's free quota. What you pay for is the scheduling, storage, history, alerting and submission around them. Our Agency plan is $119 a month billed annually, covers about 150,000 URLs a month across multiple sites, and includes the submission endpoint and white-label reports.

The honest break-even: if you mainly check backlinks on third-party sites, a per-check API will be cheaper and is the only kind that can see them. If you are monitoring your own or your clients' sites and want the missing pages pushed back automatically, paying per check for something Google gives you free is the expensive path.

  • IndexedAPI: from $0.0007 per URL, credits do not expire.
  • IndexCheckr: $0.0075 per check at $15, about $0.0013 at $1,300.
  • Checking 100,000 URLs once: roughly $70 to $750 on per-check pricing.
  • Indexing Agency: $119 a month billed annually, about 150,000 URLs a month, submission included.

Keep reading

Good questions

Questions about index checker api

Yes. The URL Inspection method of the Google Search Console API returns Google's own index verdict for a URL, including the coverage state and last crawl. It is free, allows 2,000 queries a day and 600 a minute per property, inspects one URL per call, and only works for properties you have verified.
Yes, with a search-based checker that runs a site: or inurl: query for the URL, such as IndexedAPI or IndexCheckr. That is the only way to check backlinks on sites you do not own. Indexing reads Google's own inspection data instead, so it needs each site connected through Search Console.
Google publishes a quota of 2,000 queries per day and 600 per minute for each Search Console property. Because the limit is per property, an agency with twenty verified client sites has twenty separate daily allowances, which is why a scheduler that spreads checks across properties matters more than raw speed.
No. The Search Console API reads performance and inspection data and manages sitemaps, but none of its endpoints submits a URL for indexing. Indexing adds a submit endpoint that sends URLs to Google's Indexing API and to Bing through IndexNow, within your plan allowance.
API access is part of the Agency plan, $119 a month billed annually or $239 month to month, which covers about 150,000 URLs a month across multiple sites and includes white-label reports and priority support. You issue the key from the dashboard, and it stops working if the subscription lapses.
Each URL is re-inspected at most once a day, with never-checked URLs first and then the oldest checks, and every row carries its checked_at time so your code can decide how much to trust it. Time to index runs from our first submission of a URL to the first check that finds it indexed.
A checker only reports. Submission can speed up discovery of a page Google has not fetched yet, but nobody can force Google to index a page it crawled and declined. The API returns Google's coverage state so you can tell those two cases apart before spending anything on them.
No. Google's Indexing API sends notifications that a URL was added or removed; it does not report index status. Google documents it for pages with JobPosting structured data or a BroadcastEvent in a VideoObject, with a default quota of 200 publish requests a day per project.

Explore more

More ways teams get every page indexed

Put index status for every client URL into your own dashboards.

Connect your sites, issue a key, and pull Google's verdict for every URL as JSON, then send the missing ones back through Google and Bing from the same integration.

See pricing

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