How to Export Google Search Console Data
A practical guide to exporting Google Search Console performance data, choosing the right format, and preparing query and page evidence for review.
Short answer: Open Google Search Console, choose the correct property, open the Search results Performance report, set a clear date range, and export the data. CSV is the simplest general-purpose option. SearchTriage currently accepts CSV, ZIP, and XLSX files.
Google's direct export instructions explain the controls in Search Console and the data included in a normal report download. The filters, dimensions, and date range active on screen affect what is exported.
Choose the right property and report
Use the property that matches the domain, subdomain, or URL prefix you want to review. Mixing unrelated site sections can make later analysis noisy because they may serve different audiences, templates, or goals.
Open Performance, choose Search results, and confirm the search type and date range. Export each property separately when you manage more than one site.
Export both query and page evidence
Queries show the search language associated with the property. Pages show which URLs received impressions. Useful content decisions often depend on the relationship between the two.
A relevant query with impressions but no clicks may point to weak search packaging, low position, or the wrong page. Read the impressions-without-clicks diagnostic before assuming it needs a new article.
If the query is useful but an unsuitable URL is appearing, use the query/page mismatch guide. When a suitable page already exists, the write-or-update decision guide can help prevent a duplicate.
What format should you export Google Search Console data into?
Choose the format around what you need to do next rather than looking for one universally best file type.
CSV is the simplest choice
CSV is compact, widely supported, and easy to inspect or import into another tool. It is usually the best choice when you want individual query, page, or date tables and do not need workbook formatting.
SearchTriage accepts individual CSV files when they contain a recognised Google Search Console dataset and the required columns.
ZIP keeps a multi-file export together
A ZIP file is useful when a Search Console download contains several related CSV files and you want to preserve the bundle. It is easier to upload one archive than select each file separately.
SearchTriage accepts ZIP archives containing supported GSC CSV files. It validates the archive and ignores unrelated entries rather than treating every file as search data.
XLSX is convenient for spreadsheet review
Microsoft Excel format is useful when you want the exported tables in one workbook, need to inspect sheets manually, or expect to annotate the data before sharing it.
SearchTriage accepts XLSX workbooks exported from Google Search Console and reads the recognised worksheets. It does not accept older XLS files.
JSON and the Search Console API suit automated workflows
JSON makes more sense when a script or application is calling the Search Analytics API. The API supports selected dimensions, filters, date ranges, and pagination, but its responses still reflect Search Console's reporting limits.
SearchTriage does not currently accept JSON uploads or connect directly to a user's Search Console account. Its current workflow uses manual CSV, ZIP, or XLSX imports.
Normal exports are not bulk data exports
The Export button in the Search Console interface downloads the data shown by that report. It is not the same as Search Console's bulk data export to BigQuery, which is an ongoing Google Cloud setup intended for much larger datasets.
Normal exports are practical for periodic review. The API or BigQuery may be a better source when a large site needs repeatable automated analysis or more data than the interface download provides.
Using the export in other analysis tools
CSV, Excel, API responses, or warehouse tables can later feed Power BI, Tableau, Qlik, PostgreSQL, Redshift, and similar tools. That is a data-preparation step, not a direct SearchTriage integration.
SearchTriage is designed for a narrower job: review GSC evidence with site context, then organise the useful findings into decisions about what to write, update, link, fix, or ignore.
Move the export into another reporting tool
A normal Search Console download is enough when you want to inspect the data in a spreadsheet or upload it to SearchTriage. Moving the same evidence into Power BI, Tableau, Qlik, PostgreSQL, Redshift, monday.com, an API workflow, or BigQuery requires a different hand-off.
The guide to exporting Google Search Console data to other tools explains when a CSV or XLSX import is sufficient, when a connector or ETL process is required, and when BigQuery bulk export is the better long-term source.
Keep the reporting period clear
A weekly or monthly export is easier to explain than a random date range. Record the start and end dates and avoid comparing a complete period with a partial one.
If overlapping ranges are imported later, SearchTriage updates its canonical daily history without double-counting overlapping dates. It also records gaps and overlap so the resulting report can describe the data honestly.
Tested with SearchTriage's current uploader
Checked 24 July 2026: the upload interface, extension allow-list, validation code, and parser support CSV, ZIP, and XLSX. JSON, XLS, database dumps, and files from unrelated reporting tools are not accepted as GSC imports.
I use SearchTriage on my own sites, including Old Stack Journal, to review Search Console exports and decide which content changes are worth making.
Before uploading private search data, review how SearchTriage protects imports and account data. Then see how the audit works from import to recommendation.