Universal Analytics stopped collecting data in mid-2024, which means every SEO now works in GA4 whether they’ve fully adjusted to it or not. GA4 is built around events rather than pageviews and sessions the way UA was, and that shift changes which reports actually answer an SEO’s questions. This guide covers correct setup and the report set worth checking regularly — not every GA4 feature, just the ones that matter for organic performance.
Setting Up a GA4 Property Correctly
Every GA4 install should start with a Google-tag (gtag.js) or Google Tag Manager container placed once, sitewide — duplicate tags are the single most common cause of inflated pageviews and sessions in GA4 data. Set the correct time zone and currency before any real traffic arrives, since both are effectively locked in for historical data once reporting has started.
Enable Google Signals only if you actually need cross-device reporting and are comfortable with the consent implications, and set data retention to the maximum available (currently 14 months) rather than the two-month default — the default silently truncates year-over-year comparisons in Explorations.
The Reports That Matter for SEO
Three reports do most of the SEO-relevant work: Acquisition > Traffic acquisition (which channel, including Organic Search, drove sessions), Engagement > Pages and screens (which content actually holds attention), and Explorations (custom cross-tabs GA4’s stock reports don’t offer). The old dedicated “Landing Pages” report from Universal Analytics doesn’t exist by that name in GA4 — the closest equivalent is built from Pages and screens filtered or segmented by session source, covered in more depth in our Landing Page report guide.
For a first-pass sense of organic health across a period, Traffic acquisition segmented to Organic Search, viewed alongside engagement rate rather than bounce rate (a metric GA4 doesn’t use the same way UA did), gives the most honest read of whether organic visitors are actually engaging.
Linking Search Console
Search Console links to GA4 at the property level under Admin > Product links, and once connected it surfaces a Search Console report inside GA4’s Acquisition section — query and landing-page data GA4 cannot generate on its own. This link is one-directional (GSC data flows into GA4’s reporting UI); it does not merge the two data models, and each still has blind spots the other fills, which is exactly what our GSC vs GA4 article walks through in detail.
Common Setup Mistakes
The most common issue is a duplicated or looping tag firing twice per pageview, which silently doubles session and pageview counts without throwing any visible error. Check this early using GA4’s DebugView (Admin > DebugView, with the tag’s debug mode enabled) rather than waiting for numbers to look suspicious weeks later. The second most common issue is leaving data retention at the two-month default, which quietly breaks any Exploration built on a longer comparison window.