Search Console's story ends at the click. Once a searcher lands on your page, Google stops reporting and Google Analytics 4 takes over, and whether that visitor read, enquired or bought lives only there. Out of the box GA4 shows none of it in a way an SEO can use. You need a handful of views, each answering one question: how much organic traffic arrives, where it lands, what it does next, and whether that's changing.
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. Everything between those moments drops a visitor from one count and not the other: a declined consent banner, an ad blocker, a page so slow they leave before the tag fires. And Google's Analytics help says a session ends by default after 30 minutes of inactivity, so 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 after.
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 AI traffic on its own, build a custom channel group under Admin, Data display, Channel groups, with a rule matching those source domains; see Measuring your AI visibility.
Mark the events that mean money
GA4 records everything as an event, from a page view to a form submission. None of it says whether organic traffic is working until you tell GA4 which events count. Those are key events (Google renamed conversions to key events in 2024, per its Analytics help), and a property with none configured can only judge organic by volume, which is how "traffic is up" gets reported to a client whose phone stopped ringing.
Pick two or three events that mean a real outcome: a purchase, a lead form, a booking, a phone tap. Some exist already; 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 then show them per channel and 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 key event, or had at least two page views. High engagement with no key events means interested visitors and no next step; low engagement means the page is mismatched to the search that sent people there.
View one: what organic landing pages do
Open Reports, Engagement, Landing page. This 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 key events.
Sorted by sessions, the top of the list is where organic traffic lands. Then scan for pages with plenty of sessions and almost no key events: either the search behind them is informational and the page offers no path toward an enquiry, or it has a path nobody takes. Writing a page that ranks covers both fixes. Editors can Save the table as a new report for next month.
View two: organic against every other channel
Open Reports, Acquisition, Traffic acquisition. The primary dimension is Session default channel group, so you get one row per channel with sessions, engagement rate and key events. This answers "is organic doing its job": compare the organic row's key events per session with direct, paid and referral. Organic converting like your other channels is carrying its weight; organic bringing most of your sessions and a sliver of your key events is attracting the wrong searches, and The buying-intent ladder is the remedy.
One trap. Traffic acquisition credits a key event to the channel of the session it happened in, so a person 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 brought the person the first time. Organic usually looks better there; neither view is the truth alone. Report both and say 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 Search Console clicks, impressions and position next to its GA4 sessions, engagement and key events, the only report where both halves sit in one row. The Queries report beside it is Search Console's query data and can't be joined to key events, so it's context, not attribution.
Then under Admin, Data collection and modification, Data retention, 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, but that's where you'll eventually want a year of history, and data you didn't retain is gone.
What to take away
- GA4 and Search Console measure different moments, so their numbers never match and shouldn't be forced to.
- Organic traffic can only be judged once key events are marked, because sessions alone say nothing about outcomes.
- 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.