ToolsThatRank / API limits
Planner from Google's published limits
Search Console API row limit planner
Enter the days of data, the number of search types and the rows that you expect per day for each type. The planner shows the number of searchanalytics.query requests at 25,000 rows per request. It flags a day above the 50,000 row maximum, and it gives the time at a steady rate of 1,200 queries per minute.
By Michael Lip, an independent full-stack consultant who builds and runs ToolsThatRank.
The limits here are Google's published ones. The interface export stops at 1,000 rows. One API request returns at most 25,000 rows. The API exposes at most 50,000 rows of data per day per search type. The per-site and per-user quotas are 1,200 queries per minute each. The four sources are linked at the bottom of this page.
What each limit counts
Interface export caps at 1,000 rows
Google states that the maximum you can export through the Search Console interface is 1,000 rows of data. For more rows, use the API.
Each API request caps at 25,000 rows
The rowLimit valid range is 1 to 25,000, and the default is 1,000. To get
the next rows, send the same query again with a higher startRow value.
The API exposes 50,000 rows per day per search type
Google states that the Search Analytics method exposes a maximum of 50,000 rows of data per day per search type, sorted by clicks. This data limit is separate from the API usage quota. Google also states that the limit may not be reached in all cases. Google's bulk data export to BigQuery is not affected by this daily row limit, but it leaves out anonymized queries.
Quotas are a ceiling, not a promise
The per-site quota and the per-user quota are each 1,200 queries per minute. The per-project quota is 40,000 queries per minute and 30,000,000 queries per day. A short-term load quota (10 minute chunks) and a long-term load quota (1 day chunks) also apply. Queries grouped or filtered by page or query cost more load. The load quota can stop a job before the QPM limit.
How the counts are computed
For each day and each search type, the planner takes the smaller of your rows per day and 50,000. It divides that number by 25,000 and rounds up. This gives the requests per day and type. It multiplies that by the days and by the search types. The time is the number of requests divided by 1,200 per minute. This is the time at a steady rate at the QPM quota. It is not the shortest possible time, and it is not a promise.
Google's sample code runs one query for each day of data. It pages with
startRow in steps of 25,000 until a response has 0 rows. That last empty
response is one more request for each day and type. The planner shows that total too.
ToolsThatRank sells the pipeline that produced this page.
No ranking, traffic, or revenue outcome is promised.
The limits quoted are Google's documented numbers and may change; the Google documentation pages linked below are the source of record.
The example inputs are not data from a real property. Enter your own numbers.
