GA4 for SEO: measuring organic traffic, landing pages and key events

What GA4 and Search Console each measure

The two tools look at different halves of the same journey. Search Console counts what users did on Google: whether your page appeared, whether someone clicked it and where it ranked. Google defines a click there as “How often someone clicked a link from Google to your site.” It knows nothing about what happened next.

GA4 starts where Search Console stops. A tag on your pages sends events, GA4 groups them into sessions and users, and it tells you which pages people landed on, whether they engaged and whether they did something valuable, such as sending a form or buying. It knows that a visit came from organic search, but it does not know the query for most visits.

That is why an SEO needs both. Search Console tells you whether you are visible and attractive in results. GA4 tells you whether that traffic is worth having. Setting up Search Console itself is covered in the lesson Setting up Search Console, and reading its own data in the lesson on the Performance report.

What Google officially says

How GA4 decides a visit is Organic Search

GA4 reads the source and medium of each session, which come from the referrer or from UTM parameters, and runs them through fixed channel rules. The Organic Search rule has two parts joined by OR. Google writes it as: “Source matches a list of search sites listed under "SOURCE_CATEGORY_SEARCH"” OR “Medium exactly matches organic”.

In practice this means three things. First, Organic Search is not only Google: Bing, DuckDuckGo, Yahoo, Yandex, Baidu, Ecosia and the other engines on Google's list land in the same channel. Second, clicks from Google's AI Overviews and AI Mode are counted here too, not in a separate AI channel. Third, anything you tag with utm_medium=organic becomes Organic Search, even if it is not search at all, so keep that medium for real search traffic.

Three channel dimensions, three questions

The same channels appear in three dimensions, and picking the wrong one is the most common reporting error:

• Session default channel group: “The channels by which users arrived at your site/app when they initiated new sessions”. Use this for SEO traffic reports. It tells you how many sessions organic search brought.
• First user default channel group: “The channels by which users first arrived at your site/app”. Use it to see how many new users organic search acquired.
• Default channel group: “The channels by which users arrived at your site/app and triggered a key event.” It uses the property's attribution model, data-driven by default, and is the view for crediting key events across channels.

Session attribution has one more twist. GA4 uses a non-direct last click model for sessions, and Google gives this example: “Day 68: The user comes back to the website directly => session is also attributed to “google / organic”.” Returning visitors who type your URL can still count as organic, within the lookback window. This is one reason GA4 can show organic sessions on days when Search Console shows fewer clicks.

Sessions, users and engaged sessions

GA4 has several counts that sound alike. Know exactly what each one means before you put it in a report.

• Session. “A session is a period during which a user is engaged with your website or app.” Google adds: “By default, a session ends or times out after 30 minutes of user inactivity.”
• Total users and Active users. Total users counts everyone who triggered any event. Active users counts people who engaged; Google defines them as “the number of people who engaged with your site or app in the specified date range.” Most GA4 reports show active users under the label “Users”.
• Engaged session. “The number of sessions that lasted 10 seconds or longer, or had 1 or more key events or 2 or more page or screen views.”
• Engagement rate and bounce rate. “Engagement rate = engaged sessions / total sessions”, and “The bounce rate is the percentage of sessions that were not engaged.” The two always add up to 100%.
• Average engagement time. The time your page was in focus in the browser, averaged per active user.

For SEO, report sessions as the traffic number and engaged sessions or engagement rate as the quality number. Users are useful for audience questions, but one person can arrive from search several times, so users and sessions answer different questions. Always say which one a chart shows. Also keep in mind that Google states “Session and User metrics are calculated through an estimation”, so small differences between reports and BigQuery exports are normal.

Landing pages from organic search

The landing page is where SEO meets GA4: it is the page that ranked and got the click. GA4's Landing page + query string dimension is “The page path and query string associated with the first pageview in a session.”

There are two quick ways to see organic landing pages in standard reports:

1. Engagement › Landing page, then add a comparison where Session default channel group exactly matches Organic Search. You get sessions, users, engagement and key events per landing page, organic beside all traffic.
2. Acquisition › Traffic acquisition, filter or compare on Organic Search, then add Landing page + query string as a secondary dimension.

What to look for, in practice:

• Pages with many organic sessions and a low engagement rate. The page ranks but may not answer the query. Compare its queries in Search Console with what the page actually offers.
• Pages with high engagement but few key events. The content works, the path to the next step does not: missing calls to action, weak internal links.
• The same page by device. A page that engages on desktop and not on mobile usually has a layout or speed problem on phones.
• Query-string variants. /shoes/?utm_source=newsletter and /shoes/ appear as separate rows. Use the Landing page dimension without the query string when you want them combined.
• (not set) landing pages. In practice these are sessions whose first event was not a page view, for example a session that timed out and restarted with a scroll or click event. A large share points to tagging problems.

Key events: measuring SEO conversions

