Why does a Search Console export stop at 1,000 rows, and how do you get the rest?

A Search Console export stops at 1,000 rows because Google truncates it to 1,000 rows of representative examples, the same cap the report's table has. More rows come from the Search Console API, which returns up to 25,000 per request, or from a BigQuery bulk export, which Google says gives the most complete list of queries.

• Google says an export is truncated to 1,000 rows of representative examples, while the totals shown are actual totals (Google, Search Console Help, read 30 October 2026).
• The Search Console API takes a rowLimit from 1 to 25,000 and defaults to 1,000, so a request that omits it returns at most 1,000 rows (Google, Search Console API reference, read 30 October 2026).
• The Search Console API guide describes a maximum of 50,000 rows of data per day per search type (Google, Search Console API guide, read 30 October 2026).
• The first BigQuery bulk export arrives up to 48 hours after configuration and covers the day of the export, and Google points to the API or the reports for earlier days (Google, Search Console Help, read 30 October 2026).
• Penlid's hidden query share tool treats a queries table of exactly 1,000 rows as cut by the limit, because the file cannot show whether rows were dropped (Penlid, hidden query share tool, read 30 October 2026).

Where does the 1,000-row limit apply, and where does it not?

The 1,000-row limit applies to the Performance report's table and to the file you download from it, while the API, the Data Studio (formerly Looker Studio) connector and the BigQuery bulk export follow their own rules. Google's troubleshooting page says The table can display a maximum of 1,000 rows, and its export page says Data is truncated to 1,000 rows of representative examples of your data. Google's 2022 post says the limit on what can be displayed or exported comes from limitations related to serving latency, storage, processing resources, and others; none of the pages we read says why the figure is 1,000.

The connector row in this table comes from a 2022 post, and we found no current Google page that repeats it, so treat it as dated.

Why can the table add up to less than the chart?

The table can add up to less than the chart because the chart counts rows that the table leaves out: rows beyond the limit, rows Search Console does not store or show, and anonymized queries. Google says anonymized (rare) results are omitted from the table but stay in the chart totals unless a query filter is applied, and that Search Console stores and shows only the most important data rows. The export page adds that Totals shown are actual totals, not totals with any row limits applied, so the limit trims rows, not totals.

The Google pages we read do not say how many rows are cut, and the file cannot show how the gap divides between those causes. So a table under 1,000 rows can still be missing rows; that step is our reasoning from Google's wording, not a Google statement about any particular table.

An export reflects the report with any filters or special grouping applied. In our reading, each filtered view is therefore its own table with its own cap, and exporting country by country can return more rows in total; we found no Google statement that such slices add up to every row.

How do you get more than 1,000 rows from the Search Console API?

You get more than 1,000 rows from the Search Console API by raising rowLimit, which accepts up to 25,000, and paging with startRow until a response comes back empty. The API reference gives the range: Valid range is 1–25,000; Default is 1,000. Google's API guide says to keep going until you reach the last page (a response with 0 rows). To keep an API pull comparable with an export:

1. Use the same dates, search type and filters as the export.
2. Set rowLimit to 25,000, then raise startRow by 25,000 each time until a response has 0 rows.
3. Request totals separately. Google says accurate counts need the page and query dimensions left out, and that asking for more detail means its system may drop some data.
4. Add up the clicks and impressions of the rows you received and compare them with those totals. That comparison is our method, not a Google procedure.

The API still has a ceiling. Google's guide describes a maximum of 50K rows of data per day per search type, and the API reference says a query does not guarantee to return all data rows but rather top ones. An API pull therefore gets you more than the export, not necessarily every row.

What does the BigQuery bulk export add, and what does it cost?

The BigQuery bulk export adds a growing set of tables in your own Google Cloud project, with storage and query costs above a free usage level. Google says The most complete list of queries can be exported using bulk data exports, and three details decide whether it fits your case.

• It is not retroactive. Google says The first export includes data for the day of the export; it arrives up to 48 hours after configuration, and for earlier days Google points you to the API or the reports. Start early if you want history; the guide to keeping Search Console data older than 16 months covers the options.
• Rows can repeat a key. Google's table reference mentions table rows with repeated keys, so add up clicks and impressions by key before you compare them (our advice).
• Anonymized queries are the exception. The overview covers the data with the exception of anonymized queries, while the table reference flags rows for rare queries and the query guide says such a query is reported as a zero-length string. The pages we read do not say whether those rows hold all of an anonymized query's clicks and impressions.

How do you measure what your export left out?

You measure what an export left out by subtracting the total of its query rows from the chart total, separately for clicks and for impressions, and the free hidden query share tool does that from the export itself, in your browser. Four steps:

1. Export without a query, page or search appearance filter. In Search Console open Performance, then Search results, choose the dates, and use Export, then Download CSV. Filters on search type, country or device are fine.
2. Keep the whole ZIP. It holds the daily table (Dates.csv, or Chart.csv in newer exports) and Queries.csv. Google's file has no total row, so the tool sums the daily rows to get the chart total, and it refuses a weekly, monthly or Compare table. Search Console keeps 16 months (Google, Analytics Help), and 16 × 31 = 496 rows is under the cap, so the daily table cannot be cut (our arithmetic).
3. Read the gap. It is one minus the query rows' total over the chart total. A queries table that adds up to more than the chart is refused.
4. Read each share as an upper bound. The gap mixes anonymized queries with rows Google does not show, so the tool labels it an upper bound even under 1,000 rows, and it treats a table of exactly 1,000 rows as cut by the limit.

The share is not a count of anonymized queries; the guide to how much of your traffic is in anonymized queries explains the difference.