How to export data from Google Search Console

How do you export data from Google Search Console?

Open the Performance report, choose the Queries or Pages tab, set the date range and filters, then click Export and choose Google Sheets, Excel or CSV. The download contains the chart and table data for the view you configured, so set the report up before you export.

The export button sits above the Performance report. Google's Performance report help confirms that many reports provide an export button for the chart and table, and that values shown as ~ or - in the interface become zeros in the downloaded file.

How do you export the queries report?

Select the Queries tab, narrow the report to the search terms you need, then export that view. Queries are the searches people used before they saw or clicked your site.

1. Open Performance

   Choose the verified property you want, then open Performance in the left menu. The default view covers the past three months.

2. Set the date range

   Pick a start and end date. For a fair comparison, use two equal periods and leave out the newest days while they are still being collected.

3. Choose Queries and add filters

   Click the Queries tab, then use the filters for search type, country or device. A filter changes which rows the report contains, so check it before exporting.

4. Export the view

   Click Export and choose Google Sheets, Excel or CSV. Keep the date range and filters in the filename or a notes column so a later export is easy to compare.

How do you export the pages report?

Select the Pages tab, set the same date range and filters, then export. Pages are your URLs that received impressions or clicks; Google groups page data by page rather than by the whole property.

1. Choose Pages

   Click the Pages tab above the table. The table now lists URLs from your property with their clicks, impressions, CTR and average position.

2. Check the aggregation

   Page rows are grouped by page, while query, country, device and date rows are grouped by property. That difference can make table totals differ from the chart.

3. Filter before exporting

   Use a page or query filter when you only need one section of the site. The export follows the report view, so an unfiltered export is broader than one with filters.

4. Download and label the file

   Export the pages view to a spreadsheet. Add the property, date range, search type and filter to the sheet name so the file is useful after the report changes.

What date-range and row-limit caveats change the numbers?

The export is a snapshot of a filtered report, not a complete copy of every query Google ever recorded. These limits are the main reasons a spreadsheet can look different from the chart or from another analytics tool.

• Rows: Google says Search Console tables show a maximum of 1,000 rows, and the API exposes a larger selection. A table or export can therefore contain fewer rows than the chart total.
• Privacy filtering: Rare queries and queries containing personal or sensitive information are omitted. Query rows may not add up to the property total.
• Top rows only: Google stores top data rows rather than every row. Requests grouped by query or page can also lose some data because of internal processing limits.
• Delay: Data is normally available in 2-3 days, and the newest days can still change. Exporting those days and comparing them later may show a difference.
• Time zone: Search Console labels daily Performance data using California time. A report built in another time zone may not match day for day.
• History: Search Console keeps about 16 months of Performance data. If you need a longer record, save a dated export regularly.
• Missing values: A ~ or - in the interface becomes zero in the download, so do not read every zero as a true absence of activity.

Google's About Search Console data page explains the 1,000-row table limit, privacy filtering and the 2-3 day delay. Read the definitions before treating a row count as the size of your search market.

Spreadsheet or API: which workflow fits?

Use the interface export for one-off analysis and the Search Analytics API for repeatable, larger or automated pulls. The table below compares the practical differences; it does not change Google's limits.

When is a spreadsheet workflow more suitable?

A spreadsheet is the better choice when you need to understand one period, compare a handful of pages or share a report with someone who will not use an API. It is simple, portable and easy to annotate.

• Ad hoc analysis: You want to sort pages by impressions, add a CTR formula or chart clicks over time.
• Manual joins: You need to match exported pages to a keyword list, content plan or internal-link map.
• Client or team review: A CSV or Google Sheet is easier to discuss than a JSON response.
• Small, periodic checks: A weekly or monthly export is enough and you do not need a scheduled pipeline.

Keep one tab per export or one dated file per period. Add the property, date range, search type and filters to the file so a row is still understandable when you return to it months later. A spreadsheet does not remove the row limit; it simply makes the visible rows easier to work with.

When is the Search Console API more suitable?

The Search Analytics API is the better choice when the export has to run on a schedule, return more rows or feed another system. You call searchAnalytics.query with a date range and dimensions such as query or page, then page through the results with startRow.

• More rows per request: rowLimit accepts 1 to 25,000 rows; the default is 1,000.
• Paging: Re-run the query and increase startRow until a response returns zero rows.
• Daily ceiling: Google documents a maximum of 50,000 rows of data per day per search type, sorted by clicks.
• Automation: A scheduled job can save one day of data at a time and keep a longer local history than the interface shows.
• Quota: API calls also count against the Search Console API quota, so a daily one-day query is the recommended pattern.

The API reference sets out the request fields and response format in searchAnalytics.query, and Google's Getting your performance data guide explains the daily query and paging pattern. An API pull is still Search Console data, so privacy filtering and the top-row limits apply.

How does MrKeyword fit an export workflow?

MrKeyword connects to your own Search Console property and uses that data for rank tracking, opportunities and reports. It does not unlock rows Google does not return, and it does not change Google's limits. Use the export when you need the raw file, and use MrKeyword when you want the same data turned into decisions.

The SEO opportunities feature ranks quick wins by the clicks at stake from your own Search Console data, and reports turn the numbers into something you can share. For setup and the other reports, read our guide to using Google Search Console.

What should a practical export workflow include?

Export the same view consistently, keep the date range and filters with the file, and record what you changed on the site. A short routine is enough:

1. Start with one question

   Decide whether you are checking queries, pages or a single section of the site. That choice sets the tab and filters before you export.

2. Use a consistent date range

   Compare equal periods, such as the last 28 days against the previous 28, and leave out the newest 2-3 days while they settle.

3. Save the file with context

   Include the property, date range, search type and filters in the filename or a notes tab so the next export is comparable.

4. Turn rows into actions

   Look for pages with impressions but few clicks, queries close to page one, and pages that lost clicks. Fix the page or snippet, then use MrKeyword reports to track the change.

Questions and answers