Key events are what GA4 used to call conversions. Any event can be one: you mark it in Admin › Data display › Events by clicking the star next to it, or create a new event and switch on Mark as key event. Google sets a limit: “You can mark up to 30 events as key events for standard properties and 50 events as key events for Analytics 360 properties.” On websites, purchase is marked as a key event by default.

Choose key events that show the business value of organic traffic:

• generate_lead or a form-submit event for lead-generation sites;
• purchase for shops, ideally with revenue;
• sign_up for products and communities;
• clicks on phone numbers and email addresses for local businesses;
• file_download for sites whose goal is a brochure or price list (collected by enhanced measurement when it is enabled).

Keep the list short. If scrolls and every click are key events, every session looks like a success and the number stops meaning anything. Also plan ahead: “Marking an event as a key event affects reports from time of creation. It doesn't change historic data.” Google says to “allow for up to 24 hours for it to show up in standard reports”. Mark key events when you set up the property, not on the day someone asks for a report.

Connecting Search Console to GA4

Linking brings Search Console's clicks, impressions, CTR and position into GA4. You need two permissions: “To create a link, you need the Editor role on the Google Analytics property, and you need to be a verified owner of the Search Console property.”

1. In GA4, go to Admin › Product links › Search Console links and click Link.
2. Choose the Search Console property you own, then the web data stream for the same site.
3. Review and submit. “You can't edit Search Console links.” To change one, delete it and create a new one.
4. Open Reports › Library and publish the Search Console collection: “The Search Console collection of reports is unpublished by default.”

The two Search Console reports in GA4

• Queries (Google Organic Search Queries): “Displays search queries and associated Search Console metrics for the linked Search Console property.” Note the limit: “You can drill deeper into the data by Search Console dimensions (but not by Analytics dimensions).”
• Google organic search traffic: “Displays landing pages with associated Search Console and Analytics metrics.” This is the useful one: clicks, impressions, CTR and position next to active users, engaged sessions, engagement rate and key events for each landing page, split by country or device.

Their limits

• “Search Console metrics are only compatible with Search Console dimensions and the following Analytics dimensions:” landing page, device and country. You cannot combine queries with key events, for example.
• “Search Console keeps data for the last 16 months. As a result, reports in Analytics also include a maximum of 16 months of data.”
• “Search Console data is available in Search Console and in Analytics 48 hours after it is collected by Search Console.”
• “The Search Console reports currently do not support time-series charts.” For trends, use Search Console itself.
• “You can link a web data stream to only one Search Console property.” If your site has several Search Console properties, link the one that covers the whole site, usually a Domain property.
• Data does not go back forever. Google: “If you create the web data stream and then complete site verification, data is available from the time of site verification.”

Google also asks you to “Be sure that your Google Analytics property and your Search Console property are collecting data for the same set of web pages.” A GA4 stream on https://www.example.com linked to a Search Console property for blog.example.com only gives you a partial picture.

Why GA4 and Search Console numbers never match

Expect Google organic sessions in GA4 and clicks in Search Console to differ, and expect the gap to vary between sites and pages. These are the usual reasons.

A click is not a session

A click becomes a GA4 session only if the page loads, the Google tag runs and sends data. People who go back before the tag fires, ad blockers, JavaScript errors and pages without the tag all produce clicks with no session. In the other direction, one person can click twice within 30 minutes and produce one session.

Google vs every search engine

GA4's Organic Search channel includes Bing, DuckDuckGo and the others; Search Console is Google only. To compare like with like, filter GA4 to Session source / medium = google / organic.

Consent

Google's own wording: “When visitors deny consent, instead of storing cookies, tags send pings to Google. If you are using Google Analytics, Google fills the data collection gaps with conversion modeling and behavioral modeling.” Modelling needs the advanced setup, where you “Load Google tags in all cases, not only if the user consents.” Google warns that “If you choose to implement consent mode by blocking Google tags until the consent dialog appears and users consent, you will not get the full benefits of consent mode.” Behavioral modelling also has volume thresholds, for example “The property collects at least 1,000 events per day with analytics_storage='denied' for at least 7 days.” Smaller sites often never qualify, so their GA4 numbers stay lower in regions with consent banners.

When modelling is on, numbers shift again: “When Analytics includes modeled data, you will probably see differences when compared to reports that include only observed data”.

Bots

“In Google Analytics properties, traffic from known bots and spiders is automatically excluded.” Search Console counts clicks on Google’s side and does not use GA4’s bot list, so the two tools will not exclude exactly the same visits.

Attribution

Search Console counts the click itself. GA4 attributes sessions with non-direct last click, so a later direct visit can still be credited to google / organic, as in Google's Day 68 example above. This adds organic sessions that have no matching click.

Different URLs

“Click, impression, and position data are attributed to the canonical URL of the link.” GA4 records the URL that was actually loaded, with its query string, after any redirect. If Google shows /shoes/ but the page redirects to /shoes/all/, the two tools will list different pages.

Estimates, delays and dates

