What a SEOKit export contains and why it may have fewer rows than expected

Most “missing rows” are limits set by Google, not by SEOKit. An export holds the rows left after your active filters, up to what Google returns: 1,000 rows from the Search Console interface, and up to 50,000 rows a day per site and search type through the API that SEOKit uses (Performance data: filtering and limits). Anonymized queries are never rows, so a sum of the rows is lower than the total.

Pick the right export

Copy, CSV, HTML report and PNG take what the report shows. GSC Full Export is the tool for large extracts: it pages through the API 25,000 rows at a time and stops at 50,000 rows for a period. If a file is smaller than you expected, check the active filters first. Default filters and a branded or non-branded split apply to exports too, so open Default Filters in the account menu.

Dimensions and the daily split

Every extra dimension multiplies the rows, so query and page together reach the 50,000 ceiling much sooner than query alone. When your request has no query or page, for example only countries, devices or search appearance, Google lets you view and export everything.

To get more from a long period, add the date dimension and switch on the daily partition. Each day is then queried separately, and the period is no longer cut at a single 50,000-row ceiling. Without the date dimension the tool shows “Daily partition export requires the date dimension”. The reason this works is that Google states the cap as 50,000 rows a day for each site and search type, not per request, so a daily partition can return many more rows over a long period than one query for the same dates (Search Analytics query).

Data state and columns

Final data is complete days, while “all” includes fresh data that can still change; for a record you will keep, use final. The CSV starts with a byte-order mark so that spreadsheets show non-English characters correctly. CTR is a fraction between 0 and 1, so 0.032 means 3.2 percent, and you should format that column as a percentage; position is the average position. Search Console also exports values shown as “~” or “-” as zeros (Performance report overview).

What the file is telling you

If you get exactly 50,000 rows, you reached the ceiling: add the date dimension with a daily partition, or shorten the period. If the sum of clicks is lower than the dashboard total, anonymized queries are in the total but never in the rows. Fewer than 1,000 rows from Search Console and more from SEOKit is normal, because the interface export is capped and SEOKit loads more through the API. Do not export a whole year with query and page at once, since it hits the ceiling and drops the tail without any warning; partition by day. And do not share a CSV from a recording session: privacy blur affects the screen only, and exports contain the real values.

Search Console is the source of truth

The export reads the Search Console API, so it can never contain more than Google exposes, and Google says that Search Console stores top data rows, not all of them (about Search Console data). For everything Search Console has, use Google’s bulk data export to BigQuery, which covers all the performance data available for the property except anonymized queries (bulk data export). The documentation on default filters and exports describes every format, the numbers article helps reconcile totals, and the API guide covers the limits and quotas behind all this.

Go further

Docs: default filters and exports: Presets, regex and every export format. FAQ: why SEOKit numbers differ: Six checks to reconcile numbers. FAQ: Search Console API: Limits and quotas behind the export.