GA4 for SEO comes down to three moves: filter every report to organic sessions, report on landing pages instead of vanity pageviews, and mark real business actions as Key events so you can prove organic traffic converts. This guide walks through the exact setup, the specific reports and dimensions to use, and the gotchas that quietly break your organic numbers.
Most of the friction people hit isn't GA4 being worse — it's that the model changed. Once you stop looking for Universal Analytics metrics that no longer exist and learn the new dimension names, GA4 is a sharper SEO tool than UA ever was.
Why GA4 is different from Universal Analytics for SEO
Universal Analytics was session-based: everything hung off sessions and pageviews. GA4 is event-based — a page view, a scroll, a click and a form submit are all events with parameters. That single shift renames or removes almost every metric you used to report on.
For SEO work, three changes matter most:
- Bounce rate is gone (mostly). GA4 leads with Engagement rate — the share of sessions that lasted 10+ seconds, fired a Key event, or had 2+ pageviews. It's a far better signal of whether an organic landing page actually held the visitor. GA4 does expose a bounce rate again, but it's just the inverse of engagement rate, so lean on engagement.
- Organic lives in a channel group. In UA you filtered by
Medium = organic. In GA4 you use Session default channel group = Organic Search, or the more precise Session source / medium = google / organic. - Free BigQuery export. GA4 streams raw events to BigQuery at no cost — impossible on free UA. For serious organic traffic analysis that's a genuine upgrade.
| Task | Universal Analytics | GA4 |
|---|---|---|
| Isolate organic traffic | Medium = organic | Session default channel group = Organic Search |
| Engagement quality | Bounce rate | Engagement rate / engaged sessions |
| Landing page report | Behaviour → Landing Pages | Explorations (custom) or Landing page report |
| Goal / conversion | Goals | Key events |
| Raw data export | Paid (360 only) | Free BigQuery export |
The practical takeaway: don't try to rebuild your old UA dashboard. Rebuild the questions — which pages earn organic traffic, do those visitors engage, and do they convert — using GA4's vocabulary. For the metrics that actually deserve a scorecard, see our guide to SEO KPIs.
Essential GA4 setup: events, conversions and Search Console linking
Before any report is trustworthy, do this checklist once per property.
- Confirm Enhanced Measurement is on. In Admin → Data streams → your web stream, Enhanced Measurement auto-collects scrolls, outbound clicks, site search and file downloads. For SEO, site search and scroll depth are the useful ones.
- Extend data retention to 14 months. Admin → Data settings → Data retention. The default is 2 months, which will silently starve your Explorations of history. Bump it to 14.
- Define Key events (conversions). Decide the actions that represent business value — lead form submit, signup, purchase, phone tap, demo booked. Create them as events (via GTM or gtag), then in Admin → Events toggle Mark as key event.
- Link Google Search Console. Admin → Product links → Search Console links. This unlocks two reports inside GA4: Queries and Google organic search traffic. You must also publish them by editing the report collection in the Library so they appear in the left nav.
On Search Console linking: it's worth doing, but keep expectations honest. Search Console and GA4 count different things — clicks vs sessions, its de-duplication vs GA4's — so the totals never match. Use Search Console for queries, impressions and position; use GA4 for post-click behaviour. The pairing is covered end-to-end in our Search Console performance report walkthrough.
Building an organic-traffic landing page report
The single most useful SEO report in GA4 is a landing page report scoped to organic. The built-in Landing page report (Reports → Engagement → Landing page) is fine for a quick look, but you can't segment it cleanly, so build a custom one in Explorations.
Here's the recipe:
- Open Explore → blank exploration → Free form.
- Rows: add the dimension Landing page + query string (or just Landing page).
- Values: add Sessions, Engagement rate, Average engagement time, and your Key event (e.g.
generate_lead). - Segment: create a segment where Session default channel group exactly matches Organic Search, and drop it on the report.
- Sort by Sessions descending.
You now have, in one table, every page earning organic traffic, how engaged those visitors are, and how many converted. That's the backbone of an SEO reporting dashboard — and it answers the question executives actually ask: which pages are pulling their weight?
If a top-traffic page has an engagement rate well below your site average (say under 40% when the site sits at 60%), that's a content or intent-match problem worth a rewrite — not a ranking problem.
Segmenting organic sessions with explorations
Segments are where GA4 earns its keep for SEO. Beyond the basic "organic only" segment, build these:
- Organic + converters: Session default channel group = Organic Search AND includes a Key event. Overlay it against all organic sessions to see what the converting cohort did differently — which pages, which devices.
- Organic + new users: isolate first-time organic visitors to judge how well pages perform for cold traffic from search.
- Organic by device: if organic mobile engagement lags desktop by 15+ points, you likely have a Core Web Vitals or layout problem, not a content one.
GA4 supports session-scoped and user-scoped segments. For SEO, session-scoped is almost always what you want — you're analysing what happened in the visit that started from search, not the person's entire lifetime. Building segments well is the difference between surface numbers and real SEO attribution.
One quiet win: comparison mode. In any standard report you can add a Comparison (e.g. Session default channel group exactly matches Organic Search) instead of a full exploration segment — faster for quick checks, no exploration needed.
Tracking SEO conversions and engaged sessions
Traffic without conversion is a vanity metric. GA4's Key events let you connect organic landing pages to outcomes — the whole point of tracking SEO conversions.
Once a Key event is defined, GA4 attributes it using its default data-driven attribution model, but for landing-page SEO analysis you often want last-click within the session thinking — "this organic page started the session that converted." In an exploration, adding your Key event as a value against the Landing page dimension gives you exactly that page-level view.
Pair Key events with Engaged sessions and Engagement rate as leading indicators. A page might get few conversions simply because it sits top-of-funnel — but if it drives high engagement and assists later conversions, it's doing its job. Judging pages purely on last-click conversions punishes good informational content. This nuance matters when you tie effort to revenue, which we cover in SEO ROI and how to measure SEO success.
Custom SEO dashboards and shareable reports
Explorations are powerful but personal — they don't share cleanly with clients or executives. For shareable output you have two routes:
- GA4 Library (Reports → Library): build a custom report collection with a Traffic acquisition report pre-filtered to organic and a Landing page report. Publish it so stakeholders see a clean, GA4-native "SEO" collection in the left nav.
- Looker Studio: connect GA4 as a data source for a polished, branded dashboard. This is the standard for client reporting — you can blend GA4 with Search Console and your rank tracker in one view.
For rankings, GA4 has no idea where you rank — it only sees post-click behaviour. Pair it with a dedicated tracker like DeployFlare's rank tracker so your dashboard shows position, clicks and on-site conversion side by side. That combination — ranking → click → engagement → conversion — is the complete SEO funnel, and no single tool covers all of it.
Keep dashboards to 6–8 tiles: organic sessions trend, top organic landing pages, organic engagement rate, organic Key events, top queries from Search Console, and a device split. More than that and no one reads it.
GA4 gotchas that skew organic data
These are the traps that make people distrust their numbers.
- Data thresholding. When Google Signals is on and a report has low volume, GA4 hides rows to protect anonymity, showing totals that don't add up. Fix: switch the reporting identity to Device-based (Admin → Reporting identity) if precision matters more than cross-device stitching.
- (not set) landing pages. Caused by page_view not firing first, consent-mode modelling, or session_start races. Ensure page_view fires reliably and widen the date range.
- Sampling in large explorations. Big date ranges + complex explorations trigger sampling — check the green/yellow icon top-right. Narrow the range or use BigQuery for unsampled data.
- Session vs event scope confusion. Filtering by event source/medium instead of session source/medium will misattribute organic traffic. For landing-page SEO, always use Session source / medium.
- Bounce rate nostalgia. GA4's bounce rate is not UA's. Don't compare them or set targets against old benchmarks — use engagement rate instead. This is a common thread in our take on bounce rate for SEO.
Get the setup right once — retention at 14 months, Key events marked, Search Console linked, session-scoped segments saved — and GA4 becomes a reliable, sharp instrument for organic search. Skip the setup, and you'll spend months arguing about numbers that were never trustworthy in the first place. Start from the SEO analytics overview if you want the full measurement stack in order.