SEO data integration: combine Search Console, GA4 and your leads
Short answer Join your SEO data by page and month, not by keyword. Search Console totals clicks per page, never per visitor, so no tool can tie one search to one customer. A monthly spreadsheet or Data Studio report covers most small sites. Google aims BigQuery's bulk export at sites with tens of thousands of pages or queries.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callHow to combine Search Console and GA4 data: match on the page
Line up your sources by page address and month. Search Console counts what happened on Google before the click. GA4 counts what the visitor did after it. Your lead list says who became a customer. The page each visitor landed on is what all three share.
Google names the fields to join on:
"If you want to blend or join the data to see per-query data, you could use the country, device, landing page dimensions." (Google Search Central: Using Search Console and Google Analytics data for SEO)
| Source | What it knows | Join on |
|---|---|---|
| Search Console | Impressions, clicks and searches per page, before the visit | Page and month; country and device if needed |
| GA4 | Visits and key events (forms, calls, bookings) per landing page | Landing page and month |
| Your lead list or CRM (customer database) | Booked jobs and revenue | The first page the lead saw |
| Rank tracker or backlink tool | That tool's own estimates | Page |
Can you see which keywords bring customers?
Not search by search. Search Console data arrives already totaled: Google describes its exported tables as data "aggregated by property" or "aggregated by URL" (Google Search Central Blog: Bulk data export). No single visitor is in it to match to a customer. So answer it in two steps:
- Which pages bring customers? GA4 and your lead list, by landing page.
- Which searches reach those pages? Search Console: Performance, filter to the page, then the Queries tab.
Two more limits:
- Rare searches are hidden. Google leaves out "anonymized queries", ones that "aren't issued by more than a few dozen users over a two-to-three month period" (Google Search Central Blog: A deep dive into Search Console performance data). They still count in chart totals, so query rows won't add up to the total.
- Keep customer names out of GA4. Its terms bar sending Google personally identifiable information, "hashed or otherwise", outside specific features that accept hashed data (Google Analytics Terms of Service). Join leads in your own sheet, by page and month, never by person.
The no-cost way: a monthly spreadsheet
- Search Console. Performance report, last month, Pages tab. Click Export, then Google Sheets (Google Search Central Blog: Connecting Search Console to Data Studio). The export holds up to 1,000 rows (Google Search Central Blog: deep dive).
- GA4. The Landing page report filtered to google / organic, as Google's guide suggests. Export visits and key events per page. Key events must be set up first: GA4 key events.
- Your lead list. Count booked jobs and revenue by first page. A hidden form field that saves the page address does this; otherwise use each lead's "How did you hear about us?" answer.
- Match the addresses. Search Console reports only the canonical URL (the version Google treats as the main one); GA4 reports every address its tag fired on (Google Search Central). Trim both to one form, such as /water-heater-repair/.
- Join. One row per page; pull the other sheets in with VLOOKUP or XLOOKUP on the page column.
- Keep the file. Search Console shows 16 months. For longer, Google suggests the API or bulk exports "to pull data and store it in your systems" (Google Search Central: Debugging drops in Google Search traffic). A saved sheet each month does the same.
Then read each row:
| Pattern on a page | Likely problem | Where to look |
|---|---|---|
| Many impressions, few clicks | Title and description don't earn the click | On-page SEO for service pages |
| Clicks, no leads | Calling or booking isn't easy | Website not getting leads |
| Leads that rarely book | Slow follow-up or poor-fit leads | Speed to lead |
| Leads, few impressions | The page works but few see it | More content on that service |
Ready-made options. Google's dashboard template shows Search Console and GA4 side by side in Data Studio, called Looker Studio until April 2026 (Google Cloud Blog). When it asks for a Search Console table, pick URL Impression, as the template says: it's totaled by page, which is what you join on. Data Studio's blending feature joins Search Console to your own table, such as page categories (Google Search Central Blog: Blending Search Console and internal data). Data Studio is "available at no charge for creators and report viewers" (Google Cloud: Data Studio pricing). Linking Search Console to GA4 adds a few reports inside GA4 with the queries and landing pages behind Google organic traffic, and on WordPress, Google's Site Kit plugin shows both in one dashboard (Google Search Central).
Do you need BigQuery for SEO data?
Probably not with one location or a few hundred pages. BigQuery is Google Cloud's data warehouse, a database you query in SQL. Search Console can copy your data into it daily (the bulk data export), and GA4 can send all its raw events (Google for Developers: BigQuery export for Google Analytics). Google says who the bulk export is for:
"This data export could be particularly helpful for large websites with tens of thousands of pages, or those receiving traffic from tens of thousands of queries a day (or both!)." (Google Search Central Blog: Bulk data export)
Small and medium sites, the post adds, already reach all their data in Search Console, the Data Studio connector or the API.
| Need | Without BigQuery | With the bulk export |
|---|---|---|
| More than 1,000 rows | Connector or API: up to 50,000 rows per day, per site, per search type | No daily row limit |
| History past 16 months | Save a sheet each month | Kept until you set an expiration |
| Rare searches | Hidden | Still hidden (query left blank) |
| Data from before you start | In the reports, up to 16 months | Not loaded |
| Joining large internal tables | Slow in a spreadsheet | SQL joins |
What does BigQuery cost?
Search Console charges nothing to export; BigQuery bills storage and queries (Google Search Central Blog: BigQuery efficiency tips). Google Cloud's prices as of November 2026, in US dollars:
| Item | Free each month | After that |
|---|---|---|
| Storage | First 10 GiB | Billed per GiB, by the hour |
| Queries (on-demand) | First 1 TiB of data read | $6.25 per TiB |
Source: Google Cloud: BigQuery pricing. Paying in Canadian dollars or another currency, Google Cloud's prices in that currency apply.
- Billing is required. "You must set up a Google Cloud project with billing and enable BigQuery" (Search Console Help: Start a new bulk data export). The no-card BigQuery sandbox can't keep an archive: its tables "automatically expire after 60 days" (Google Cloud: Try BigQuery using the sandbox).
- Cap the bill. Set a budget alert, and a bytes limit per query; a query over the limit "fails without incurring a charge" (Google Search Central Blog: BigQuery efficiency tips).
- Read less. Google calls SELECT * "the most expensive way to query the data", and LIMIT "does not affect the amount of data read" (same post). Filter by date, and feed dashboards a daily summary table, not the raw tables.
How to set up the Search Console bulk export
Only a property owner can (Google Search Central Blog: Bulk data export). From Search Console Help:
- In Google Cloud, pick a project with billing. Enable the BigQuery API and BigQuery Storage API.
- Under IAM, give search-console-data-export@system.gserviceaccount.com two roles: BigQuery Job User and BigQuery Data Editor.
- In Search Console, open Settings, then Bulk data export. Enter the project ID (not the number), a dataset name and a location. You "can't easily change this location later".
- The first export arrives within 48 hours with that day's data. For earlier data, Google points to the API or the reports.
- Optional: a partition expiration of 14 days or more caps storage. Don't add columns: "Schema changes will cause the export to fail."
- The export makes two tables: one totaled by site, one by page (Google Search Central Blog: Bulk data export). Join the page table, searchdata_url_impression, to your GA4 export and lead table by date and page.
Why the numbers never match
"Clicks and sessions are calculated differently, which means that when you compare the data, you'll likely see different numbers." (Google Search Central: Using Search Console and Google Analytics data for SEO)
| Cause | What happens |
|---|---|
| Time zone | Search Console uses Pacific Time, unchangeable; GA4 uses yours |
| Cookie consent | Visitors who opt out are missing from GA4 |
| Canonical URLs | Search Console reports only canonical URLs; GA4 any tagged URL |
| Bots | GA4 drops known bots; Search Console doesn't necessarily |
| PDFs and other files | Search Console counts them; GA4 may not track them |
Source: the same Google guide. A small gap is "normal and expected"; check that trends move together. Joining by month blunts the time-zone shift.
Example
Illustrative cases. Numbers are invented for the example.
A plumber's monthly sheet (US dollars)
Twelve service pages, one row each. Water heater repair: 2,400 impressions, 40 clicks, 6 form leads, 4 booked jobs worth $3,200. Drain cleaning: 300 clicks, 2 leads, no jobs. Next month: a sharper title for the water heater page, and a call button at the top of the drain page.
A Toronto accounting firm asking about BigQuery (Canadian dollars)
Forty pages, well under 1,000 query rows a month. It skips BigQuery, saves a sheet monthly so its history outlasts Search Console's 16 months, and spends $0.
An online parts store with 30,000 product pages (US dollars)
It turns on the bulk export, sets a $50 monthly budget alert, builds one daily summary table for its dashboard, and joins the URL table to its product categories.
FAQ
Can I link Search Console to Google Analytics 4?
Yes. GA4 then shows the queries and landing pages behind Google organic traffic. Joining leads still needs a sheet, Data Studio or BigQuery.
Is the Search Console BigQuery export free?
The export is. BigQuery bills storage over 10 GiB and queries over 1 TiB a month, and needs a billing account.
Can the Search Console API split branded and non-branded searches?
Yes, since November 16, 2026, for eligible properties. For others, "the response won't include any rows" (Google Search Central Blog: Search Analytics API update).
Different for you?
- Search Console isn't set up: Search Console for a small business.
- You only need the monthly numbers: is my SEO working?.
- You want your agency's report to show leads: the report to ask for.
- You want Google Ads to learn which leads booked: tracking a lead to a booked job.
- You run a US clinic: Google Analytics on a clinic website.
- You'd rather have every lead tracked to the booking for you: Conversion Agent.