How to Track Organic Traffic by Landing Page in GA4

Last updated: October 10, 2026

Quick answer: In GA4, you can track organic traffic by landing page by building a free-form Explore report with Landing page + query string as the row dimension and an Organic Search filter; most sites should review it over 28 to 90 days for steadier SEO decisions. If you want to know which pages actually bring in unpaid search visits in GA4, this report shows the first page of the session, not just the pages people visited later. This article explains how to track organic traffic by landing page in GA4, what to use, and how to read the results.

What “organic traffic by landing page” means in GA4

Organic traffic by landing page means the first page a user enters on during a session, limited to sessions that came from unpaid search. In GA4 terms, that is usually the landing page plus query string dimension, paired with the Session default channel group or Session medium dimension.

That distinction matters because a page can receive a lot of organic entrances without being the page that gets the most total pageviews. A blog post might be the landing page for a few hundred organic sessions in a month, then those users click to six other pages. The landing page is still the entry point. If you only look at Page path or Page title, you miss that difference.

GA4 also behaves differently from Universal Analytics in one key way: landing page reporting is not as central or as visible by default. You usually have to build the view yourself in Explore or a custom report. That is annoying, but it gives you more control over filters, segments, and comparisons.

I would use this report when I need to answer one of three questions: which content attracts organic visits, which landing pages convert, and which pages bring search traffic that never goes anywhere else. It is the wrong report if you only want total pageviews or if your organic traffic is so small that the data gets noisy. A page with 8 organic sessions is not a decision-making sample.

Which GA4 dimensions should you use?

The cleanest setup uses Landing page + query string and Session default channel group. That combination shows the page people entered on and whether the session was organic search.

If you want more control, add Session source / medium. That lets you separate google / organic from bing / organic or other search sources. If you run a broad SEO program, that distinction can help explain why one landing page performs well in one engine and not another.

A few dimensions sound similar but answer different questions:

• Landing page + query string: the landing page for the session.
• Page path and screen class: every page viewed, not necessarily the landing page.
• Session default channel group: the session’s traffic bucket, such as Organic Search.
• Session source / medium: the source and medium together, such as google / organic.
• First user default channel group: where the user first came from historically, which is not the same as the current session.

The most common mistake is using Page path and screen class, then assuming the report shows landing pages. It does not. Another mistake is using First user source / medium when the real question is about current organic sessions. That will blur paid, direct, and returning behavior across multiple visits.

If your site uses query strings heavily, keep the query string version of the landing page only if you really need it. Otherwise, the same page can split into many rows because of tracking parameters. For clean SEO reporting, I usually prefer the version without query strings unless those parameters change content in a meaningful way.

How do I build the report in GA4?

A practical way to start is to use Explore and create a free-form table with landing page as the row dimension and an organic filter applied to sessions.

Here is the basic setup in GA4:

1. Open Explore.
2. Start a Free form exploration.
3. Add Landing page + query string to Rows.
4. Add metrics such as Sessions, Engaged sessions, Conversions, and Total revenue if relevant.
5. Add a filter for Session default channel group = Organic Search.
6. Sort by Sessions or Conversions, depending on the question.

If you want to compare organic landing pages against all traffic, create a segment for Organic Search rather than filtering the whole exploration. That way you can place organic and all sessions side by side. A segment is better when you want context. A hard filter is better when you want a pure organic list.

For a simple report in the standard interface, I would also check Reports > Engagement > Landing page if your property has that report available. In some GA4 setups, it is easier to use an exploration because the default reports are too rigid.

A useful setup is to add a comparison for Organic Search, then view landing pages sorted by sessions and conversions. That gives you more than traffic volume. A landing page with 1,000 organic sessions and 0 conversions may be less valuable than one with 120 sessions and 18 conversions.

What if your organic data looks wrong?

Your organic landing-page report looks wrong when the channel grouping, tags, or consent setup are muddying the session source. The fix is usually in attribution hygiene, not in the landing page dimension itself.

The first thing I check is whether paid campaigns are missing UTMs. If someone runs ads without proper tagging, GA4 may misclassify visits and they can land in organic, referral, or direct. That pollutes the report before it starts.

The second check is cross-domain tracking. If your site sends users across multiple domains and the setup is incomplete, landing pages can fragment or sessions can restart. The result is a report that shows odd landing pages or inflated direct traffic. For sites with checkout domains, booking engines, or subdomains, this can matter quickly.

The third issue is consent mode and tagging gaps. If data collection is inconsistent, session counts can shift between browsers, regions, or devices. I would not treat tiny changes in organic landing-page rankings as meaningful until the tracking stack is stable; if the result could affect a major SEO decision, consult a qualified analytics or SEO professional and verify the setup against Google’s documentation. See Google Analytics support on cross-domain measurement and attribution and channel grouping.

