How do I export data from Google Search Console?

Q: How do I export data from Google Search Console?

Use Export for up to 1,000 rows, Looker Studio or the API for 50,000 rows a day, or Bulk data export for every row. Here is which route fits which job.

Open the report, set the date range and filters you want, and use its Export button: Search Console offers Google Sheets, Excel or CSV. The file holds at most 1,000 rows per table, enough for a small site and a truncated sample for a large one. For more rows, use the Looker Studio connector or the Search Analytics API, up to 50,000 rows per day per search type, or Bulk data export to BigQuery, which has no row limit.

Exporting from a report

Open the report, for example Performance > Search results.
Set the date range, search type, comparison and any filters. They carry over into the file.
Choose Export and pick Google Sheets, Excel or CSV.

The file contains both the chart and the table data. Values shown as ~ or - in the report become zeros. Rows beyond 1,000 are cut, with Google keeping what it calls representative examples. Most other reports export the same way, including the example URLs of each Page indexing reason, up to 1,000.

Which route fits which job

Route	Rows	History	Effort	Best for
Export button	1,000 per table	16 months	None	Quick snapshots and sharing
Links report exports	Up to 100,000 links per export	Links found over time	None	Backlink lists
Looker Studio connector	Up to 50,000 per day per search type	16 months	Low	Dashboards
Search Analytics API	Up to 50,000 per day per search type, 25,000 per request	16 months	Code and OAuth	Automation, your own database
Bulk data export	Every row	From setup day, kept until you delete it	Cloud project and SQL	Complete data, long-term storage

The deep dives: the Search Console API, Bulk data export and Looker Studio.

Getting more than 1,000 rows without code

Each filtered view gets its own 1,000 rows, so you can slice the data and export the slices:

By section. Filter pages with a regular expression such as /blog/, export, then repeat for each folder.
By country or device. Export each market separately.
By month. Shorter ranges surface a different top 1,000 for each period.

Two cautions. A query filter removes rare, anonymised queries from the totals as well, so the sum of your slices will not match the unfiltered chart. And slices can overlap, so de-duplicate before adding them up.

Keeping exports useful over time

Exports are snapshots: an export from this month cannot be refreshed later, and nothing in Search Console survives past 16 months. If you export to keep history, do it on a schedule, keep the date range in the file name, and store query and page data at the same granularity each time. For automated storage, see how long Search Console keeps data.

How AutoPSEO helps

Every table in AutoPSEO exports to CSV or copies to the clipboard, and its tables are filled through the Search Console API rather than the 1,000-row export, so a query or page list is far longer than Search Console's own. To send a report to someone, save it as a shared link: it holds a snapshot of up to 5,000 rows that anyone with the link can open without an account, and can also be downloaded as CSV or a self-contained HTML file. For pipelines, AutoPSEO's REST API returns the same data with an API key. See exporting data and sharing.

Sources: Google's export help, API export help, Links report help and performance data limits.