---
title: "SQL for SEO: Build a Search Data Warehouse"
description: "Use SQL for SEO to combine Search Console, GA4, crawl, ranking, and CRM data in a queryable BigQuery warehouse that replaces fragile sheets."
canonical: "https://nikoalho.fi/writing/sql-for-seo/"
language: "en"
---

> Canonical source: [https://nikoalho.fi/writing/sql-for-seo/](https://nikoalho.fi/writing/sql-for-seo/)

[← writing](https://nikoalho.fi/writing/)

Lab Published 2026 · 05 · 20

# SQL for SEO: the architecture that replaces spreadsheets

Spreadsheets break past 100k rows. The SQL architecture and BigQuery schema I use to consolidate GSC, GA4, and crawl data into one queryable warehouse.

![Niko Alho](https://nikoalho.fi/assets/niko-alho-avatar-96.webp)

**Niko Alho**Operator in Turku · firsthand systems

ON THIS PAGE

[01 Why Excel Breaks at Scale (The Diagnosis)](#why-excel-breaks-at-scale-the-diagnosis) [02 Spreadsheet limits versus a SQL warehouse](#spreadsheet-limits-versus-a-sql-warehouse) [03 The Infrastructure: BigQuery for SEO Analysis](#the-infrastructure-bigquery-for-seo-analysis) [04 How BigQuery cost scales with partitioning](#how-bigquery-cost-scales-with-partitioning) [05 5 SQL Queries That Replace Manual Audits (The Architecture)](#5-sql-queries-that-replace-manual-audits-the-architecture) [06 Automating the Output: From Query to Dashboard (The Application)](#automating-the-output-from-query-to-dashboard-the-application) [07 Estimate the traffic lift from a position gain](#estimate-the-traffic-lift-from-a-position-gain) [08 The Directive: Stop Reporting, Start Architecting](#the-directive-stop-reporting-start-architecting)

PROGRESS

0%

ON THIS PAGE 8 sections

[01 Why Excel Breaks at Scale (The Diagnosis)](#why-excel-breaks-at-scale-the-diagnosis) [02 Spreadsheet limits versus a SQL warehouse](#spreadsheet-limits-versus-a-sql-warehouse) [03 The Infrastructure: BigQuery for SEO Analysis](#the-infrastructure-bigquery-for-seo-analysis) [04 How BigQuery cost scales with partitioning](#how-bigquery-cost-scales-with-partitioning) [05 5 SQL Queries That Replace Manual Audits (The Architecture)](#5-sql-queries-that-replace-manual-audits-the-architecture) [06 Automating the Output: From Query to Dashboard (The Application)](#automating-the-output-from-query-to-dashboard-the-application) [07 Estimate the traffic lift from a position gain](#estimate-the-traffic-lift-from-a-position-gain) [08 The Directive: Stop Reporting, Start Architecting](#the-directive-stop-reporting-start-architecting)

**TL;DR** The useful bits

-   9-min read
-   4 takeaways

1.  01 VLOOKUP across 5 million GSC rows is not analysis — it's manual labor that destroys agility.
2.  02 Spreadsheets create data silos (crawl in one CSV, GSC in another, logs rotting on a server) — SQL collapses them into one warehouse.
3.  03 BigQuery is the standard architecture for enterprise SEO inside the Google ecosystem; the analyst becomes an architect once they leave Excel behind.
4.  04 SQL is the dividing line between reporting on the past and engineering the future — query, don't export.

A/01 Direct answer

Why do search marketers need SQL?

Past 100k rows, spreadsheets break. SQL — typically via BigQuery in the Google ecosystem — lets you query GSC, GA4, crawl data, log files, and CRM data as one warehouse. The shift from VLOOKUP to SQL is what turns an SEO analyst into an SEO architect.

SQL is the architectural layer that turns 5 million rows of Google Search Console data, crawl logs, and CRM exports into a single queryable warehouse — replacing the `VLOOKUP` workflow that breaks the moment you cross 100,000 URLs. For any SaaS platform or enterprise e-commerce site, it is the difference between an analyst who reports on the past and an operator who engineers the future.

In 2026 the volume of search data has exploded — log files alone produce gigabytes per day on a mid-sized site, GSC’s API outpaces any spreadsheet, and joining those streams to CRM closed-won data is the only way to answer the only question that matters: which keyword sourced the deal that paid this month’s salaries.

* * *

## Why Excel Breaks at Scale (The Diagnosis)

The comfort of a spreadsheet is a liability. For a small brochure site, Excel is fine. For a SaaS platform or an enterprise e-commerce site with 100,000+ URLs, it is a bottleneck that actively bleeds revenue.

Here is the brutal truth about your current workflow:

1.  **The Data Cap Reality:** While Excel technically handles roughly 1 million rows, performance degrades rapidly with complex lookups. Google Sheets has a higher cell limit, but calculation latency often renders it unusable for massive datasets long before you hit that cap. When analyzing 16 months of GSC data combined with daily log files, you are dealing with tens of millions of data points. Truncating data to fit a spreadsheet means making decisions based on incomplete intelligence.
2.  **The Silo Problem:** Spreadsheets create disconnected islands of data. Your crawl data lives in one CSV, your GSC data in another, and your log files are likely rotting in a server folder. This fragmentation prevents you from seeing the correlation between technical health and revenue performance.
3.  **Static vs. Dynamic:** A spreadsheet is a snapshot in time. The moment you export it, it is obsolete. An SQL environment is a living pipeline.

To execute true **technical SEO auditing** at an enterprise level, you must move from manual file management to a centralized data warehouse. You need a system that allows you to interrogate data, not just store it.

* * *

## Spreadsheet limits versus a SQL warehouse

02

Reference table

| Use Case | SQL Pattern | Difficulty | Impact |
| --- | --- | --- | --- |
| Keyword Cannibalization | `GROUP BY` query, `HAVING COUNT > 1` | Medium | High |
| Content Decay Detection | `WHERE clicks < lag(clicks, 90)` | Medium | High |
| CTR Anomaly Detection | `WHERE ctr < avg_ctr * 0.7` | Easy | Medium |
| Crawl Budget Analysis | `JOIN logs ON url = page` | Hard | Medium |
| Internal Link Audit | `COUNT(DISTINCT source)` per target | Easy | High |
| Position Clustering | `NTILE(4) OVER (ORDER BY position)` | Medium | Medium |

## The Infrastructure: BigQuery for SEO Analysis

You do not run enterprise SQL queries on your laptop. You run them in the cloud. In the current 2026 search landscape, **Google BigQuery** is the standard for **Technological Sovereignty** in SEO for those operating within the Google ecosystem.

Why BigQuery? Because it integrates natively with your existing tool stack. The Google Search Console Bulk Data Export feature pipes raw performance data directly into BigQuery daily. This eliminates the need for expensive third-party connectors or fragile API scripts that time out.

### The Cost Myth

Many SEOs fear the cloud because of potential costs. This is a lack of **Operational Intelligence**. BigQuery separates compute from storage. Storing terabytes of data is incredibly cheap. Querying costs accrue based on data processed, but if you architect your tables correctly—using **partitioning** (e.g., by date) and **clustering** (e.g., by query or URL)—running a complex query over millions of rows often costs pennies.

Using **BigQuery for SEO analysis** allows you to perform operations impossible in a GUI. You can calculate the weighted average position of a keyword across specific subfolders, identify crawl anomalies in seconds, or model CTR curves based on your specific brand authority — feeding directly into [SEO KPIs](https://nikoalho.fi/writing/seo-kpis/) the C-suite actually cares about.

This is not about spending more; it is about spending smarter to gain an “unfair” advantage.

* * *

## How BigQuery cost scales with partitioning

01

Visual model

SEO DATA WAREHOUSE ARCHITECTURE

Source

GSC

Search Console

Source

GA4

Analytics

▶

Data Lake

BigQuery

Centralized storage & SQL engine

▶

Transform

Views

Materialized queries

▶

Output

Dashboard

Looker Studio / Sheets

## 5 SQL Queries That Replace Manual Audits (The Architecture)

Stop wasting time on basic `SELECT *` tutorials. As an Architect, you need to solve business problems. Below are five advanced SQL architectures designed to replace manual auditing workflows with automated precision.

### 1\. Cleaning and Normalizing URL Structures

Data integrity is the prerequisite for analysis. GSC might report a URL with a trailing slash, while your crawl data reports it without. Before joining datasets, you must normalize the keys (URLs).

This query creates a standardized “join key” by stripping protocols, `www`, and trailing slashes.

```
SELECT
  url,
  -- Remove protocol (http/s) and www
  REGEXP_REPLACE(REGEXP_REPLACE(url, r'https?://', ''), r'^www\.', '') AS clean_domain_path,
  -- Remove query parameters and trailing slashes for a clean join key
  TRIM(REGEXP_REPLACE(url, r'\?.*', ''), '/') AS join_key
FROM
  `your_project.dataset.crawl_data`
WHERE
  content_type = 'text/html'
```

**The Value:** By creating a `join_key`, you ensure that when you merge GSC data with crawl data, you don’t lose matches due to minor formatting discrepancies.

### 2\. Querying Log Files for Crawl Budget Analysis

Most SEOs guess how Google crawls their site. **Log file analysis automation** removes the guesswork. You need to know exactly where Googlebot is spending its resources.

*Note: While User-Agent filtering is a good starting point, a solid production environment should verify Googlebot via reverse DNS lookup to filter out spoofed traffic.*

This query groups bot hits by status code and directory.

```
SELECT
  -- Extract the first directory level
  REGEXP_EXTRACT(request_uri, r'^/([^/]+)/') AS directory,
  status_code,
  COUNT(*) AS hit_count,
  -- Calculate percentage of total crawl budget
  ROUND(COUNT(*) * 100.0 / SUM(COUNT(*)) OVER(), 2) AS percentage_of_crawl
FROM
  `your_project.dataset.server_logs`
WHERE
  user_agent LIKE '%Googlebot%' -- Ensure upstream verification of IPs
  AND date >= DATE_SUB(CURRENT_DATE(), INTERVAL 30 DAY)
GROUP BY
  1, 2
ORDER BY
  hit_count DESC
```

**Revenue Impact:** If this query reveals that 40% of Google’s crawl budget is hitting `404` errors or low-value `/tag/` pages, you have identified a critical inefficiency. Blocking those paths forces Googlebot to reallocate resources to your high-intent money pages.

### 3\. Joining GSC Data with Internal Crawl Data (The Orphan Finder)

Orphan pages (pages that exist but have no internal links) are invisible to users and struggle to rank. A standard crawl won’t find them because the crawler cannot reach them.

By utilizing a **LEFT JOIN** between your GSC data (what Google knows about) and your crawl data (what your site structure shows), you can identify pages that receive traffic but are disconnected from your architecture.

```
WITH gsc_urls AS (
  SELECT DISTINCT url
  FROM `your_project.dataset.gsc_bulk_export`
  WHERE date >= DATE_SUB(CURRENT_DATE(), INTERVAL 30 DAY)
),
crawl_urls AS (
  SELECT url, incoming_links
  FROM `your_project.dataset.site_crawl`
)

SELECT
  g.url AS orphaned_url
FROM
  gsc_urls g
LEFT JOIN
  crawl_urls c ON g.url = c.url
WHERE
  c.url IS NULL -- The URL exists in GSC but was not found in the crawl
```

**The Fix:** These URLs are often legacy pages retaining equity. Once identified, redirect them to current assets or reintegrate them into the site navigation.

### 4\. Identifying Keyword Cannibalization at Scale

Cannibalization is not just about two pages ranking for the same term; it is about two pages *splitting* the click-through rate (CTR) and preventing either from reaching position #1.

This query identifies queries where multiple URLs have significant impressions, signaling a conflict in intent targeting.

```
SELECT
  query,
  COUNT(DISTINCT url) AS url_count,
  STRING_AGG(url, ', ') AS competing_urls,
  SUM(impressions) AS total_impressions,
  SUM(clicks) AS total_clicks,
  -- Calculate the spread of clicks
  SAFE_DIVIDE(SUM(clicks), SUM(impressions)) AS aggregate_ctr
FROM
  `your_project.dataset.gsc_bulk_export`
WHERE
  date >= DATE_SUB(CURRENT_DATE(), INTERVAL 30 DAY)
GROUP BY
  query
HAVING
  url_count > 1
  AND total_impressions > 1000 -- Filter for significant volume
ORDER BY
  total_impressions DESC
```

**The Strategy:** When you find a high-volume query with a split URL count, the directive is clear: consolidate the content or differentiate the intent. This directly improves rankings.

### 5\. Forecasting Traffic Impact Based on CTR Models

Executives don’t care about “rankings”; they care about forecasted growth. **Data-driven SEO forecasting** requires modeling scenarios: *“If we move these keywords from position 5 to position 2, what is the revenue impact?”*

We can use SQL to apply a custom CTR curve (derived from your own historical data) to project traffic lift.

```
WITH current_performance AS (
  SELECT
    query,
    average_position,
    impressions
  FROM
    `your_project.dataset.gsc_data`
  WHERE
    average_position BETWEEN 3 AND 10 -- Focus on striking distance keywords
)

SELECT
  c.query,
  c.average_position,
  c.impressions,
  -- Current estimated traffic
  FLOOR(c.impressions * model_current.expected_ctr) AS current_clicks,
  -- Projected traffic if moved to Position 1
  FLOOR(c.impressions * model_top.expected_ctr) AS projected_clicks,
  -- The Delta
  (FLOOR(c.impressions * model_top.expected_ctr) - FLOOR(c.impressions * model_current.expected_ctr)) AS opportunity_gap
FROM
  current_performance c
JOIN
  `your_project.dataset.ctr_model` model_current ON ROUND(c.average_position) = model_current.position
JOIN
  `your_project.dataset.ctr_model` model_top ON model_top.position = 1
ORDER BY
  opportunity_gap DESC
```

**The Math:** $$ProjectedTraffic = Impressions \\times (NewPositionCTR)$$

This provides a prioritized list of keywords where the ROI of optimization is highest. You present this to the board, not a list of generic “best practices.”

* * *

## Automating the Output: From Query to Dashboard (The Application)

SQL is powerful, but raw code does not communicate value to stakeholders. A database table is not a deliverable. To operationalize this data, you must pipe the output of these queries into a visualization layer.

Once you have your clean dataset in BigQuery, connect it directly to **Looker Studio** or **Tableau**. This allows you to build dynamic dashboards that update automatically as new data flows into your warehouse. You are no longer building weekly reports; you are monitoring a live pulse.

By visualizing SQL data, you bridge the gap between technical complexity and executive clarity. You can show a live trend line of “Orphaned Pages” decreasing or “Projected Revenue” increasing. This is the foundation of an infrastructure that powers [automated competitive intelligence](https://nikoalho.fi/writing/competitive-intelligence/) and strategic decision-making.

* * *

## Estimate the traffic lift from a position gain

03

Working tool

Query Time Savings Calculator

Analysis queries run per week 

Avg manual time per query (min) 

Hourly rate € 

BigQuery cost per month € 

Automated query time (min) 

Monthly Impact

Manual time/month

Automated time/month

Time saved/month

Manual cost/month

Automated cost/month

Net savings/month

## The Directive: Stop Reporting, Start Architecting

The industry is full of “marketers” who copy-paste data into spreadsheets and call it strategy. That is not strategy; that is administration.

To secure **Technological Sovereignty**, you must own your data. You must be able to ask complex questions and get answers without waiting for a developer or crashing your computer.

**SQL** is the language of that ownership.

**The Directive:**

1.  **Audit your data capabilities.** If you are managing a 100k+ page site via CSV exports, you are negligent.
2.  **Enable GSC Bulk Export.** It takes five minutes to point it to a Google Cloud project.
3.  **Learn the logic, not just the syntax.** Don’t just learn how to write a query; learn *what* to query to expose revenue opportunities.

If you are ready to stop guessing and start engineering, it is time to build your data warehouse. This approach is essential for modernizing your reporting. Learn more about [visualizing SQL data](https://nikoalho.fi/writing/looker-seo-reporting/) to turn these queries into C-suite assets.

**Build the system. Eliminate the noise. Scale the revenue.**

Questions people actually ask

FAQ · 4

Q01 What SQL skills does an SEO actually need? +

SELECT, WHERE, GROUP BY, JOIN (especially LEFT JOIN), window functions (RANK, LAG), CTEs, and date functions. You don't need stored procedures or query optimization — just enough to join GSC + GA4 + CRM.

Q02 Why BigQuery over Snowflake or Redshift? +

Native connectors to GSC, GA4, Ads, and CrUX. Pay-per-query pricing works well for SEO data volumes. Snowflake and Redshift make sense if your data team is already there.

Q03 How do I get GSC data into BigQuery? +

GSC bulk data export (free, native) sends daily data to BigQuery automatically. Set it up once in GSC settings.

Q04 What's the simplest SEO SQL query worth running? +

JOIN GSC impressions with GA4 sessions and CRM closed-won deals on URL + date. The output is revenue-per-URL — the only metric that matters.

Sources & further reading

1.  \[01\]
    
    [GSC bulk data export](https://developers.google.com/search/blog/2023/02/bulk-data-export)
    
    Google Search Central
    
    DOC
2.  \[02\]
    
    [BigQuery for marketing](https://cloud.google.com/bigquery)
    
    Google Cloud
    
    DOC

INBOX · TWICE A MONTH

Notes from the lab, in your inbox.

The same pipelines I run for paying clients — written up first for subscribers.

Written for operators, not marketers

![Niko Alho](https://nikoalho.fi/assets/niko-alho-avatar-192.webp)

Niko Alho

I run agentic SEO and build custom AI for B2B companies. Based in Turku.

[About →](https://nikoalho.fi/about/)

KEEP READING

## More on lab.

-   [
    
    Lab 2026 · 05 · 20
    
    Solving Next.js hydration issues that tank SEO
    
    Hydration mismatches tank INP and ghost pages from Google's index. Diagnose with DevTools and Search…
    
    read →](https://nikoalho.fi/writing/hydration-nextjs-seo/)
-   [
    
    Lab 2026 · 05 · 20
    
    Localization engineering: scalable multilingual SEO architecture
    
    Plan multilingual SEO as engineering: hreflang logic, URL topology, CMS fields, canonical rules, loc…
    
    read →](https://nikoalho.fi/writing/localization-engineering/)
-   [
    
    Lab 2026 · 05 · 20
    
    Predictive search analytics: forecast demand before it spikes
    
    Predictive search analytics use Python forecasting to catch demand before competitors react. The Pro…
    
    read →](https://nikoalho.fi/writing/predictive-search/)

[More writing →](https://nikoalho.fi/writing/)

Direct with Niko · 20-min intro, no pitch [Book a slot →](https://nikoalho.fi/book/)

## Structured data

```json
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "@id": "https://nikoalho.fi/#website",
  "url": "https://nikoalho.fi/",
  "name": "Niko Alho",
  "description": "Agentic SEO and custom AI builds for B2B companies.",
  "inLanguage": "en",
  "publisher": {
    "@id": "https://nikoalho.fi/#person"
  },
  "potentialAction": {
    "@type": "SearchAction",
    "target": {
      "@type": "EntryPoint",
      "urlTemplate": "https://nikoalho.fi/search/?q={search_term_string}"
    },
    "query-input": "required name=search_term_string"
  }
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "Person",
  "@id": "https://nikoalho.fi/#person",
  "name": "Niko Alho",
  "givenName": "Niko",
  "familyName": "Alho",
  "url": "https://nikoalho.fi/about/",
  "image": "https://nikoalho.fi/og/default.png",
  "jobTitle": "Agentic SEO & Custom AI Consultant",
  "email": "mailto:contact@nikoalho.fi",
  "telephone": "+358401539426",
  "address": {
    "@type": "PostalAddress",
    "addressLocality": "Turku",
    "addressCountry": "FI"
  },
  "knowsAbout": [
    "Search Engine Optimization",
    "Agentic SEO",
    "Topical Authority",
    "Retrieval-Augmented Generation",
    "Large Language Models",
    "Custom AI Builds",
    "B2B SaaS Content Strategy",
    "Schema.org Structured Data",
    "Generative Engine Optimization"
  ],
  "knowsLanguage": [
    "en",
    "fi"
  ],
  "worksFor": {
    "@id": "https://nikoalho.fi/#organization"
  },
  "sameAs": [
    "https://www.linkedin.com/in/nikoalho/",
    "https://github.com/alhoniko"
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "ProfessionalService",
  "@id": "https://nikoalho.fi/#organization",
  "name": "Niko Alho — SEO & AI Automation",
  "alternateName": "Niko Alho",
  "description": "Agentic SEO and custom AI builds for B2B companies.",
  "url": "https://nikoalho.fi/",
  "image": "https://nikoalho.fi/og/default.png",
  "logo": "https://nikoalho.fi/assets/logo-mark.svg",
  "email": "mailto:contact@nikoalho.fi",
  "telephone": "+358401539426",
  "priceRange": "$$$",
  "founder": {
    "@id": "https://nikoalho.fi/#person"
  },
  "employee": {
    "@id": "https://nikoalho.fi/#person"
  },
  "knowsLanguage": [
    "en",
    "fi"
  ],
  "address": {
    "@type": "PostalAddress",
    "addressLocality": "Turku",
    "addressCountry": "FI"
  },
  "areaServed": [
    {
      "@type": "City",
      "name": "Turku"
    },
    {
      "@type": "City",
      "name": "Helsinki"
    },
    {
      "@type": "Country",
      "name": "Finland"
    },
    {
      "@type": "Place",
      "name": "European Union"
    },
    {
      "@type": "Place",
      "name": "Worldwide (remote)"
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "TechArticle",
  "@id": "https://nikoalho.fi/writing/sql-for-seo/#article",
  "headline": "SQL for SEO: the architecture that replaces spreadsheets",
  "name": "SQL for SEO: the architecture that replaces spreadsheets",
  "description": "Spreadsheets break past 100k rows. The SQL architecture and BigQuery schema I use to consolidate GSC, GA4, and crawl data into one queryable warehouse.",
  "image": "https://nikoalho.fi/og/sql-for-seo.png",
  "url": "https://nikoalho.fi/writing/sql-for-seo/",
  "datePublished": "2026-05-20T00:00:00.000Z",
  "dateModified": "2026-05-20T00:00:00.000Z",
  "inLanguage": "en",
  "isAccessibleForFree": true,
  "wordCount": 1802,
  "articleSection": "Lab",
  "keywords": "sql for seo, seo sql, bigquery seo, seo data warehouse, sql for search marketers",
  "author": {
    "@id": "https://nikoalho.fi/#person"
  },
  "publisher": {
    "@id": "https://nikoalho.fi/#person"
  },
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://nikoalho.fi/writing/sql-for-seo/"
  },
  "about": {
    "@type": "Thing",
    "name": "Lab"
  },
  "speakable": {
    "@type": "SpeakableSpecification",
    "cssSelector": [
      "h1",
      ".tldr",
      ".article-body > .prose > p:first-of-type"
    ]
  }
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://nikoalho.fi/"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Writing",
      "item": "https://nikoalho.fi/writing/"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "SQL for SEO: the architecture that replaces spreadsheets",
      "item": "https://nikoalho.fi/writing/sql-for-seo/"
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What SQL skills does an SEO actually need?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "SELECT, WHERE, GROUP BY, JOIN (especially LEFT JOIN), window functions (RANK, LAG), CTEs, and date functions. You don't need stored procedures or query optimization — just enough to join GSC + GA4 + CRM."
      }
    },
    {
      "@type": "Question",
      "name": "Why BigQuery over Snowflake or Redshift?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Native connectors to GSC, GA4, Ads, and CrUX. Pay-per-query pricing works well for SEO data volumes. Snowflake and Redshift make sense if your data team is already there."
      }
    },
    {
      "@type": "Question",
      "name": "How do I get GSC data into BigQuery?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "GSC bulk data export (free, native) sends daily data to BigQuery automatically. Set it up once in GSC settings."
      }
    },
    {
      "@type": "Question",
      "name": "What's the simplest SEO SQL query worth running?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "JOIN GSC impressions with GA4 sessions and CRM closed-won deals on URL + date. The output is revenue-per-URL — the only metric that matters."
      }
    }
  ]
}
```