Organic search traffic in GA4: where it is and how to read it

You want the organic traffic number, the pages that earn it, and whether those visits sign up. This page shows where that lives in GA4, how to read it, and how to join it with Search Console when you need the queries.

By , founder of Porteur · Updated 14 September 2026 · Markdown

Where organic search sits in GA4

Organic search visits sit in the default channel group Organic Search. GA4 assigns that from the session source and medium, like google or bing with medium organic.

  1. Open the Traffic acquisition report

    Reports, Acquisition, Traffic acquisition. Set the primary dimension to Session default channel group if it is not already.

  2. Filter to Organic Search

    Click the Organic Search row. This filters all metrics on the report to organic sessions only.

  3. Read the trend and totals

    Use the chart for trend and the table for Sessions, Users, Engaged sessions, and Key events.

If Organic Search looks low but Direct is high, check attribution and consent later in this guide. A device that blocks referrers or cookies will push sessions into Direct or lose them.

Source and medium: when the channel is not enough

Channel group is a roll‑up. Source and medium tell you the exact referrer and type. Google and Bing both live in Organic Search, but you often need to separate them.

  1. Switch the primary dimension

    On Traffic acquisition, change the primary dimension to Session source / medium. You will see google / organic, bing / organic, and others.

  2. Add a secondary dimension if needed

    Use the plus icon to add Landing page as a secondary dimension. Now each row shows source / medium broken down by the first page of the session.

  3. Save a filtered view

    Click the table filter and include only mediums that equal organic. Save this view to the report if you want it next month.

Example: if google / organic brings most sessions to "/pricing" but bing / organic lands on "/guides/getting-started", your title and snippets differ by engine. Fix the page that misses its intent for that engine.

Landing page report: sessions and key events by first page

You make decisions on pages. GA4’s Landing page report shows the first page of the session, the sessions it started, and the key events on those sessions.

  1. Open the Landing page report

    Reports, Engagement, Landing page. Set the date range, for example Last 28 days.

  2. Filter to Organic Search only

    Use Add filter, include Session default channel group equals Organic Search. Apply.

  3. Add the metrics you need

    Edit comparisons or customise the report to show Sessions, Users, Views, Key events, Key events per session, and Average engagement time.

  4. Read the top rows

    Scan the top landing pages. Which paths like "/" or "/pricing" start sessions, and which drive key events. Sort by Key events to surface sleepers.

Fixed, this page reads like: "/guides/getting-started" starts fewer sessions than "/blog/what-is-x", but its key events per session is higher. You know where to add internal links and where to improve copy.

Key events and attribution in GA4, in plain words

Conversions were renamed key events in 2024. Any event you mark as a key event counts here, such as signup, trial_start or purchase. Mark only the events that mean progress for the business, not a pageview.

  1. Mark your product events as key events

    Admin, Data display, Events. Toggle the key event switch for signup, checkout_complete, or your named goals.

  2. Check attribution model impact

    GA4 uses data‑driven attribution for key events. Add a comparison in reports for First click and Last click to see how Organic Search changes.

  3. Keep the action on landing pages

    If Organic Search under data‑driven looks low but First click raises it, your content brings people who convert later. Keep investing in the landings that start those journeys.

First touch credits the visit that brought the person. Last touch credits the visit right before the conversion. For a product site, the useful question is which landing pages bring people who later sign up. That is why you filter the Landing page report to Organic Search and read key events by path.

Build a one screen monthly view you can reuse

Stop scrolling 20 columns. Make a compact view you check each month, and save it. Keep it to one screen. You need landings, sessions, key events, and the source group.

  1. Create a Landing page detail view

    Open Reports, Engagement, Landing page. Click Customise. Keep these metrics: Sessions, Users, Key events, Key events per session, Avg engagement time.

  2. Add channel group and source/medium

    Add a secondary dimension toggle that can switch between Session default channel group and Session source / medium.

  3. Fix the date to months

    Use a monthly date range in comparisons. For example, set Last 28 days and compare to the previous period, so both fit one chart without scrolling.

  4. Pin it to your Reports snapshot

    Save the custom report and add it as a card to your Reports snapshot. Now your monthly check is one click.

