Search Console bulk export for technical SEO audits

What to take away

Why the interface is not enough

The Search Console interface is built for quick checks. It shows top rows and samples, so a large catalogue can look healthy while long-tail URLs are excluded or duplicated. Search Console is Google's free reporting service for site owners, and its bulk export option moves the full daily dataset into BigQuery.

For a UK retailer with seasonal traffic, the interface hides the difference between a normal summer dip and a crawl issue. Bulk export keeps daily history, so you can compare August against January and see whether Googlebot returned after a fix.

Pair the export with Screaming Frog crawl budget analysis to compare Google's crawl patterns with your own crawl. If Google spends its budget on filter URLs your crawler also flags as low value, you have a case for a canonical or robots rule.

How to set up the bulk export

Compare the export options

For technical SEO, the bulk export and URL Inspection API work as a pair. The export shows which URLs get impressions; the inspection API tells you whether Google indexed them. The bulk export does not replace the Coverage report. It gives you the URL list to test.

Spotting index bloat and coverage gaps

Index bloat usually appears as many URLs with impressions but no clicks, or as parameter pages that Google keeps crawling. Query the export for URLs with low impressions over 90 days, then group by path pattern. Compare those groups against your sitemap and internal links.

For example, this query totals clicks and impressions by URL over the same 90-day period. Replace the project and dataset placeholders with your own IDs.

SELECT
  url,
  SUM(clicks) AS clicks,
  SUM(impressions) AS impressions
FROM `PROJECT_ID.DATASET_ID.searchdata_url_impressions`
WHERE data_date >= DATE_SUB(CURRENT_DATE(), INTERVAL 90 DAY)
GROUP BY url
ORDER BY impressions ASC;

Use the results to prioritise URLs for technical checks, but treat the export as performance data rather than a technical-status report. It does not show robots.txt directives, sitemap inclusion, canonical or hreflang implementation, or Core Web Vitals. Check crawl and sitemap issues with Screaming Frog, use the URL Inspection API for indexing and Google-selected canonical status, and assess Core Web Vitals separately in Search Console.

Coverage issues need a different check. The bulk export has no index status column, so export a sample of suspect URLs and run them through the URL Inspection API. Look for Crawled - currently not indexed or Duplicate without user-selected canonical. Fix the cause, then watch the daily export for a change in impressions.

For JavaScript-heavy sites, the export can hide rendering problems because data only appears when Google renders the page. If you see impressions for URLs but no clicks and no rich results, audit rendering separately.

Protect the data you export

Search Console query data can include names, email addresses or other identifiers. The ICO's UK GDPR guidance sets out the lawful basis and data minimisation rules that apply when you store or share that export. Keep the BigQuery dataset access limited to people who need it, and set a retention period.

Server logs add the crawl side. Log file analysis for technical SEO shows how often Googlebot hits each path, which status codes it sees and where it wastes time. Combine that with the bulk export to separate demand problems from crawl problems.

Use URL-level performance patterns to prioritise technical investigation rather than relying on broad sector benchmarks. A drop in impressions is a signal to inspect affected templates and crawl paths, not proof of an indexing fault.

Common questions

Can I export Search Console data without BigQuery?

Yes. The Search Console API returns JSON or CSV on a schedule. It suits smaller sites or a fixed report.

Does the bulk export include the Coverage report?

No. The bulk export focuses on Search performance data, not index status. Use the Coverage report or the URL Inspection API to check specific URLs.

How much does BigQuery cost for Search Console data?

The BigQuery free tier includes up to 1 TiB of query processing and 10 GiB of storage per month. Beyond those allowances, charges depend on usage, location and pricing model, so check the current Cloud pricing for your location before enabling the export.

Is the bulk export compliant with UK GDPR?

The export is a tool, but the data can contain personal details. Follow the ICO guidance, limit access, and delete data you no longer need.