Google Search Console offers a powerful Bulk Data Export feature that allows website operators to store and analyze extensive search data in Google BigQuery. In this blog post, you’ll learn how to set up and optimally use the Bulk Data Export in Google Search Console.

Why use Bulk Data Export?

Bulk Data Export enables:

  • In-depth analyses through more comprehensive data than in standard reports.
  • Automation of reports through direct integration with Google BigQuery.
  • Long-term data storage, which is otherwise only available in Search Console for a limited time.

Step-by-step guide to setting up the Search Console BigQuery Export

This guide has been derived from the official instructions.

Before you can use Bulk Data Export, you need a Google Cloud Project:

  • Log in to the Google Cloud Console.
  • Create a new project or use an existing one.
  • Ensure that BigQuery is enabled, as the data will be stored there.
  1. Log in to Google Search Console:
  2. Navigate to settings:
    • Click on Settings in the left menu bar.
    • Scroll down and select Bulk Data Export.
  3. Connect Google Cloud Project:
    • Copy the Project ID (not the project number!) from the Google Cloud Console.
    • Paste the ID into the Cloud Project ID field.
  4. Choose Dataset name:
    • By default, the name is searchconsole.
    • If you’re exporting data from multiple properties, use individual names (e.g. searchconsole_mywebsite_com).
  5. Choose storage location for the Dataset:
    • Select a storage location from the list.
    • Please note that the save location cannot be easily changed once the export has begun. For users from the EU, this should also be “EU.”
  6. Confirmation and start of export:
    • Click on Continue to complete the configuration.
    • If there’s a problem (e.g., missing permissions), an error message will be displayed.
    • The first export will occur within 48 hours.
Google searc console bigquery export.png

What happens after setup?

  • Daily export: Search Console automatically exports the data every day.
  • Error handling: If there’s a non-critical error, the export will be attempted again the next day.
  • Data structure: After the first export, table partitions can be adjusted. Changes to the schema (e.g., adding new columns) should be avoided as this can interrupt the export.
  • Historical data: For older data from before setup, the Search Console API or standard reports must be used.

Conclusion

The Google Search Console Bulk Data Export is a valuable feature for SEO professionals and data analysts who want to gain comprehensive insights into their website’s search performance. With this guide, you can quickly and efficiently set up the export and thus utilize valuable data for your analyses in the long term.

Bernhard prange webmeisterei

SEA-Experte: Bernhard Prange

Bernhard Prange ist Google Ads Freelancer und Tracking-Spezialist mit über 10 Jahren Erfahrung im Performance-Marketing. Sein Fokus liegt auf datengetriebenem Arbeiten: von Google Shopping über Conversion-Tracking bis hin zu serverseitigen Lösungen mit Matomo und BigQuery.

Als Ansprechpartner für Agenturen, E-Commerce-Unternehmen und B2B-Dienstleister verbindet er technisches Know-how mit strategischem Blick auf Marketing und Geschäftsmodelle.

Beiträge, die dich auch interessieren könnten…

  • Better data, better decisions: Data enrichment in Server-Side Tracking

    Lesen
  • Google Ads DemandGen: The Complete Practical Guide

    Lesen
  • Claude MCP: 30+ Integrations for WordPress, Google Ads & SEO

    Lesen
  • Track User Reading Behavior with Google Tag Manager

    Lesen