Your finished view shows a table like: Landing page path, Sessions, Key events, Key events per session. A filter at the top holds Organic Search. You can scan "/", "/pricing", "/blog/x" on one screen and decide edits without hunting menus.

Why impressions rise without clicks, and why numbers differ

Search Console and GA4 do not reconcile exactly. A click can start no session. A session can follow several clicks. Consent tools drop some sessions. Small segments can be thresholded. Large explorations can be sampled. Expect direction, not a match.

  • Search Console counts Google impressions and clicks. No other engines. GA4 counts sessions after the click, from any engine.
  • Cookie consent in the EU removes some sessions. Any rate computed on consented sessions undercounts.
  • Query data in Search Console can be anonymised. Rows with few queries roll up into Other. GA4 has no queries at all.
  • Attribution redistributes key events across channels. A data‑driven model credits assists. A first or last click view will shift Organic Search up or down.
  1. Use the Search Console link for context

    Admin, Product links, Search Console. Link the property. GA4 adds two reports: Google organic search queries and Google organic search traffic.

  2. Open the two added reports

    Library, Collections, Search Console. Read the query table for clicks and impressions. Read the landing page table for clicks, impressions, and sessions side by side.

  3. Join insights by landing page

    Spot pages with clicks and no key events. Or pages with key events per session high and no clicks. Fix title and snippet on the first. Add links to and from the second.

Example: "/guides/getting-started" shows high key events per session in GA4. In the Google organic search traffic report it has few clicks. Improve its title and meta description, link it from "/blog/x", and add a call to action above the fold.

UTM parameters: use them outside your site, never inside

UTMs tell analytics where a session came from when you place the link. GA4 reads utm_source, utm_medium, utm_campaign, utm_term, utm_content. They belong on links you put elsewhere, like a newsletter, a social post, or a partner page.

  1. Build clean, consistent UTMs

    Use Google’s Campaign URL Builder. Keep medium values that GA4 groups: email, social, cpc, affiliate. Do not invent new mediums if you want clean channel reports.

  2. Protect against indexed UTM URLs

    A UTM URL that others link to can be indexed. Set the canonical tag on that page to the clean URL.

  3. Check your organic view

    Filter your Landing page report by Organic Search. UTM parameters on external links do not affect organic sessions.

Example: your newsletter links to "yourproduct.com/guides/getting-started?utm_source=newsletter&utm_medium=email&utm_campaign=q4". That classifies as Email, not Organic Search. A blog link you add without UTMs that people click from Google stays Organic Search.

When you need product analytics to answer signups from search

GA4 is strong on sessions and pages. Product analytics answers the person‑level question: which landing pages bring people who later sign up. That needs the first landing page joined to a later product event.

PostHog is an event‑based product analytics tool with a web analytics dashboard. It classifies sessions into channel types, including Organic Search from the referrer and UTMs. A $pageview carries $current_url, $pathname and $referring_domain. A person carries initial referrer and initial UTM properties from their first visit.

  1. Build a funnel from a landing page to signup

    Create a funnel from a pageview on "/pricing" or "/guides/getting-started" to signup. Break it down by the person’s initial referring domain. You will see Google, Bing, and others.

  2. Answer first touch vs last touch

    First touch credits the first visit. Last touch the one before signup. In PostHog you can use the initial referrer to read first touch funnels.

  3. Bring revenue into the picture

    Join the payment event to the person and their first landing page. That report answers what a search click earns. GA4’s page reports alone cannot answer that.

Example: people who first land on "/pricing" from Google have a higher signup rate than those who land on "/blog/compare-x-vs-y". That tells you to improve the call to action on the comparison page and link it to "/pricing" higher up.

Questions

Sources

Check my site, free

Paste your homepage URL to get a free read of your pages, the searches around them and the rivals on them in about thirty seconds, then decide what to fix next with three findings shown whole.

  • Free check, no card
  • Read-only, your own accounts
  • Readable by your agent

Read next