How to export Google Search Console data past 1,000 rows

You can export Google Search Console data from almost any report in two clicks, to Google Sheets, Excel or a CSV file. The catch is size: the export stops at 1,000 rows, which on a bigger site can be a small part of its queries and pages. This guide covers the export, what the limit does to your numbers, and how to get past it by exporting the report in slices, with nothing to install.

1. Open the report you want, such as Performance for search results.
2. Set it up first. Per Google, most reports export the data the report is showing, so pick the date range with the Date filter, add any filters in the bar at the top, and choose the tab you want in the table: Queries, Pages, Dates and so on.
3. Export. Find the export button on the report, and choose Google Sheets, Excel or CSV.

The file holds the report's tables, and Google notes that how many there are and how they are laid out varies by report, so look through the file and delete the tables you don't need.

Google says it plainly: the data is truncated to 1,000 rows of representative examples of your data. So if your site has 30,000 queries, the export has 1,000 of them, and adding up the clicks in those rows need not give you the total clicks the report shows: the rows are a sample.

Two habits follow. Take totals from the report, not from summing the export. And if you need more than 1,000 rows, ask for smaller pieces, each under the limit, instead of one big export.

Each export is 1,000 rows of whatever the report shows, so make the report show less and export it several times. Three ways to slice it:

• By date. Set the Date filter to one month, export, then move to the next month. A shorter range has fewer queries in it, so more of them fit. If a month still hits 1,000 rows, go to weeks.
• By query. Add a "queries containing" filter for a word, such as a product or a topic, and export each word in turn. Google notes this filter ignores case.
• By page or section. Filter the report to one page, or to the pages of one part of the site, and export that (more in the next section).

Then paste the exports one under another in a single sheet, with a column saying which slice each row came from, and delete the repeated heading rows. Slices can overlap, especially by query, so remove duplicates on the query column plus the slice column, not on the query alone. And keep in mind that each slice is still a sample of its own part, so the sheet is a much fuller picture, not a complete one.

The question behind most exports is which queries bring people to which page. The Queries tab answers it for the whole site, cut at 1,000 rows. For your important pages, ask it one page at a time instead:

1. In the Performance report, set the date range.
2. Use the filter bar at the top to filter the report to one page.
3. Choose the Queries tab, and export. The file is that page's queries, up to 1,000 of them.
4. Repeat for each page, add a Page column to each file before you stack them, and you have queries by page for the pages that matter.

Google groups pages by the final address after any redirect, so a page you redirected shows up under the address it redirects to.

Choose Google Sheets from the export menu to get the data as a spreadsheet rather than a file. For sliced exports, copy each one's table into a single tab of a working spreadsheet, and keep a separate tab for your charts that points at it, so next month you only add rows.

Choose Excel and you get a workbook; choose CSV if the data is going into another tool. Two things to check once it opens. Click-through rate and position are rates and averages, so don't add them up across rows; recompute the rate from the clicks and impressions instead. And if a date or a number sorts as text, fix it with Data, then Text to Columns, or with the other general fixes for pasted lists in our guide to exporting a list from any site.

Google also offers an export through the Search Console API, for developers.

For very large sites, there is a bulk data export to BigQuery.

Tabless is a browser extension that builds what you ask for from the sites you allow; nothing is typed or submitted without your OK. It isn't open yet. An export like this one is the kind of job we're building it for: asking in plain words for "the queries for each of these ten pages last month, with clicks and impressions", and getting it as a CSV or XLSX file with just those columns.

It's designed to read through the session your browser already has, so there are no API keys or passwords to hand over, and to ask before it reads each site. You sign in to Tabless with a Wix account.

Because the export is cut to 1,000 rows, which Google calls representative examples of your data, so the rows don't have to add up to the report's total. Take the total from the report, and slice the export by date, query or page when you need more of the rows.

As far back as the report goes. Google's help says Search Console keeps data for the last 16 months, and the Performance report shows the past three months until you change the Date filter. To keep more than 16 months, export each month as it ends and keep the files.

Not yet. Tabless isn't open, and exports like this one are among the jobs we're building it for. Join the waitlist, and we'll let you know when you can try Tabless.