---
title: "Search Console 1,000-row limit: why totals and rows differ"
description: "Diagnose a Search Console table that stops at 1,000 rows or fails to match the chart total. Check filters, aggregation, and query privacy."
canonical_url: "https://gscdump.com/learn-google-search-console/limits/1000-row-limit"
last_updated: "2026-09-11"
---

A Search Console query table can show **1,000 rows** without listing every query behind the chart. Google says report exports contain [up to 1,000 representative rows](https://support.google.com/webmasters/answer/12919797?hl=en), while totals still include truncated data.

If the rows don't add up, first check what you're comparing. Downloading the same table again won't resolve a difference caused by privacy filtering or aggregation.

## A gap is a question to investigate

Suppose the chart shows **500 clicks**, while your downloaded query rows sum to **380**. These are illustrative numbers.

The difference is **120 clicks**, but you cannot label all 120 as “hidden keywords.” Several mechanisms can contribute, and a click count is not a count of distinct queries.

Google's [data documentation](https://support.google.com/webmasters/answer/96568?hl=en) identifies row limits and omitted rare queries as reasons chart totals can exceed visible rows.

## Check the comparison in this order

1. **Match the report settings.** Keep the same dates, search type, and filters on both sides. A saved file may reflect an earlier state.
2. **Check the table tab.** Pages and Queries represent different groupings. Google's [report setup guide](https://support.google.com/webmasters/answer/7576553?hl=en) explains why page-level aggregation can differ from property-level chart totals.
3. **Check the row count.** A table at 1,000 rows can be truncated. A shorter table still doesn't prove every query is visible.
4. **Check query privacy.** Search Console omits anonymized query text. It also stores top rows rather than every detail row, according to [Google's data documentation](https://support.google.com/webmasters/answer/96568?hl=en).

Keep the same checks when comparing a report with an API result. Changing the extraction method does not make unlike groupings equivalent.

## Filtering changes the question

A focused page or query filter can help you investigate a smaller slice. It does not prove that separate filtered exports reconstruct the entire original dataset.

Google notes that [anonymized queries behave differently when query filters are applied](https://support.google.com/webmasters/answer/17011259?hl=en). Record the filter beside the result instead of treating the new total as directly interchangeable with the unfiltered chart.

For example, use a page filter to investigate one landing page's visible queries. Describe the result as that filtered report, not a complete list of every search that reached the page.

## When you need more rows

The API can provide a larger selection than the interface, but Google still limits which rows it exposes. For method selection and pagination, continue with [Search Console export limits](/learn-google-search-console/limits/export-row-limits).

If the problem affects recent dates rather than the number of visible rows, check [data delay](/learn-google-search-console/limits/data-delay) before interpreting a missing day as zero traffic.

## Sitemap

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