GA4 user and session counts are estimates, reports can apply data thresholds, and Search Console data reaches GA4 with a delay. Check that the GA4 property time zone and the date ranges match before you compare totals.

Useful explorations and comparisons for SEO

Standard reports cover most daily questions. For anything more specific, Google notes that “Explorations gives you access to data and analytical techniques that aren't available in reports.” A free-form exploration is enough for most SEO work.

Explorations that pay off for SEO, all filtered to Session default channel group = Organic Search unless noted:

• Organic landing pages × device. The layout above. Sort by sessions, then look at engagement rate and key events per row.
• Organic landing pages × country. Shows which markets your pages actually serve, useful for international sites and hreflang work.
• Landing pages × key events. Put the event name in columns and key events in values to see which pages lead to which conversions.
• Organic vs other channels. Remove the filter and use Session default channel group as rows to compare engagement and key events per channel.
• Before and after. Compare two date ranges, for example the four weeks before and after a migration or a core update, by landing page.
• Google only. Filter on Session source / medium = google / organic when you want to put the numbers next to Search Console.

One setting limits all of this. Google states: “The data retention setting only affects explorations and funnel reports.” If retention is left at two months, an exploration cannot show you last year. Set it to 14 months, the longest option for user and event data on standard properties, as early as possible.

AI assistants and referral traffic

GA4's default channels now include AI Assistant. Google describes it as the channel “by which users arrive at your site from sources like ChatGPT, Gemini, Deepseek, Copilot, or Grok. It excludes Google’s AI Overviews and AI Mode.” Clicks from AI Overviews and AI Mode stay in Organic Search, so you cannot separate them from classic Google results in GA4.

In practice, not every AI visit lands in that channel:

• An AI tool that is not on Google's list arrives with a normal referrer and shows up as Referral, for example chat.example-ai.com / referral.
• Older data, from before the channel existed in your property, shows AI tools as Referral too, so a trend line can jump when the classification changes.
• Visits from desktop and mobile apps often carry no referrer at all and end up in Direct.

To see the full picture, look at Session source in Traffic acquisition rather than the channel alone, and keep a short list of AI sources to check each month. If you need your own grouping, create a custom channel group; the default one cannot be edited.

Common mistakes

• ✕Matching clicks to sessions one to oneThey measure different things; compare trends, not totals.
• ✕Comparing all engines with GoogleFilter to google / organic before you put GA4 next to Search Console.
• ✕The wrong channel dimensionUse Session default channel group for traffic, not the key-event attributed Default channel group.
• ✕No key events, or far too manyWithout them you cannot show value; with every scroll marked, the number means nothing.
• ✕UTM tags on internal linksA UTM on your own banner starts a new session and replaces the organic source.
• ✕Self-referralsPayment gateways and your own subdomains appear as Referral and steal organic sessions; set unwanted referrals and cross-domain measurement.
• ✕Two-month data retentionExplorations cannot reach back further than the retention setting.
• ✕Tag missing on some templatesOrganic landing pages without the tag simply vanish from GA4.
• ✕Search Console linked to the wrong propertyAn http, www or subdomain-only property gives partial data.
• ✕Forgetting to publish the collectionThe link works but the reports stay hidden in Library.

How to set up GA4 for SEO step by step

1. Install the Google tag on every template and confirm visits in the Realtime report, including on landing pages built outside your main CMS.
2. Check enhanced measurement in the web data stream, so page views, scrolls, outbound clicks, site search and file downloads are collected.
3. Set data retention to 14 months in Admin › Data collection and modification › Data retention.
4. List unwanted referrals and set cross-domain measurement if checkout or booking happens on another domain.
5. Mark your key events: leads, purchases, sign-ups, calls. Test each one once.
6. Set up consent mode with your consent platform, using the advanced implementation if your legal team allows it.
7. Link Search Console in Admin › Product links › Search Console links, choosing the property that covers the whole site.
8. Publish the Search Console collection in Reports › Library.
9. Build and save an organic exploration by landing page, device and country, and share it with the team.
10. Write down your reporting rules: which channel dimension, sessions or users, Google only or all engines. Consistency matters more than the choice.

FAQ

Sources

• Google Analytics Help — Default channel group
• Google Analytics Help — Connect Search Console to Google Analytics
• Google Analytics Help — Google organic search traffic report
• Google Analytics Help — Key event
• Google Analytics Help — Mark events as key events
• Google Analytics Help — Engagement rate and bounce rate
• Google Analytics Help — About Analytics sessions
• Google Analytics Help — Understand user metrics
• Google Analytics Help — Consent mode on websites and mobile apps
• Google Analytics Help — Behavioral modeling for consent mode
• Google Analytics Help — Known bot-traffic exclusion
• Google Analytics Help — Get started with Explorations
• Google Analytics Help — Data retention
• Search Console Help — What are impressions, position, and clicks?

Quotes checked against the official pages on 30 October 2026.