GA4 Landing Page Report: How to Find and Fix Your Worst Performers.

Every session starts somewhere. The landing page report tells you where — and more importantly, it tells you which pages are engaging users and which are driving them away. This report is the fastest way to find conversion optimization wins.

Finding the GA4 Landing Page Report

Navigate to Reports → Engagement → Landing Page. The report isn't visible in all GA4 properties by default — Google quietly re-added it in July 2023 after removing it at the GA4 launch, and properties created during that window often still don't include it in the default navigation. If you don't see it, you'll need to add it to your report library manually, which takes about 60 seconds.

1. Go to Reports → Library (bottom-left of the Reports section).
2. Find the "Life cycle" or "Engagement" collection.
3. Click Edit Collection.
4. Drag the "Landing page" report card into the collection.
5. Click Save, then Publish so the change rolls out to all viewers of the property.

You need Editor role or higher to publish library changes — Viewer or Analyst roles can only edit for themselves.

Key Metrics to Add to the Default Report

The out-of-the-box landing page report only shows sessions, users, and new users. That's not enough to diagnose a page's performance. Click the pencil icon in the top-right to customize the report and add these five metrics — they give you the complete picture of entry-point quality in under a minute.

• Engagement rate — % of sessions lasting 10+ seconds, having a conversion event, or 2+ page views. The GA4 equivalent of UA's inverse bounce rate.
• Bounce rate — % of sessions that were NOT engaged (exactly the inverse of engagement rate).
• Key events (conversions) — Which landing pages actually drive the outcomes you care about?
• Average engagement time — How long do people spend here in seconds?
• Views per session — Do visitors explore further or land-and-leave?

How to Read the Report: The 4-Quadrant Framework

Once you've added the right metrics, the fastest way to extract insight is to mentally plot each landing page onto a 2×2 grid: traffic volume (sessions) on one axis, engagement rate on the other. Every page falls into one of four quadrants, and each quadrant demands a different action. Sort by sessions descending first, then scan engagement rate to place each page.

• High traffic + High engagement: Your stars. Protect these pages. Do not redesign what's already working — document it.
• High traffic + Low engagement: Your biggest opportunity. These pages get eyeballs but lose visitors fast. Prioritize for A/B testing or rewriting.
• Low traffic + High engagement: Hidden gems. These convert well but lack visibility. Improve internal linking, write about them, run ads to them.
• Low traffic + Low engagement: Deprioritize. Either fix fundamental issues (speed, mobile layout, misaligned intent) or remove them from the sitemap.

Segmenting Landing Pages by Traffic Source

A single landing page can perform wildly differently depending on where the traffic came from. Organic visitors arrive with high intent; paid social visitors are cheaper to acquire but less patient; email visitors are already warm. An aggregate bounce rate hides these patterns completely. Add a secondary dimension to break the numbers apart and you'll often find one source dragging the average down.

1. Click the + icon next to the "Landing page" dimension column.
2. Select Traffic source → Session source / medium.
3. The table now shows each page split by source (e.g. google/organic, facebook/cpc).
4. Sort by sessions to find your highest-volume page-source combinations.

Typical diagnostic this unlocks: "Our homepage has a 45% bounce rate" becomes "25% from organic, 70% from paid search — the paid landing experience is the problem, not the page itself."

Combining Landing Page with Path Exploration

The Landing Page report tells you the entry point but stops there. To see where users go after they land — and where the biggest drop-offs happen — pair it with a Path Exploration. Path explorations run against the last 30-60 days of event data depending on your retention setting, and they're the single best way to visualize multi-step user flows inside GA4.

1. Open Explore → Path exploration.
2. Click the "Starting point" dropdown and set it to Event name: page_view.
3. Add a filter for your specific landing page URL or a regex pattern.
4. Expand each node to see which pages users visit next and where they exit.
5. Look for unexpected exit pages — these usually flag broken flows or missing CTAs.

Common Landing Page Problems and How to Fix Them

Most landing page issues fall into four repeating patterns. Recognizing them on sight saves hours of diagnosis — we see these daily across the NiceLookingData audit pipeline, and the fix for each is usually well-defined even when the root cause isn't immediately obvious in the data.

• High bounce, fast exit (< 3s average engagement): Page loads slowly, doesn't match ad copy, or has a confusing above-the-fold experience. Check Core Web Vitals first.
• Good engagement, no conversions: Strong content but weak or missing CTA. Add one clear next step above the fold.
• Mobile bounce much higher than desktop: The page isn't mobile-optimized. Check font sizes (≥16px), button tap targets (≥44×44px), and layout shifts.
• "(not set)" appearing as the landing page: Usually caused by cross-domain tracking gaps or sessions starting with a non-page_view event (e.g. a file_download fired first).