What it is: a connection to the Search Console bulk data export that you switch on in your own Google Cloud project. The BigQuery bulk export starts on the Pro plan.
Set up, in order:
- In Search Console, turn on the bulk data export. Google creates the dataset and fills it from the day you enable it. Earlier days are not exported.
- In your Google Cloud project, create a service account that only reads the export.
- Grant it
roles/bigquery.dataVieweron the export dataset only, androles/bigquery.jobUseron the project. No write roles are needed. - In SerpUp, open the site's Integrations page, then BigQuery bulk export. Enter the project id, the dataset and the location, and upload the service account's JSON key. The key is encrypted on arrival and never shown again; only the service account e-mail and the last four characters of the key id are displayed.
- Run the connection test. It reads metadata only and makes no changes.
- Review the cost estimate, then enable the export. The enable button stays disabled until you have run the test and the estimate.
Cost: BigQuery bills your Google Cloud project for the queries SerpUp runs, not SerpUp. The estimate comes from a BigQuery dry run, so asking for it queries and bills nothing.
What you see: the Reconciliation page compares the Search Console API totals with the bulk export totals for the same days. A day is compared only when both sources have it, so no number appears without its counterpart.
Turning it off: disabling the export switches the site's reports back to the Search Console API.