Search Console's story ends at the click. Once a searcher lands on your page, Google stops reporting and GA4 takes over, and whether that visitor read, enquired or bought lives only there. Out of the box GA4 shows none of it in a form an SEO can use, so you set up a few views that each answer one question.
Why GA4 and Search Console never agree
Search Console counts a click on Google's results page. GA4 counts a session when its tag runs on your page. Anything between those two moments drops a visitor from one count and leaves them in the other: a declined consent banner, an ad blocker, a page so slow the visitor leaves before the tag fires.
Sessions add another gap. Google's Analytics help says a session ends by default after 30 minutes of inactivity. One person clicking two of your results in an afternoon is two clicks and possibly one session. Use Search Console for what Google did and GA4 for what people did afterwards.
GA4 decides a session came from search by reading the referrer. The Session source / medium dimension shows google / organic, and Session default channel group folds every search engine into Organic Search. Visits from AI assistants don't land there. A referral from an assistant's own domain, such as chatgpt.com or perplexity.ai, is filed under Referral. To report that traffic separately, build a custom channel group under Admin, Data display, Channel groups, with a rule matching those source domains. Measuring your AI visibility walks through it.
Mark the events that mean money
GA4 records everything as an event, from a page view to a form submission. Until you say which events matter, it can judge organic traffic only by volume. That's how "traffic is up" gets reported to a client whose phone stopped ringing.
Google calls the events that matter key events. It renamed conversions to key events in 2024, per its Analytics help. Pick the two or three that mean a real outcome: a purchase, a lead form, a booking or a phone tap. Some already exist. Others you create, usually from a thank-you page view or in Google Tag Manager. Then go to Admin, Data display, Events and switch on Mark as key event for each. Every report can now show them per channel and per landing page.
Engagement rate is the secondary signal. Google's Analytics help defines an engaged session as one that lasted longer than 10 seconds, had a marked event, or had at least two page views. High engagement with no marked events means interested visitors and no next step. Low engagement means the page doesn't match the search that sent people there.
View one: what organic landing pages do
Open Reports, Engagement, Landing page. The table lists the pages visitors arrived on, which for organic is the page Google sent them to. Click Add filter, choose Session default channel group, and set it to Organic Search. Every row is now an organic entry point with its sessions, engagement time and marked events.
Sort by sessions and the top of the list is where organic traffic lands. Then look for pages with plenty of sessions and almost no marked events. Either the search behind them is informational and the page offers no path toward an enquiry, or the path exists and nobody takes it. Writing a page that ranks covers both fixes. If you're an editor on the property, Save the table as a new report so next month's check takes a minute.
View two: organic against every other channel
Open Reports, Acquisition, Traffic acquisition. The primary dimension is Session default channel group, so each channel gets a row with its sessions, engagement rate and marked events. Compare the organic row's events per session with direct, paid and referral. If organic converts like your other channels, it's carrying its weight. If it brings most of your sessions and a sliver of your outcomes, it's attracting the wrong searches, and The buying-intent ladder is the remedy.
There's a trap here. Traffic acquisition credits an event to the channel of the session where it happened. Someone who found you by searching on Monday and typed your URL on Thursday to buy converts under Direct. The User acquisition report beside it uses First user default channel group, which credits the channel that first brought the person. Organic usually looks better there. Neither view is the whole truth, so report both and label which is which.
Link Search Console and set retention before you need it
Two settings pay off for a year. Under Admin, Product links, link your Search Console property to the GA4 property. Then open Library in Reports and publish the Search Console collection. It adds a Google organic search traffic report that puts each landing page's clicks, impressions and position next to its GA4 sessions, engagement and marked events. It's the only report where both halves share a row. The Queries report beside it holds Search Console's query data and can't be joined to your events, so treat it as context rather than attribution.
Next, go to Admin, Data collection and modification, Data retention and change event data retention from the default of two months to 14 months, the longest a standard property allows according to Google's Analytics help. It only affects Explorations, GA4's custom analysis tool. That's where you'll eventually want a year of history, and data you didn't retain is gone.
Frequently asked questions
Does Google Analytics have SEO?
Not as a feature you switch on. GA4 doesn't rank pages or audit them. It measures what organic visitors do after Google sends them, which is the half of SEO that Search Console can't see. Filter reports to Organic Search and you get landing pages, engagement and outcomes for search traffic.
How do I add a user to Google Analytics 4?
User management sits in the Admin area, alongside the settings in this lesson. Give each person the role that matches their job. Editors can save reports and change settings such as event marking, as in view one, so hand that role to whoever maintains the setup.
Is SEO replaced by AI?
AI assistants send some visitors, but GA4 files them under Referral, not Organic Search. That means your organic numbers don't include them unless you build a custom channel group. Measure both and you can see how much each source actually brings.
Why don't my GA4 and Search Console numbers match?
They count different moments. Search Console counts clicks on Google's results page, and GA4 counts sessions once its tag runs. Consent banners, ad blockers and slow pages all open a gap between the two. Expect the numbers to differ and read each for what it measures.
What to take away
- GA4 and Search Console measure different moments, so their numbers never match and shouldn't be forced to.
- You can judge organic traffic only after you mark your outcome events, because sessions alone say nothing about results.
- The Landing page report filtered to Organic Search shows where search traffic lands and which pages waste it.
- Traffic acquisition shows whether organic converts like your other channels. User acquisition shows the credit that session-based reports hide.
Next
The last piece is what a ranking change does and doesn't mean: Reading rank movements honestly.