A fourth issue is self-referrals. If your own domains appear as referrals, the session source can get reassigned away from organic. That can hide the landing pages you actually care about.

When the report looks off, I would check these in order: channel tagging, cross-domain setup, referral exclusions, and then the landing-page report itself. Fix the plumbing first. Otherwise you can spend an hour optimizing a page that is not really losing traffic at all.

The mistake that costs the most data

The biggest mistake is confusing landing pages with all pages and then making SEO decisions from the wrong metric. That error can turn a high-performing landing page into a false underperformer in a single dashboard.

Here is the problem. Suppose a page gets 500 organic entrances in a month. If users then click to two or three deeper pages, the original page may not look like the top performer in a generic page report. A pageview report might put a different URL on top because it gets repeated views from the same sessions. That is not the same thing as acquisition.

Another common mistake is ignoring query strings. A blog post may appear under five different rows because of UTM pollution, search parameters, or print versions. If you sort the report naïvely, the page gets split into pieces and the numbers look smaller than they are.

The cost is usually strategic. Teams prune pages that are actually doing acquisition work. Or they keep pages that attract traffic but do nothing after the click. Both mistakes come from reading the wrong row in GA4.

This is also where I would be cautious about making hard decisions from short time windows. A week of data can be enough to spot a broken page, but it is usually too short to judge seasonal organic performance. For SEO, 28 to 90 days is a more defensible window than 3 or 4 days. For broader business decisions, the safer approach is to review the data alongside rankings, revenue, and site changes before acting.

How should you read the report once it is built?

You should read it as a path-to-entry report, not as a full content ranking report. The landing page tells you which pages start organic sessions; it does not tell you why Google ranked them or whether the visitor was satisfied.

A practical way to read it is to line up four columns: Sessions, Engaged sessions, Conversions, and Revenue if you have ecommerce. Then ask which landing pages bring the most traffic, which landing pages bring the best quality traffic, and which pages bring the most business value.

A page with high sessions and low engagement may still be useful if it brings branded search or top-of-funnel discovery. A page with modest sessions and strong conversions may deserve more internal links, better titles, or a stronger call to action. The report does not tell you what to change, but it does tell you where to look.

I would not make the mistake of optimizing only the highest-traffic pages. Sometimes the highest-value SEO gains sit on the second tier: pages with enough volume to matter and enough weakness to improve. That is where title tag rewrites, content expansion, or internal linking often pay off.

If you need to present this to a client or stakeholder, pair the report with a date range and one comparison period, such as last 28 days versus the previous 28 days. That keeps the conversation grounded in change, not in a single snapshot. Without that, people tend to overreact to one noisy week.

Landing page report template I would use

I would use a simple template with one row per landing page and five columns: Landing page, Organic sessions, Engaged sessions, Conversions, and Revenue. That is enough to answer most SEO questions without burying the reader in metrics.

That template is deliberately plain. I would rather have a report that answers one question cleanly than a dashboard with 17 metrics and no decision attached. If you are reporting to non-technical stakeholders, keep the page title visible and avoid extra dimensions until the core view is stable.

One more useful refinement is to compare organic landing pages against paid or referral landing pages using the same table. That shows whether a page is naturally strong or only performing because of a traffic source mismatch.

FAQ

Can I see organic traffic by landing page in GA4 without Explore?

Yes, but Explore is usually the cleanest way to do it. Some GA4 properties include a landing-page report in the standard reports area, and you can sometimes use comparisons or filters there. Explore gives you more control over the session-level organic filter.

What is the difference between landing page and page path in GA4?

Landing page is the first page in the session. Page path is any page the user viewed. If you want organic entry pages, use landing page.

Should I include query strings in the landing page dimension?

Only if those query strings change meaning or content. For most SEO reporting, query strings create noise and split one page into many rows.

Why does my organic traffic not match Search Console?

Because GA4 and Search Console measure different things. Search Console reports search performance in Google results. GA4 reports on-site sessions after the click. The numbers should not be expected to match exactly.

How far back should I look?

For most sites, 28 to 90 days is a practical window. Shorter windows can help spot issues, but they are usually too small for stable SEO decisions.

Key takeaways

• Use Landing page + query string with an Organic Search filter to see which pages start unpaid search sessions.
• Do not confuse landing pages with all pages viewed; they answer different questions.
• If the report looks wrong, check UTMs, cross-domain tracking, and self-referrals before you blame the content.
• Read the report by traffic, engagement, and conversions, not just sessions.
• Keep the view simple enough that it can guide one decision, not a dozen half-decisions.

Drafted with AI; not yet reviewed by a person.