---
title: "Search Console API rate limits and quota errors"
description: "Identify Search Analytics request and load quotas, check URL Inspection limits, and choose a useful response to quota errors."
canonical_url: "https://gscdump.com/learn-google-search-console/api/rate-limits"
last_updated: "2026-09-11"
---

A Search Console quota error can mean too many requests or too much query work. Check both before increasing retries.

Start by identifying the API resource, the Google account making requests, and the property being queried. A worker that stays below its own limit can still share quota with other workers.

## Search Analytics request quotas

Google documents these [Search Analytics quotas](https://developers.google.com/webmaster-tools/limits), checked on 11 September 2026:

| Scope                        | Limit                      |
| ---------------------------- | -------------------------- |
| One property, across callers | 1,200 queries per minute   |
| One user, across properties  | 1,200 queries per minute   |
| One project                  | 40,000 queries per minute  |
| One project                  | 30,000,000 queries per day |

For example, two jobs using the same Google account share that user's allowance, even if they query different properties. Track usage at the shared account and property level, rather than giving each job the full allowance.

## Low request count, expensive query

Search Analytics also has short-term load windows of 10 minutes and long-term load windows of one day. Google does not publish a numeric load budget you can calculate from a request body.

Long date ranges cost more. Grouping or filtering by page and query together is particularly expensive. Repeatedly fetching the same historical range wastes that budget.

If you hit a load limit, Google's guidance is to wait 15 minutes before trying again. If it persists even with one query in a 10-minute period, investigate the daily load limit.

A useful repair is to fetch smaller date ranges and reuse stored results. Remove page or query detail when the report only needs totals. The [query guide](/learn-google-search-console/api/query-builder) shows how the dimensions change the report.

## URL Inspection has a different allowance

For indexed URL inspection, the same [quota reference](https://developers.google.com/webmaster-tools/limits) lists:

| Scope        | Per minute | Per day    |
| ------------ | ---------- | ---------- |
| One property | 600        | 2,000      |
| One project  | 15,000     | 10,000,000 |

A property-level daily allowance matters when planning a crawl review. Inspect a chosen set of URLs with a clear question, and record when each result was obtained. The API reports the indexed version; it does not replace a live crawler.

Other resources have their own limits: 20 queries per second and 200 per minute per user, plus 100,000,000 per day per project. Check the resource before applying a Search Analytics scheduler to it.

## Choose a retry that can help

Keep the error response and the request context, excluding credentials. Distinguish a quota response from a [permissions error](/learn-google-search-console/api/authentication#when-access-stops-working) or an invalid request.

- If you burst requests, queue them and coordinate the workers sharing the allowance.
- If the query is expensive, reduce its scope before scheduling more copies.
- If you've exhausted a daily allowance, repeated short retries cannot restore it.
- If a failure is transient, use bounded retries with increasing delays and jitter. Stop after your chosen retry budget.

That last point is an implementation pattern, not a promise that every Google error will recover. Make the final failure visible to whoever depends on the report.

You can inspect project usage in the Google Cloud quota console linked from Google's reference. Keep your own per-property and per-user logs when several jobs share a project.

## Rows are a separate limit

A successful response with fewer rows than expected is not necessarily a quota error. `rowLimit`, pagination, privacy filtering, and internal row availability govern the data returned.

Follow the [export limits guide](/learn-google-search-console/limits/export-row-limits) for missing rows. Raising request throughput won't recover information Google doesn't expose.

## Sitemap

See the full [sitemap](/sitemap.md) for all pages.