Search teams who learned analytics in the Universal Analytics era have spent the last two years rebuilding muscle memory. Universal Analytics stopped processing hits on July 1, 2023, and historical UA data was wiped from the interface on July 1, 2024. The replacement, Google Analytics 4, is a different product with a different data model, a different reporting layout, and a different relationship with Search Console. If your SEO reporting still feels clumsy, you are not alone.
This guide is the practical version. No certification fluff, no screenshots of menus that Google will move next quarter. You will see exactly which GA4 reports answer SEO questions, how to wire GA4 to Search Console without losing data, which metrics to trust, and how to spot a ranking problem before it becomes a traffic problem. Use it as a working manual, not a tour.
We will assume you already have a GA4 property installed via Google Tag or GTM and that data is flowing. If you are still on UA, stop reading and migrate. There is no way to do google data analytics for SEO on a property that does not collect events. Once your GA4 setup is live, the next decision is which reports become your weekly habit.
One quick orientation note before we dive in: GA4 is event-based, not session-based. Every pageview, scroll, click and form submit is an event. Sessions still exist as a derived metric, but the underlying unit is the event. That single change explains why old SEO dashboards stopped working overnight and why a fresh approach makes more sense than porting UA habits over.
Universal Analytics counted a session as a 30-minute container of user activity. Bounce rate meant any single-page session. Goal completions were configured one at a time. Most SEO dashboards lived on three numbers: organic sessions, bounce rate, goal completions. GA4 deprecated that worldview entirely.
In GA4 the headline engagement metric is engagement rate, the inverse of bounce rate but calculated very differently. A session counts as engaged when it lasts more than 10 seconds, fires a conversion, or has 2+ pageviews. Bounce rate still exists as a metric you can add to reports, but it is no longer the default. For SEO that is good news. The old UA bounce rate punished long-form content where a reader landed, read 1,800 words, and left satisfied. GA4 treats that as engaged.
UA used a hit-based model with pageviews, events, transactions and social as separate hit types. GA4 collapses everything into events. For SEO this means custom events (scroll, file_download, outbound_click) are first-class citizens, not awkward add-ons. You can mark any event as a conversion with two clicks in Admin.
Sessions are still calculated, but a new session triggers after 30 minutes of inactivity OR at midnight in the property time zone, not on a UTM parameter change. That detail matters when you analyze paid-to-organic crossover.
GA4 install is one tag (Google tag, gtag.js) or one container (GTM). Enhanced measurement turns on automatically and captures scrolls, outbound clicks, site search, video engagement and file downloads with no extra code. Many SEOs miss this and double-tag scroll tracking. Check the Enhanced Measurement toggle in Admin → Data Streams before adding anything custom.
Cross-domain tracking is configured in the UI rather than in the snippet — Admin → Data Streams → Configure tag settings → Configure your domains.
The Reports section is grouped into Life cycle (Acquisition, Engagement, Monetization, Retention) and User. For SEO you live in Acquisition → Traffic acquisition and Engagement → Pages and screens. The classic UA "Channels" report is now "Traffic acquisition" with the Default channel group dimension. Filter for "Organic Search" and you have your daily SEO report.
Explore (formerly Analysis Hub) is where you build segment overlaps, funnels and free-form tables that the standard reports cannot produce.
UA goals were limited to 20 per view and required configuration per type (destination, duration, pages/session, event). GA4 lets you mark any event as a conversion — up to 30 conversion events per property. Better yet, conversions count every occurrence by default, not once per session, so multi-touch attribution becomes possible.
For SEO this means you can track scroll depth as a content-quality conversion, outbound clicks as a referral conversion, and form starts vs. form submits as a funnel.
The single highest-leverage move in GA4 for SEO is linking Google Search Console. Without the link you are flying blind on impressions, queries, and average position. With the link, two pre-built Search Console reports appear inside GA4: Queries and Google organic search traffic. These pages join GSC click and impression data to GA4 engagement and conversion data, which is exactly what you need to prove that a top-ranking page actually converts.
To enable the link, open Admin → Product links → Search Console links → Link. Choose the Search Console property and the GA4 web stream. After the link is live, publish the Search Console reports in the Library: Reports → Library → Search Console collection → Publish. Until you publish them, the reports exist but are hidden from the left nav. This is the single most common GA4 setup mistake — the link is created but the reports are never published.
Once published, you can finally compare clicks (GSC) against sessions (GA4) on the same page. The two numbers will never match exactly. GSC counts clicks from Google search results. GA4 counts sessions, which include direct entrances, returning visitors and non-Google organic. A 10–20% gap is normal. A 50%+ gap usually means tracking is broken on the landing page or a redirect is dropping the referrer. Use the gap as a diagnostic, not a reconciliation target.
One important nuance: GSC data in GA4 is aggregated daily and lags 24–48 hours. If you need today's queries, use Search Console directly. For trend analysis and joining query data to conversion data, GA4 is the better surface. Pair this with a deeper read on google analytics website traffic to see how the joined view fits a full traffic audit.
You do not need every GA4 report. You need five, opened in the same order, every Monday morning. Each answers one question.
The Traffic acquisition report (Reports → Acquisition → Traffic acquisition) tells you how organic sessions trend week over week. Add a comparison for "Session default channel group exactly matches Organic Search" and you have a clean SEO-only view. Add Landing page as a secondary dimension to see which pages drove the change.
Landing page report (Reports → Engagement → Landing page) is the deepest SEO surface in GA4. It shows sessions, engaged sessions, average engagement time per session, event count, conversions and total revenue per landing page. Filter by organic search and sort by sessions descending. The first 20 rows are your money pages.
Pages and screens (Reports → Engagement → Pages and screens) breaks engagement down by page path, not entrance page. Use it to spot mid-funnel content that gets internal traffic but no organic entries — those are link-equity sinks that need promotion.
Queries (Reports → Search Console → Queries) shows the search terms driving impressions and clicks. The hidden gem here is the click-through rate column. Sort by impressions descending and filter for CTR below 2%. Those are pages that rank but do not earn the click — usually a title tag or meta description issue.
Weekly organic session trend. Filter Default channel group = Organic Search. Add Landing page as secondary dimension.
The single most useful SEO surface. Shows sessions, engagement, conversions and revenue per landing page.
Engagement by page path, regardless of entry. Use to find pages that get internal traffic but few organic entries.
Impressions, clicks, CTR and average position per query. Filter low CTR + high impressions for title-tag wins.
Same as Queries but pivoted by landing page. Shows GSC clicks alongside GA4 sessions and conversions.
GA4 ships with a few default events but no SEO-specific conversions. You have to mark them yourself. The four that earn their keep on a content site are scroll depth (set at 75% or 90% to filter skimmers), outbound_click for affiliate or partner links, file_download for PDFs and study guides, and form_submit for newsletter or lead-gen captures. Enhanced measurement captures the first three automatically — open Admin → Data Streams → Configure tag settings → Enhanced measurement and check that they are toggled on.
To mark one as a conversion, go to Admin → Events, find the event, toggle the Mark as conversion switch. Wait 24 hours and the event will start showing up in conversion reports. Note that scroll fires at 90% by default, which is too lenient for SEO — readers can scroll past in seconds.
Custom scroll thresholds at 50% and 90% require a small GTM trigger using the Scroll Depth variable; once set, you can compare drop-off between the two on long-form articles. If you also write or audit articles, compare conversion-event firing against the topical coverage of your own google analytics certification walkthroughs to spot where readers drop off.
For form submissions, the cleanest pattern is a GTM trigger on form submit with the form ID as a parameter. That lets you track which forms convert without polluting the event list. If you cannot reach the form via GTM (third-party embed, single-page app), use the GA4 measurement protocol to send a server-side event from your form handler.
Headline organic sessions never tell the full story. Segmentation does. The four segments worth building in Explore are organic mobile vs desktop, organic by country (especially if you have hreflang variants), organic by landing page directory (/blog, /pricing, /docs), and branded vs non-branded organic.
Branded vs non-branded is the segment most SEOs skip and the one that matters most. To build it, open Explore → Free form → add a segment → Session source/medium contains "google / organic" AND Page referrer NOT contains your brand name. That filters out brand-name searches that would inflate organic numbers. Compare branded and non-branded over the same period and you will see which one is actually growing.
For the device segment, the GA4 Device category dimension splits mobile, desktop and tablet cleanly. Layer this on top of Landing page and you can see whether mobile rankings are bringing in less qualified traffic than desktop — a sign that mobile UX is lagging or that mobile SERPs are showing zero-click features above your result.
Country segmentation matters once you cross one international border. GA4's geographic data is reliable down to the country level and often down to the region. City-level data is approximate. For SEO reporting, country and region are enough — drill into the city level only when chasing a specific local query.
The earliest warning sign of an SEO problem in GA4 is not a sessions drop. It is an engagement-rate drop on a single landing page. If a top-20 organic page sees engagement rate fall from 65% to 45% week over week while sessions hold steady, the SERP feature above your result has changed, the snippet was rewritten by Google, or the page itself is mismatching intent. Catch it here and you have two weeks before sessions follow.
The second warning sign is rising impressions in Search Console alongside falling clicks. That means you ranked for more queries but earned fewer clicks per query — usually because Google added an AI Overview, a featured snippet from a competitor, or a People Also Ask block above your result. Open the Queries report, filter for the page, and look for queries that newly appeared with high impressions and zero clicks. Those are the AI Overview captures.
A third pattern: exit-page surges on conversion-critical pages. GA4 does not have a dedicated Exit page report like UA, but you can build one in Explore by adding Page path and Exits as metrics. A pricing or checkout page where exits suddenly spike usually means a CTA broke, a price changed, or a third-party script slowed the page. SEO sends the traffic but conversion lives or dies here. If you are also tracking the same patterns for exam prep audiences, compare against landing page engagement on google analytics test traffic to confirm whether the issue is page-specific or category-wide.
AI search engines — Perplexity, ChatGPT search, Claude, Google AI Overviews — send referral traffic that does not appear under Organic Search in GA4. They land in Referral with hostnames like chat.openai.com, perplexity.ai, www.bing.com (Copilot), and gemini.google.com. To see AI search traffic, open Reports → Acquisition → Traffic acquisition, change the dimension to Session source / medium, and filter for those hostnames.
For ongoing tracking, build a custom channel group in Admin → Data Settings → Channel groups. Add a channel called "AI Search" with the rule Source contains any of (chat.openai.com, perplexity.ai, gemini.google.com, copilot.microsoft.com, you.com, claude.ai). Volumes are still small for most sites (1–3% of organic) but growing fast and biased toward high-intent visitors. Engagement rate on AI-search traffic tends to run 10–15 points higher than Google organic.
AI Overviews are different — they are inside Google search results, so clicks from them appear under Organic Search, not Referral. The signal is indirect: impressions up, clicks flat or down in GSC. Combine that with Bing Webmaster Tools data (where Bing Chat citations appear) and you have a rough AI-citation tracker. For a deeper baseline on the certification side of analytics knowledge, see our google analytics iq exam walkthrough.
The first mistake is leaving data retention at the 2-month default. Open Admin → Data Settings → Data Retention and switch to 14 months. Without this, year-over-year reporting becomes impossible after 60 days and any cohort analysis is capped. This is a 30-second fix that 60% of GA4 properties never apply.
The second mistake is treating GA4 sessions as equivalent to UA sessions. They are not. GA4 starts a new session on inactivity OR at midnight, and GA4 sessions cross channel boundaries. A user who arrives via organic and clicks an email link within the same session keeps the organic attribution. UA would have started a new session on the UTM. This makes paid-to-organic crossover look different — neither right nor wrong, just different.
The third mistake is not setting up cross-domain tracking. If your blog runs on a subdomain or a different domain than your main site, GA4 will count the cross-domain hop as a referral unless you list both domains in Admin → Data Streams → Configure tag settings → Configure your domains. Without that step, organic traffic to the blog that converts on the main site looks like blog-referral instead of organic.
The fourth mistake is using engagement rate as the only quality metric. Engagement rate is broad — it counts 10-second sessions as engaged. For long-form content, layer on average engagement time per session and scroll-90% completion rate. The combination tells you whether readers stayed and finished, not just whether they did not leave instantly. For one more reference point on the metrics-and-analytics knowledge layer, the google analytics covers the conceptual side that anchors these reports.
A defensible monthly SEO report has six sections and takes about an hour to build once the templates are in place. Section one: organic sessions and engagement rate, month-over-month and year-over-year, with a one-line explanation of any 10%+ change. Section two: top 20 landing pages by organic sessions, sorted descending, with new entries flagged. Section three: top 20 organic queries from the GSC link, with average position trend.
Section four: SEO conversions count and conversion rate, by landing page. Section five: AI search referral traffic, even if small. Section six: a list of three to five recommendations for the next month — pages to update, queries to chase, technical fixes flagged. Skip the screenshots-of-everything approach. Five numbers explained well beat fifty numbers presented without context. If you want to test what you know against the official certification curriculum, the google analytics individual qualification path is the closest thing to a structured curriculum on the topic.
The reporting tool itself matters less than the discipline. Some teams stay in the GA4 UI and screenshot reports. Others build Looker Studio dashboards (free, fast, real-time). Larger teams export to BigQuery for SQL-level analysis. All three are valid. The smallest team can run a perfectly good SEO program on the GA4 UI plus a Looker Studio dashboard refreshed monthly.