What the Landing Page Report Is
The Landing Page report in GA4 groups your traffic by the first page a visitor saw when a session started — the entry point, not every page they touched. GA4 derives it from the session_start event, pairing that session with the page path where it began, which is why the metrics here are session-first (sessions, engagement rate, key events) rather than pageview-first.
The stakes: this is the report that tells you which pages actually pull people in from search and whether those entry points hold attention or leak visitors. For SEO it's the closest GA4 gets to "how is each of my ranking pages performing as a doorway."
Where to Find It and How It Differs from UA
It lives under Reports → Engagement → Landing page. If you don't see it, an admin can add it from the report library — it isn't always enabled by default in older properties. The dimension is Landing page + query string, so /pricing and /pricing?utm_source=x can appear as separate rows unless you account for that.
Two things trip up anyone coming from Universal Analytics:
| Aspect | Universal Analytics | GA4 |
|---|---|---|
| Core dimension | Landing Page (page path) | Landing page + query string |
| Headline quality metric | Bounce rate | Engagement rate / engaged sessions |
| How the entry is defined | First hit of the session | Page tied to the session_start event |
| Home page representation | Path, e.g. / | Often shows as / or (not set) early in processing |
| Conversion column | Goals | Key events (formerly "conversions") |
| Query string | Usually stripped in views | Included by default in the dimension |
That "(not set)" landing page row is normal, not a bug — it shows up for sessions GA4 hasn't finished processing or where the first page couldn't be attributed. It usually shrinks as data finalizes.
A real example
You rank for "best hiking boots" and the entry point is /guides/hiking-boots. In the Landing page report you filter to organic traffic (Add comparison → Session default channel group = Organic Search), and you see that page pulled 4,200 sessions with a 68% engagement rate but only 0.4% key-event rate. The guide attracts and holds people but sends almost nobody toward a purchase — a clear signal to add stronger internal links or a product callout, which raw sessions alone would never have told you.
How to Read It for SEO
- Open Reports → Engagement → Landing page. If it's missing, ask an admin to publish it from the library.
- Add a comparison for Session default channel group = Organic Search so you're looking at search entries, not all traffic.
- Sort by Sessions to find your workhorse entry pages, then scan the Engagement rate column for the ones that attract but don't hold.
- Add Key events (and, if set, Session key event rate) to see which entry pages actually move toward business outcomes.
- Watch for query-string duplication — if one page is split across many
?utm=rows, use an Exploration with a cleaned page path, or a filter, to consolidate. - Cross-check winners and losers against Search Console to connect entry-page behavior back to the queries and rankings feeding them.
Common Mistakes and How to Fix Them
- Treating it like the old bounce-rate report. GA4 leads with engagement, and engagement rate is roughly the inverse of bounce — but not identical. Fix: judge entry pages on engaged sessions and key events, not a mental bounce model.
- Not filtering to organic. Blended landing-page data mixes email, paid, and direct, hiding your SEO picture. Fix: always apply the organic comparison for SEO analysis.
- Panicking over "(not set)". It's expected during processing and for unattributed entries. Fix: let data finalize and look at the trend, not one day.
- Query-string fragmentation. The same page scattered across UTM variants understates its true totals. Fix: aggregate on a cleaned page path in an Exploration.
- Ignoring the report isn't enabled. Some properties never published it, so the team assumes GA4 lacks it. Fix: add it from the report library once and it stays.
FAQ
What exactly counts as the landing page in GA4?
The page associated with the session's session_start event — the first page the visitor viewed in that session. It's session-scoped, so a user who returns tomorrow and enters on a different page creates a new landing-page row.
Why does my home page show as "(not set)"?
Early in processing, or when GA4 can't attribute the first page, the row reads "(not set)." It typically resolves as data finalizes; a persistent, large "(not set)" can point to tagging or consent issues worth checking.
How is this different from the Pages and screens report?
Pages and screens counts every view of a page regardless of when in the session it happened. The Landing page report only counts a page when it's the entry point of a session, which is why the numbers are lower and session-based.
Where did bounce rate go?
GA4 replaced bounce rate as the headline with engagement rate (the share of engaged sessions). Bounce rate still exists as an add-on metric but is defined differently — it's simply the inverse of engagement rate.
Can I see landing pages for organic search only?
Yes — add a comparison for Session default channel group = Organic Search, or build an Exploration with an Organic session segment. That's the standard move for SEO reporting.
Related Terms
Claude Vincent is a technical SEO consultant focused on crawlability, rendering, and AI-search visibility. He writes the field guides and case studies at SEO ProCheck, with a bias toward the durable, unglamorous work that decides whether search engines and AI answer engines can actually read and cite a site.
About SEO ProCheck
Technical SEO consulting and GEO strategy with 20 years of enterprise experience. Case studies, resources, and tools for search and AI visibility.
Work With Me
Technical SEO audits, GEO strategy, site migrations, and international SEO. Hourly consulting for teams who need hands-on support, not just reports.
Subscribe to our newsletter!
