Key takeaways.
- Search Console clicks and GA4 sessions use different counting rules, so a gap alone does not prove a tracking fault.
- Filter GA4 to google / organic and align dates, site scope and landing pages before comparing.
- Investigate a sudden divergence through tags, consent, redirects and the affected pages.
Summarise with AI
You open a monthly report. Search Console says one thing about Google clicks, GA4 shows another number for organic sessions, and somebody asks which one is right. I have seen this turn into a tracking panic far too quickly.
Both numbers can be right. They describe different parts of the journey and use different counting rules. The useful question is whether their trends make sense once you compare the same traffic, dates and pages.
What each tool counts.
A Search Console click records someone clicking a result in Google Search that leads to your site. GA4 measures activity after a person reaches a tagged website or app. A session is a period of interaction, rather than a count of individual search-result clicks. Google's own guide to using Search Console and Analytics together says the totals are expected to differ, even when you compare the closest available metrics.
GA4 starts a session when someone views a page or screen and no session is active. It normally times out after 30 minutes of inactivity, although the setting can be changed. Google's session definition is worth reading before treating one search click as one Analytics session.
Search Console can record a click even when Analytics never receives the expected page data. Analytics can also count a session under a different attribution or reporting scope. That is why a difference alone cannot tell you that a tag is broken, that consent cost you a fixed percentage of visits, or that Google has sent the “wrong” number.
Make the comparison fair first.
1. Match the traffic source.
Check the Search Console report is for the Google Search result type you intend to analyse. In GA4, filter the session source and medium to google / organic. An all-organic channel can include visits from other search engines, so it is a wider population than Google Search clicks. Do not compare property-wide Search Console clicks with a single GA4 landing page either.
2. Match the time and location.
Use the same dates and, where relevant, the same country and device filters. Keep both properties' reporting settings in mind, and avoid treating the newest Search Console day as final while data is still arriving. If one chart uses a rolling 28 days and the other uses calendar months, the gap may be yours rather than the tools'.
3. Match the site and page.
Check that the Search Console property covers the same hostnames and sections that GA4 measures. A domain property, a URL-prefix property, a staging site and a multi-domain GA4 property can all describe different scopes. Page-level comparisons need extra care: Search Console assigns performance to Google's selected canonical URL, while GA4 reports the URL on which its tag ran. Normalise URLs before deciding that one page has disappeared.
Then investigate the pattern.
I start with a daily trend, not a percentage called “missing traffic”. If clicks and Google-organic sessions move broadly together, a modest difference is generally expected. Google's reconciliation guidance says to investigate a large divergence rather than assuming a fault from the existence of any gap.
If the lines split suddenly, check what changed on that date. Was a site release deployed? Did the tag, consent setup or redirect path change? Did the site move domains or introduce a new subdomain? Test the affected landing pages on desktop and mobile, and confirm the GA4 tag actually sends data under the consent choices you expect. Then inspect acquisition settings and any campaign parameters that might change how sessions are attributed.
Look at the pages and queries behind the change as well. Search Console includes some search surfaces and non-HTML results that a normal GA4 page tag may not measure in the same way. Google also notes differences from canonical URLs, implementation, attribution and bot handling. Several factors can apply at once. The aim is to narrow the explanation, not force the totals to be identical.
How I would report it to a client.
I would show Search Console clicks and GA4 google / organic sessions as two labelled lines for the same dates, followed by a short note: what moved, which filters were applied, what was checked, and what remains uncertain. If a form enquiry is part of the conversation, I would verify that the key event represents a real submission before calling it a lead. I would not join aggregate search queries to aggregate GA4 events and pretend to know which keyword produced an individual enquiry.
Once the dates, source and pages match, you can see whether there is actually a tracking problem. Sometimes the gap is just the way the two tools count. I would start with the daily trend and the landing pages where the lines split. For more on connecting that measurement to page work, see our SEO and PPC service.
