What it is.
You enable two APIs in a Google Cloud project, grant the export service account the BigQuery Job User and BigQuery Data Editor roles, then switch the export on in Search Console under Settings. Data lands in a dataset named searchconsole, and the first export happens up to 48 hours after setup.
What you get is the query and page rows in a table you can query yourself, joinable to a CRM export or a content inventory.
Costs sit with Google Cloud, which has a free usage level and charges past it, so set a partition expiration of 14 days or longer to keep storage predictable.
What you get.
- Daily tables of Search Console query and page data in your own BigQuery dataset.
- History that accumulates from the day you switch it on.
- A dataset you can join to product, CRM, or revenue tables in the same warehouse.
- SQL access, so a question like which pages lost non-branded clicks becomes one query.
How to set it up.
In Google Cloud, enable the BigQuery API and the BigQuery Storage API on the project you want the data in.
Grant search-console-data-export@system.gserviceaccount.com both BigQuery Job User and BigQuery Data Editor.
In Search Console, open Settings, then Bulk data export, and enter the Cloud project ID.
Pick the dataset name, where searchconsole is the default, and a location you can live with, because changing it later is hard once exports begin.
Set a partition expiration of 14 days or longer so storage stops growing without limit.
Wait up to 48 hours for the first export, then read the dataset before you build anything on top of it.
Use cases
Keep query history
Switch the export on so the data stops falling out of the sixteen-month window.
Join search to revenue
Put the query tables next to your CRM data in the same warehouse.
Report at page level
Query the raw tables when the interface will not group the way you need.
Best for
Sites with a long tail
Thousands of low-volume queries are where the aggregate movement sits, and SQL is how you see them together.
Joining search to revenue
Query data in the same warehouse as pipeline data turns an SEO report into a revenue argument.
Keeping history
The export accumulates from the day you enable it, so switching it on early costs almost nothing and buys you a baseline.