GA4 Landing Page Report: Find Your Best Entry Points

What the Landing Page Report Actually Tells You

Most site owners spend their time in GA4's traffic reports, trying to figure out where users come from. That's useful, but it only answers half the question. The other half is: where do users land when they arrive? That's what the Landing Page report is for.

A landing page, in GA4's definition, is the first page a user sees in a session. It doesn't have to be a page you designed as a campaign landing page. It could be a blog post, a product page, your homepage, or a random category page that happened to rank. GA4 tracks whichever URL initiated each session.

That distinction matters. When you look at page views or engagement in GA4's Pages and Screens report, you're seeing aggregate activity across an entire session. The Landing Page report strips that down to first impressions only. It answers: of all the users who entered through this page, how many stuck around, converted, or came back?

Where to Find It in GA4

The Landing Page report lives under Reports > Engagement > Landing Page. If you've never opened it, you might find the default view underwhelming. It shows a table with landing page URLs, sessions, engaged sessions, engagement rate, average engagement time per session, conversions, and total revenue (for e-commerce setups).

The default date range is the last 28 days, which is a reasonable starting point. But the real work starts when you apply comparisons and secondary dimensions.

One thing to watch: GA4 sometimes strips query parameters from landing page URLs in this report, depending on your configuration. If your site uses URL parameters to distinguish campaign variants or filter states, you may need to clean up those URLs in your GA4 property settings or use custom dimensions to preserve the detail you need.

The Six Metrics That Actually Matter

GA4's Landing Page report surfaces a lot of numbers. Not all of them are equally useful. These six deserve your attention.

Sessions

This is the raw count of sessions that started on each page. High session counts tell you which pages are doing the most work as entry points, whether from search, social, referral, or direct. Sort by this column first to see your top performers by volume.

Engaged Sessions

GA4 defines an engaged session as one that lasted longer than 10 seconds, had a conversion event, or had two or more page views. This metric separates pages that attract real interest from pages that attract accidental or low-intent visits. A landing page with 10,000 sessions and 1,500 engaged sessions has a serious problem. A page with 500 sessions and 420 engaged sessions is doing something right.

Engagement Rate

This is simply engaged sessions divided by total sessions, expressed as a percentage. It replaced bounce rate as GA4's primary single-metric signal for session quality. A landing page with a low engagement rate is either attracting the wrong traffic, failing to match user expectations, or loading too slowly to hold attention. For context, most content sites see engagement rates between 50-70% on well-optimized pages. E-commerce landing pages often run 40-60%.

If you want a deeper look at how this metric compares to the old bounce rate, the article on GA4 engagement rate vs bounce rate covers the full picture.

Average Engagement Time per Session

This tells you how long users who came through each landing page actually spent engaged with your content. Longer is generally better, though what counts as "good" depends entirely on content type. A pricing page should convert quickly and have relatively short engagement time. A guide or tutorial should hold attention for several minutes.

Conversions

This column only populates if you've set up conversion events in GA4. If it's empty, that's a separate problem to fix first. When it does show data, it reveals which landing pages are actually driving business outcomes, not just traffic. A page with moderate traffic but high conversions is worth more investment than a traffic magnet that never converts.

Revenue (E-commerce Only)

For stores with GA4 e-commerce tracking enabled, this column attributes revenue to the landing page where each session started. It's the most direct measure of landing page commercial value. A product category page that sends 3,000 sessions and generates $45,000 in attributed revenue is doing very different work than a blog post that sends 8,000 sessions and generates $600.

How to Add a Traffic Source Dimension

The Landing Page report on its own doesn't tell you how users arrived at each page. Adding a secondary dimension for traffic source turns the report from interesting to actionable.

Click the + button next to the primary dimension dropdown and add Session default channel group. Now each landing page row expands to show performance broken down by Organic Search, Direct, Referral, Paid Search, Organic Social, and other channels.

This is where you start finding real discrepancies. A page might show an overall engagement rate of 55%, but when you break it down, organic search visitors engage at 70% while paid search visitors engage at 30%. That's a signal that your ad targeting is attracting the wrong audience, or that the page content doesn't match the ad message.

For a broader view of how acquisition channels perform across your site, the GA4 acquisition reports guide covers every dimension in detail.

Comparing Date Ranges to Spot Decay

Landing page performance changes over time, and not always visibly. A page that drove strong engagement six months ago might be quietly losing ground today due to increased competition, content staleness, or a shift in search intent.

Use GA4's date comparison feature, found in the top-right date picker, to compare the current period against the same period last year (or any custom range). Sort by sessions and look for pages where sessions have dropped while engagement rate has held steady. That's a traffic problem, likely a rankings issue. Pages where both sessions and engagement have dropped together signal a relevance problem.

