Over the quota, or checking pages outside your property? SpeedyIndex checks Google index status for any URL list.
URL Inspection API

URL Inspection API limits: 2,000 inspections per property per day

The URL Inspection API gives you Google's own answer to "is this page indexed?", but only within a budget. Google documents a limit of 2,000 inspections per day for each property, plus a per-minute cap. If you plan around those numbers, the API covers most needs for your own site. If you ignore them, the check stops halfway through the list.

The documented limits

Google's usage limits page for the Search Console APIs lists the following quotas for URL Inspection:

"Site" here means the Search Console property you pass in the siteUrl field. The project limits are set so high that the per-site limit is the one you will meet first.

URL Inspection API quotas: 2,000 per day and 600 per minute per site, 10 million per day and 15,000 per minute per project
The per-site quota is the one that shapes your plan; the project quota rarely matters.

The scope rule that matters more than the quota

The reference for the urlInspection.index.inspect method says the inspected URL must be under the property specified in siteUrl. In practice that means:

So the 2,000-per-day question only applies to your own pages. For third-party URLs the limit is effectively zero, and you need a different tool. One option is described in this API reference for checking index status of any URL list.

Planning 2,000 inspections a day

Two thousand a day is about 14,000 a week. For a blog or a small store that is more than enough to inspect every page regularly. For a large catalogue it is not, so you need to decide which URLs earn a check.

  1. New URLs first. Pages published in the last few days are the ones most likely to change status.
  2. Changed URLs next. Pages with new titles, new content or new canonical tags.
  3. Revenue and landing pages. A rotating sample of the URLs that bring traffic or sales.
  4. Everything else on a slow cycle. Spread the long tail over weeks instead of trying to cover it daily.

The per-minute cap of 600 means a single burst can use a large part of the daily budget in a few minutes. Pace requests evenly and stop for the day when you reach your own ceiling, rather than letting the API return quota errors.

Reading the result correctly

The inspection result includes an index status section with a verdict and a coverage state. Two details are easy to miss:

When the quota is not enough

If your own site produces more URLs than the quota can cover, check whether each Search Console property you have verified reflects how the site is organised. Teams sometimes verify URL-prefix properties for large sections. Google's limits page counts quota per site, but it does not promise that adding properties raises your total, so treat that as something to test on a small scale before relying on it.

The other route is to keep the URL Inspection API for the URLs where its detail matters, and use a bulk checker for simple indexed / not indexed status across the rest. The bulk index check script on this site is built to swap between data sources without changing the rest of the pipeline.

Guides on this site

FAQ

Is the 2,000 limit per property or per Google account?

Google lists it as a per-site quota, where the site is the property in siteUrl. The separate project quota applies to all calls made from one Google Cloud project.

Can I inspect a backlink with the URL Inspection API?

Only if the page is under a property you own. A link on another domain is out of scope.

Sources