The measurement problem most SEO teams encountered when Universal Analytics stopped processing data in July 2023 was not that GA4 lacked features; it was that GA4's data model is different at the architectural level, and the reports that SEO teams relied on in UA do not have direct GA4 equivalents. Teams that rebuilt their reporting by looking for the UA report name in GA4 and accepting the closest match ended up with metrics that answer different questions than they appeared to, and year-on-year comparisons that are unreliable by design rather than by error.
UA was session-based: every visit created a session, and all subsequent interactions within that session were attributed to the traffic source that initiated it. GA4 is event-based: every interaction is an individual event with its own parameters, and the session is constructed from events rather than events being contained within a session. The practical consequence for SEO measurement is that the organic traffic figure in GA4 can look materially different from the equivalent UA figure for the same time period, even accounting for the model change. Neither is wrong; they are measuring different constructs.
This article identifies the specific GA4 reports and Exploration paths that replace the UA workflows SEO teams use most, explains what has genuinely changed versus what has merely been renamed, and flags the measurement pitfalls that produce misleading data if missed.
The Landing Page report and why it behaves differently from UA
In Universal Analytics, the Landing Pages report under Behaviour > Site Content showed sessions by entry page, segmented by traffic source through a secondary dimension. In GA4, the equivalent is Reports > Engagement > Landing page. The fundamental difference: GA4's Landing page report shows sessions, not users, by default, and its session attribution model means a user who enters through organic search, leaves, and returns directly within 30 minutes may have their second session attributed to direct rather than organic, where UA would have attributed both to the organic campaign if the same session window was active.
The immediate implication for SEO reporting: the GA4 Landing page report will typically show fewer organic sessions for the same traffic volume than UA did, not because organic traffic has declined but because the attribution model constructs sessions differently. The correct approach is to use the first_visit event (which fires on a user's first session ever) filtered by session_source = google and session_medium = organic as a supplementary metric for evaluating new organic user acquisition, rather than relying on session counts alone for year-on-year comparison.
To access the Landing page report with the organic filter applied: Reports > Engagement > Landing page > Add filter > Session medium exactly matches organic. Save this filter as a comparison for persistent access. This report path provides the closest GA4 equivalent to the UA organic landing page session data, but it is not identical; document the methodology change in any report that compares GA4 and UA periods.
Fun fact: Universal Analytics was sunset on 1 July 2023 for standard properties, though some paid GA360 customers had access through July 2024; Google Analytics 4 was officially introduced in October 2020, giving organisations nearly three years to migrate before UA historical data stopped updating.
Free-form Explorations: the replacement for UA Custom Reports
The report that SEO teams miss most from Universal Analytics is the Custom Report: a configurable interface that allowed any dimension and metric combination to be saved and revisited. GA4's equivalent is the Explore section, specifically the Free-form exploration. Navigate to Explore > Blank > Free-form. The interface provides a canvas where dimensions and metrics are dragged from the Variables panel into Rows and Values. The key dimensions for SEO work: Page path and screen class (the equivalent of UA's Page), Landing page, Session default channel group (replaces UA's Channel), Event name, and Country.
The metrics to add for standard SEO reporting: Sessions, Engaged sessions, Engagement rate, Average session duration, Conversions (select the specific conversion event relevant to the site), and Total revenue if applicable. Engaged sessions is the GA4 metric that most closely replaces UA's Bounce rate in inverse form: an engaged session is one lasting longer than 10 seconds, containing a conversion event, or containing 2 or more page views. The GA4 Engagement rate is the percentage of sessions that were engaged; the Bounce rate in GA4 (under Reports) is the inverse of this, showing the percentage of sessions that were not engaged.
For organic search specifically, build a Free-form exploration with Landing page as the row dimension, Sessions and Conversions as values, filtered to Session medium = organic. Sort by Sessions descending. This produces the direct replacement for the UA organic landing page performance report with conversion data attached. Save the exploration; Explorations persist in the Explore section and can be shared with other users on the property.
The Search Console integration and its limitations
GA4 connects to Google Search Console through the product links section: Admin > Property settings > Product links > Search Console links. Once linked, Search Console data appears under Reports > Acquisition > Search Console. The integration provides query-level data (top queries by clicks and impressions), landing page data with GSC metrics, country and device breakdowns, and weekly charts. This integration resolves the keyword (not provided) problem by bringing GSC impression and click data into the GA4 interface, though it is important to understand what it does not provide: GSC data in GA4 reflects Search Console's 16-month data retention limit, not GA4's data retention settings, and the two datasets measure different things — GSC counts impressions and clicks in search results; GA4 counts sessions and events on the site.
The query where GSC and GA4 data diverge most significantly: branded queries. A branded query that generates a GSC click may produce a session classified under the Direct channel in GA4 if the user had a previous direct session and the attribution model assigns the return visit to direct. Cross-referencing the GSC landing page click data with the GA4 organic landing page session data surfaces these discrepancies and is the most reliable way to identify where GA4 is under-crediting organic search for the traffic it generated.
Setting up conversion events that SEO teams can actually use
GA4's default conversion events — first_visit, session_start, purchase — are minimally useful for SEO measurement without augmentation. The most valuable conversion events for SEO reporting are form_submit (for lead generation sites), scroll depth milestones at 50% and 90% (as an engagement proxy for content sites), and file_download for research or resource-heavy pages. These can all be configured without additional code on WordPress sites using Google Tag Manager with built-in trigger types: Form Submission, Scroll Depth, and Click triggers, respectively.
Once configured, mark these events as conversions under Admin > Data display > Conversions. The SEO workflow change: in Free-form Explorations, add the specific conversion event as a metric column alongside organic sessions from the landing page. This shows which organic landing pages are not only generating traffic but converting it — the metric that connects SEO investment to business outcomes rather than just reporting session volume. A page at position 8 with a 4.2% conversion rate on organic sessions warrants investment in moving it to position 3 in a way that a page at position 3 with a 0.4% conversion rate does not, and GA4 is the only place to see that combined picture.
Open Explore, build the Free-form report, and stop comparing to Universal Analytics
The most persistent GA4 measurement problem for SEO teams is the instinct to find the UA equivalent for every metric rather than accepting that some UA metrics have been replaced by better constructs. Bounce rate was not a reliable engagement signal; Engagement rate is a more meaningful proxy. Session-based attribution creates last-click distortions that event-based attribution reduces. The year-on-year comparison problem is real and unavoidable for the 2022 to 2023 transition period, but it is not a reason to persist with workarounds that reintroduce UA's measurement limitations into GA4.
Start with the Landing page exploration filtered to the organic medium. Add Engaged sessions and your primary conversion event as columns. Sort by Engaged sessions descending. The pages at the top of this list are generating organic traffic that is meaningfully engaging with the site. The pages that rank high by session volume but low by engagement rate are the ones where the search intent match is weakest — and where a content review or title refinement is more likely to produce business value than a ranking improvement. In GA4, 30 days from today, you will have 30 days of cleaner data than you have ever had on those pages in Universal Analytics.