Pages showing declining sessions are worth investigating through Google Search Console to confirm whether impressions and clicks have also dropped. The combination of both tools gives you a much more complete picture than either one alone. The article on connecting GSC to GA4 explains how to link them and use the joint data.

Content decay is often silent until it becomes severe. Running this comparison quarterly catches problems early enough to fix them. If you want a systematic process for this, the content decay guide walks through the full diagnostic workflow.

Using the Landing Page Report to Audit Conversion Paths

Most conversion analysis in GA4 focuses on the final steps before a purchase or signup. The Landing Page report lets you move the analysis upstream. Instead of asking "where did users abandon the funnel?" you can ask "which entry points produce users who even reach the funnel?"

Filter your landing page report to show only pages with sessions above a meaningful threshold, say 200 sessions per month, to remove noise. Then sort by conversions descending. You'll typically find that a small number of pages, often 10-20% of your total landing pages, drive the majority of conversions.

That concentration is useful in two ways. First, it tells you which pages to protect and invest in. Second, it gives you a model for what a high-converting landing page looks like on your site, in terms of content depth, topic focus, call-to-action placement, and traffic source mix.

For sites with complex funnels, pairing this analysis with GA4's Funnel Exploration tool adds another layer. You can see not just which pages get the session, but which ones produce users who make it all the way through. The funnel exploration guide explains how to set that up.

Segmenting by Device Type

Another secondary dimension worth adding is Device category. Mobile and desktop users often behave very differently on the same landing page, and the differences aren't always where you'd expect.

A common pattern: a blog post or content page shows high engagement on desktop but low engagement on mobile. This points to a mobile experience problem. It might be slow load time on mobile connections, hard-to-read formatting on small screens, or intrusive interstitials that trigger before users can engage with the content.

When you find a page with a large gap between mobile and desktop engagement rates, cross-check it against your Core Web Vitals data. Poor Interaction to Next Paint or Largest Contentful Paint scores on mobile are often the direct cause. Fixing those issues tends to lift both engagement rate and search rankings simultaneously, since Google evaluates mobile performance as part of its ranking signals.

Setting Up a Custom Exploration for Deeper Analysis

The standard Landing Page report in GA4 is helpful but limited. For deeper analysis, GA4's Explore module lets you build a custom free-form exploration that combines landing page data with almost any other dimension or metric in your property.

A useful setup: create a free-form exploration with Landing page + query string as your row dimension, then add columns for sessions, engaged sessions, engagement rate, event count, and conversions. Apply a filter for organic search traffic only. This gives you a clean view of how your SEO landing pages perform, which is difficult to build in the standard reports.

You can also use this exploration to compare specific page groups. Use a filter that matches pages containing a URL path segment, like "/blog/" or "/products/", to isolate content type performance. Blog posts often drive high engagement but low direct conversions. Product pages might show lower engagement but higher revenue per session. Knowing which pattern applies to which page type helps you set realistic targets and interpret anomalies correctly.

GA4's full exploration suite covers far more analysis types than most analysts use. The GA4 exploration reports guide covers each type with practical examples.

Common Mistakes in Landing Page Analysis

A few patterns come up repeatedly when analysts work with this report for the first time.

The first is treating all low-engagement pages as problems. Some pages are meant to convert quickly and send users somewhere else. A contact page that shows low engagement time and few pageviews per session is working exactly as it should if users are filling out the form. Always interpret engagement metrics in the context of page intent.

The second mistake is ignoring the landing page + query string dimension option. By default, GA4 groups landing page variants that differ only in their query string together, which can obscure important differences. An A/B test variant, a UTM-tagged campaign page, or a filtered search result page will all look identical in the default view. Switching to the query string variant exposes these differences.

Third, analysts often look at landing page performance without connecting it to conversion outcomes. High engagement on a page that never converts is a signal to investigate, not celebrate. The CRO and SEO connection article covers how to tie these two disciplines together systematically.

Turning Landing Page Data Into Action

The Landing Page report is most useful when you treat it as a prioritization tool. Every page on your site competes for your attention, and this report tells you where to spend it.

High-traffic pages with low engagement rates get your first attention because they represent wasted opportunity at scale. Even a small improvement in engagement rate on a page with 5,000 monthly sessions produces meaningful downstream effects on conversions and revenue.

Pages with strong engagement but low traffic are your second priority. They've proven they work when people land on them. The constraint is discovery, not quality. These pages benefit most from SEO investment, internal linking, and promotion.

Pages with low traffic and low engagement are candidates for the content pruning or consolidation conversation. If a page hasn't attracted meaningful traffic in 12 months and doesn't engage the visitors it does get, it may be dragging down your overall site quality signals without offering any compensating benefit.

Running through this analysis every quarter, rather than reactively when something breaks, keeps your landing page mix healthy. It's one of those reports that rewards consistency more than intensity.