Google Search Console’s limits, and how to work around them
16 months of history, 1,000 rows in a table, hidden queries, one property at a time. What Search Console holds back, in Google’s numbers, and what to do.
Search Console is the only place you get Google’s own figures for your site, and it’s free. It’s also built around one property and a few months of attention. If you run several sites, or need to answer a question about last year, you hit its limits quickly.
Here they are, with Google’s numbers, checked on 6 November 2026. We’re building Owlseen around some of these limits, and it isn’t released, so nothing below depends on it.
The limits at a glance
| Limit | What Google says | What it means for you |
|---|---|---|
| History | The Performance report covers 16 months | No comparison with two years ago unless you stored it |
| Rows in the interface | 1,000 rows you can export | The long tail of a big site isn’t in the table |
| Rows through the API | 50,000 rows a day, per site, per search type, at most 25,000 per request | More than most sites need, but not everything |
| Hidden queries | Queries not issued by more than a few dozen users over two or three months are anonymised | Part of your traffic never shows a query |
| URL inspection | 2,000 a day and 600 a minute, per site | You can’t check every page of a big site daily |
| Properties | 1,000 per account | Rarely a problem, but each one is opened on its own |
Why rows and totals don’t add up
Add up every row in the Queries table and you’ll get less than the total on the chart. That’s not a bug. Anonymised queries are included in chart totals unless you filter by query, and their rows are hidden.
Two other things catch people out:
- Aggregation differs. The chart aggregates by property, and so do tables by query, country, device or date; tables by page or search appearance aggregate by page. So the same two results on one query count as one impression in one view and two in another.
- Position is the topmost one. Google reports the topmost position occupied by a link to your property or page, averaged across queries. It isn’t a rank anyone actually saw at a given moment.
Dates are in Pacific Time, and the newest data is preliminary and can change for a few hours. If you compare with a report in your own time zone, expect a slight shift at the edges of each day.
Keep an eye on the data anomalies page
Google publishes a list of known data problems, and it matters more than most people realise. The one to remember now: a logging error meant Search Console didn’t accurately report impressions from 13 May 2025 until 27 April 2026. Impressions, click-through rate and average position were affected. Clicks weren’t.
So if you’re comparing this autumn with last autumn, trust the clicks and be careful with the rest. The same page lists two days, 28 February and 1 March 2026, that are missing from bulk exports for some properties and won’t be recovered.
How to get more out of it
Store it yourself, starting today. Google’s own advice for going past 16 months is to use the API or bulk exports to keep the data in your own systems. The sooner you start, the longer your history. Nothing recovers what you didn’t store.
Query one day at a time. Google’s guide to getting all your data says to run one day’s query, then raise startRow by 25,000 until a page comes back empty. It also warns that grouping by page or query may drop some data. For accurate totals, leave those two dimensions out.
Use the bulk export on a big site. The bulk data export to BigQuery isn’t affected by the daily row limit. It still leaves out anonymised queries, it doesn’t backfill what came before you set it up, and BigQuery storage and queries are charged above a free level. Google itself says it’s mostly useful for sites with tens of thousands of pages.
Choose your property type deliberately. A Domain property covers every subdomain and protocol, and verifies by DNS only. A URL-prefix property covers just what starts with that prefix. Since limits apply per property, large sites often add URL-prefix properties for their main sections, to see more rows of each.
What’s newer, and what it still doesn’t give
The Generative AI performance report, open to all websites since 31 August 2026, counts impressions in AI Overviews and AI Mode. Its help page describes impressions by page, country, date and device: no queries and no clicks. The branded and non-branded filter isn’t offered to sites with few impressions, and its history starts in March 2025.
The limit nobody lists: one property at a time
As of November 2026, we found no view in Search Console across your properties. You pick one from a menu. Bing Webmaster Tools is a separate product, though its API key is per user and works for all your verified sites, which makes it the easier of the two to script.
With a handful of sites, a weekly round of tabs is fine. Past that, you need one of three things: a spreadsheet fed by the API, a Looker Studio report per site, or a tool that reads the APIs for you. That’s the gap Owlseen’s first version is being built for, keeping a daily copy so the history doesn’t run out. It isn’t released yet, so until then, the first of those three is the one to start today.
Next, the signals you can’t see in a total: content decay, and what the indexing statuses really mean.