Quick pick
| Method | How many rows | Effort | Best for |
|---|---|---|---|
| Export button | 1,000 per table | None | A quick check of top queries and pages |
| Search Analytics for Sheets | What the API gives, by plan | Low | Query + page tables in a spreadsheet |
| Looker Studio | What the API gives | Medium | Dashboards you share |
| Search Console API | 25,000 per request, 50,000 per day per search type | High (code) | Automation and custom reports |
| BigQuery bulk export | No daily row limit | High (Google Cloud) | Large sites and long history |
All five read the same Search Console data. They differ in how much of it you get and how much work it takes.
1. The Export button
The fastest way. Open Performance → Search results, set the date range, then click Export at the top right and choose Google Sheets, Excel or CSV.
The export contains the chart and the tables, but each table is cut to the top 1,000 rows. Google's help page says it plainly: "Data is truncated to 1,000 rows of representative examples of your data." The totals in the export are the real totals, not the totals of those 1,000 rows.
Good for: small sites, a first look, and the main Missed Clicks tool, which reads the ZIP file directly.
Not good for: sites with more than 1,000 queries or pages that matter, and anything that needs query and page in the same row.
2. Search Analytics for Sheets
A free Google Sheets add-on, made by an independent developer, not by Google. It asks Search Console's API for data and writes it into your sheet, so you can group by Query and Page at the same time and get far more than 1,000 rows.
- In Google Sheets, open Extensions → Add-ons → Get add-ons and install Search Analytics for Sheets.
- Open it from Extensions, choose your property and date range.
- Choose Query and Page as the dimensions to group by, then request the data.
How many rows you get per request depends on the add-on's plan and on what the API returns. This query + page table is the best input for Missed Clicks: every page then shows the queries that bring it traffic.
3. Looker Studio
Looker Studio has a free Search Console connector. It offers two tables, and a single data source can use only one of them:
- Site Impression: data aggregated by property, the same way the Performance chart counts it.
- URL Impression: data aggregated by page, needed for page-level reports.
Looker Studio is built for dashboards rather than exports. You can download a table from a report, but it reads through the same API, so the API's daily limits apply.
4. The Search Console API
The API is what the add-ons use underneath. A request to searchanalytics.query returns up to 25,000 rows; the default is 1,000. To get more, request the next page with startRow. The Performance data is limited to 50,000 rows per day per search type per property, sorted by clicks, and the API documentation notes that it returns the top rows rather than a guarantee of every row.
Other limits worth knowing:
- Quotas of 1,200 queries per minute per site and per user. If you exceed one, wait 15 minutes.
dataState: "all"includes fresh data that is not final yet.- The API returns the same 16 months as the report.
Use it when you need data on a schedule, across many properties, or joined with other data. Otherwise one of the tools above does the same work without code.
5. BigQuery bulk export
Since February 2023, Search Console can send a daily export of all its performance data to Google BigQuery. It is the only method that is not affected by the daily row limit. Anonymized queries are still left out.
Setting it up:
- Create or pick a Google Cloud project with billing and the BigQuery API enabled.
- In the project's IAM settings, add
[email protected]and give it two roles: BigQuery Job User and BigQuery Data Editor. - In Search Console, open Settings → Bulk data export and enter the Cloud project ID (not the project number). Choose the dataset location carefully: it cannot easily be changed once exports have started.
The first export arrives within 48 hours, in a dataset called searchconsole with two main tables, searchdata_site_impression (by property) and searchdata_url_impression (by URL). The export starts from the day you set it up and does not fill in older history. Tables are kept until you delete them. Storage and queries are billed by Google Cloud, with a free usage level.
Which one for Missed Clicks
- For a quick check, use the Export button and drop the ZIP file into the tool. It reads
Queries.csvandPages.csvand skips the rest. - For the best results, export a Query + Page table with Search Analytics for Sheets and paste it into the tool. Every page then shows its own queries, and the AI prompts become specific to that page.
To analyze one kind of search at a time, such as questions or everything except your brand, add a filter from the Search Console regex generator before you export. Filters apply to the export too.
Common mistakes
The wrong date range. A week of data is noisy and a year mixes seasons. Three months is a good default for finding pages close to the top.
Hidden metrics. Turn on all four metrics, clicks, impressions, CTR and position, before you look at the tables, so you see what you are exporting.
The wrong property. A domain property covers every subdomain and protocol, while a URL-prefix property covers only one version, such as https://www. Check which one you exported before comparing numbers with someone else's.
Expecting rows to add up. Search Console leaves out anonymized queries, those not issued by more than a few dozen users over two to three months. They count in the chart totals but have no row, so the Queries table always adds up to less. Totals can also differ between views because some count by property and others by page.
Keeping more than 16 months
The Performance report and the API keep 16 months of data. Anything older is gone unless you saved it. Two ways to keep history:
- Export regularly, for example one month at a time with the Sheets add-on, and keep the files.
- Set up the BigQuery bulk export now. It cannot recover the past, but from the day you start, every day is kept.
Frequently asked questions
How do I export more than 1,000 rows from Search Console?
Use the Search Analytics API (up to 25,000 rows per request, with paging), a tool built on it such as the Search Analytics for Sheets add-on or Looker Studio, or the BigQuery bulk export, which is not affected by the daily row limit.
How far back does Search Console data go?
The Performance report and the API return 16 months of data. To keep more, save regular exports or set up the BigQuery bulk export, whose tables are kept until you delete them. The bulk export does not fill in history from before it was set up.
Why do my query totals not match the chart totals?
Search Console leaves out anonymized queries, those not issued by more than a few dozen users over two to three months. They are included in chart totals, so the rows of the Queries table add up to less. Totals can also differ because data is aggregated by property in some views and by page in others.
Is the BigQuery bulk export free?
Search Console does not charge for it, but the data lives in your Google Cloud project, so BigQuery storage and query costs apply. Google notes there is a free usage level.
Can I export queries and pages together?
Not from the Export button, which gives queries and pages as separate lists. The API can return both dimensions in one table, and so can the add-ons and dashboards built on it.
Sources: Google Search Console Help on exporting report data, Performance data limits and bulk data export setup; the Search Analytics API reference and usage limits; Search Central blog posts on the bulk data export and performance data; Looker Studio Help on the Search Console connector. Checked on 16 November 2026.