How to Export Google Search Console Data to BigQuery
Quick answer: Search Console can export performance data to BigQuery on a daily schedule. You enable bulk data export in Settings, point it at a Google Cloud project with billing enabled, and grant the export service account permission. Google then writes daily tables of query, page, device, and country rows, minus anonymized queries.
You hit the 1,000-row export limit in the Search Console interface for the third time this week. The API gives you more, until a script that pulls 90 days of query-and-page rows starts taking twenty minutes and hitting quota. Meanwhile the 16-month window keeps rolling forward and last year's data is already gone.
Bulk data export solves the storage problem by having Google write to your BigQuery dataset every day. Once it runs, you own the history permanently, you query it with SQL, and the row limits that constrain the interface stop applying. Setup is a one-time configuration in Google Cloud and Search Console.
SEARCH CONSOLE
How to Export Google Search Console Data to BigQuery
PRIMARY KEYWORD
export Google Search Console data to BigQuery
READ TIME
8 minutes
What does Search Console's bulk data export actually send?
Google writes daily tables of search performance data into a dataset you nominate. The rows carry the dimensions the Performance report exposes, including query, page, device, country, and search appearance, along with clicks, impressions, and position.
The export is scheduled and forward-looking. Google starts writing from the day you enable it, so it does not backfill history you have not already collected. That makes the setup date the earliest date you will ever have in BigQuery, which is the strongest argument for enabling it before you need it.
How do you set up the export?
You need a Google Cloud project with billing enabled and permission to grant roles in it. Search Console pushes data into your project, so the account doing the setup needs authority on both sides.
In the Cloud project, enable the BigQuery API and grant the Search Console export service account the roles it needs to create jobs and write data. Then open Search Console Settings, choose bulk data export, enter the project ID, and confirm. Google validates the permissions immediately and reports the first export date.
- A Google Cloud project with billing enabled
- The BigQuery API turned on in that project
- Job-user and data-editor roles granted to Google's export service account
- Owner or full permission on the Search Console property
- A dataset location you can live with, since it cannot be moved later
Which rows does the export leave out?
Anonymized queries. Google withholds queries issued by very few people to protect privacy, and those rows do not appear in the export any more than they appear in the interface. Totals in your BigQuery tables will therefore come in under the site-level totals in the Performance report.
That gap is expected and it is not a setup error. Report it once in whatever you build on top, because a stakeholder who reconciles the two figures will find the difference and assume the pipeline is broken.
What does BigQuery cost for Search Console data?
Storage and query costs come from your Cloud project, and Google bills them at standard BigQuery rates. A single site's daily performance rows are small by BigQuery standards, so cost for one property is typically dominated by how you query rather than what you store.
The cost mistake is scanning full tables repeatedly. Partition-aware queries that filter on date read a fraction of the data. Check Google's current pricing before committing, since rates and free-tier allowances change.
When is the API a better choice than BigQuery?
The Search Console API is the lighter option when you want current numbers rather than accumulated history. It returns rows on demand, needs no Cloud billing, and suits a weekly report or a dashboard that reads the last 28 days.
BigQuery earns its setup when you need history beyond 16 months, joins against other datasets, or row volumes the API makes painful. Many teams run both: the API for live questions, the export for the archive.
TAKEAWAY CHECK
What belongs on the stand up the bigquery export?
- 01Create or choose a Google Cloud project and enable billing.
- 02Turn on the BigQuery API in that project.
- 03Grant Google's Search Console export service account job-user and data-editor roles.
- 04Pick a dataset location you can live with permanently.
- 05Enable bulk data export in Search Console Settings with the project ID.
- 06Confirm the first daily table lands, then check row counts against the Performance report.
- 07Document the anonymized-query gap wherever the data gets reported.
What else do people ask about export Google Search Console data to BigQuery?
Does the BigQuery export include historical data?
No. Google begins exporting from the date you enable it and does not backfill. Anything older has to come from the Search Console API within its 16-month window, exported separately and loaded yourself. That makes enabling the export early worthwhile even before you have a use for it.
Why do my BigQuery totals not match the Performance report?
Anonymized queries are excluded from query-level rows, so summing them lands under the site total. Date handling can also differ if your queries filter in local time while the export uses a fixed timezone. Check the anonymized-query gap first, since it explains most discrepancies.
Can I export more than one property into the same project?
Yes. Each property is configured separately in its own Search Console settings and can write to the same Cloud project. Keep them in separate datasets or use the property column consistently, so a later query cannot silently blend two sites.
Do I need to write SQL to use the export?
For anything beyond a spreadsheet dump, yes. BigQuery is queried with SQL, and connecting a visualization tool still means someone writes the underlying query. If nobody on the team writes SQL, the Search Console API into a spreadsheet is the more realistic path.
What happens to the export if I lose access to the property?
The export stops when the permission behind it goes away, and data already written to BigQuery stays in your project. Agencies should set this up in a project the client owns, so losing the engagement does not strand the client's history in an inaccessible account.
Which primary sources support this guide?
Product behavior and metric definitions change. These are the official Google references used for this article and checked on July 31, 2026.
- 01Google Search Console: bulk data export to BigQuery
Google's overview of scheduled BigQuery exports and the exclusion of anonymized queries.
- 02Google Search Console: export data with the API
Google's guidance on Search Console API capabilities and the daily row limit for performance data.
- 03Google Search Console: export data from a report
Google's export formats, filtered-report behavior, and 1,000-row interface export limit.
- 04About Search Console data
Google's documentation on freshness, privacy omissions, row limits, time zones, and discrepancies.
PUT THE CLAIM ON THE RECORD
Your SEO result deserves a source, not a trust-me caption.
Connect an owner-level Search Console property, choose what stays public, and get a receipt with a stable share link.