How to Join Search Console and GA4 by Landing Page

Rakibul SumonRakibul Sumon
Published: Nov 18, 2026
How to Join Search Console and GA4 by Landing Page

TL;DR Summary

Build a page-level SEO report from Search Console and GA4. Normalize URLs, avoid inflated totals, and connect Google search traffic to key events.

I join Search Console and GA4 when I want to know which pages were visible in Google and what people did after landing. Start with one row per landing page per week in each source. That is the most important decision in the report.

Export one row for each page and week

From Search Console, use Web search and export the Pages table for a complete week. Keep the page URL, clicks, and impressions. In GA4, filter to Google organic using a session-scoped source and medium. Export landing pages, sessions, and the key event you care about, such as confirmed demo requests.

  • Search Console. Join columns are week and normalized host plus path. Metrics are clicks and impressions.
  • GA4. Join columns are week and normalized host plus path. Metrics are sessions and demo key events.

If the site uses several hosts, preserve the landing host in the reporting data, or restrict GA4 to a single known host before joining on path. Choose a common week and note any difference in reporting time zones. Google's Search Console connector docs describe the available tables.

Use the URL Impression table in the reporting connector for landing-page analysis.

The reports join on week and normalized URL after each source has one unique row per key.

Normalize only URL variants you've checked

Strip tracking parameters when they don't change the content. Keep parameters that identify different pages. Verify redirects and slash variants before mapping old addresses to new ones. Keep the original value in the raw report and map the destination in a separate column. Lowercase hostnames as needed. Paths may be case-sensitive.

Aggregate both sources to unique keys first. Start with a full outer join so mismatches stay visible. A Search Console row without a GA4 match can reflect a redirect, a missing tag, low volume, property scope, or an incomplete mapping. Keep a missing source distinct from a measured zero while you troubleshoot.

Growth mechanics, zero fluff.

Join SaaS founders and operators getting weekly notes and tear-downs on organic acquisition and churn reduction.

Catch duplicate totals before anyone uses the report

Imagine three query rows for one guide and a single GA4 row with 40 sessions and four demo events. Joining them directly can repeat the GA4 metrics three times, resulting in 120 sessions and 12 demo events in the totals.

Check that each key is unique and reconcile the totals with source reports. Calculate CTR by dividing summed clicks by summed impressions. For a session key event rate, use the share of sessions with the key event. Raw events divided by sessions can exceed one and describes a different metric.

Use the query report next to the landing-page view to understand intent. For the wider pipeline view, see SaaS SEO metrics from search to qualified pipeline.

Rakibul Sumon

Written by · SaaS Growth Marketer

Rakibul Sumon

SaaS growth marketer who learns deeply, experiments openly, and shares results publicly. Focused on content-led SEO, brand positioning, and building growth systems that compound over time.

Learning In Public

SaaS growth insights,_

No hype, no recycled advice - just honest experiments, frameworks, and lessons from the trenches, delivered when there's something worth sharing.

No spam, ever. Unsubscribe anytime.