Search Console Bulk Export to BigQuery: unsampled search data, past the row cap

Every agency hits the same wall in Search Console: the Performance report UI caps out at a thousand rows, and the API sampling behind it quietly drops the long tail of queries you actually need for striking-distance work. Google's own Bulk Export closes that gap. Set it up once and Search Console writes your full, unsampled performance data into a BigQuery dataset you control, every day, automatically.

Why it made the cut

This is not a third-party workaround, it is the feature Google built specifically because the UI and the standard API were never meant to hold a property's entire query history. Once scheduled, the export runs daily with no further intervention, and every row, every query, every page, every date, lands in your own dataset. That is the entire point: your data, in your project, queryable with arbitrary SQL rather than whatever slice the UI decides to show you.

How to use it

1. In BigQuery, create (or choose) a project and dataset to receive the export, and note the dataset location.
2. In Search Console, open Settings, then Bulk data export, and link the property to that BigQuery dataset.
3. Grant the Search Console service account the required BigQuery permissions when prompted.
4. Wait for the first daily export to land, usually within a day, then query the searchdata_site_impression and searchdata_url_impression tables directly in BigQuery.

Worth knowing

The feature itself is free. You pay only standard BigQuery storage and query costs, which for a single property is typically pennies a month. Once the data lands you can run genuine year-on-year comparisons, build query-level dashboards in Looker Studio, and join search data against anything else you hold in BigQuery, without ever touching the thousand-row ceiling again.