Google Search Console and Google Analytics 4 at a glance
Search Console takes its data from Google Search itself. Its performance report, as Google's help centre documents it, shows clicks, impressions, click-through rate and average position, filterable by query, page, country, device, search appearance and date. Its indexing reports show which pages Google has indexed and why others are excluded. No tag on the site is needed; verification of ownership is enough. The Search Console tutorial covers setting up the property and reading each report.
GA4 takes its data from the site. A tag in the page sends events as people browse, and GA4 groups them into users and sessionsA group of one user's interactions with a site or app in one visit, ended by inactivity., records engagement and counts the events marked as key events. Organic search is one channel among many, defined by GA4's own classification of where each session came from. The GA4 reports and dimensions guide explains how sessions, users and engagement are counted, how dimensions and metrics are scoped, and where thresholdsThe GA4 mechanism that withholds report rows that could identify individuals, usually small segments over short periods, when signals or modelling are used. hide rows.
The two meet at the landing page. Search Console knows which page a search click led to and which query preceded it; GA4 knows what the visitor did on that page and afterwards. Neither knows the other half without help, which is why they are linked rather than chosen between.
Compare table
Google Search Console vs Google Analytics 4
| Row label | Google Search Console | Google Analytics 4 |
|---|---|---|
| Where data comes from | Google Search's own logs of results shown and clicked | A tag on the site sending events from visitors' browsers |
| Before or after the click | Before: impressions, position and the click itself | After: the session, engagement and key events |
| Key metrics | Clicks, impressions, click-through rate, average position | Sessions, users, engaged sessions, engagement rate, key events |
| Query data | Yes, with rare queries anonymised and tables capped | Not from its own collection; shown only through the linked Search Console reports |
| Indexing data | Page indexing, URL inspection, sitemaps and enhancement reports | None |
| Conversion data | None | Key events and revenue by landing page and channel |
| Sampling and thresholds | Anonymised long tail and row limits in the interface; exports get closer to complete | Standard reports unsampled; data thresholds and the (other) row can hide rows |
| Coverage | Google Search only | Every source, including other search engines, as consent and blockers allow |
| Best use | Visibility, demand, snippet performance and technical health | Behaviour and outcomes of organic visitors against other channels |
Read the table by its second row. Every metric Search Console offers describes a moment on Google's results page; every metric GA4 offers describes a moment on your site. The rest of the differences follow from that.
When to choose Google Search Console
Choose Search Console for any question about how the site appears in Google Search. Whether a page is indexed, which queries it shows for, whether impressions rose because the site appeared on more results pages, whether click-through fell because a result feature now sits above the listing: only Search Console has that data, because only Google sees the results page.
It is the first stop when organic traffic falls. Filtered to non-brand queries, the main country and a page group, as the tutorial recommends, it separates a ranking change from a demand change, a brand effect or an indexing fault. Its page-and-query view shows when two URLs start sharing a query, and URL inspection shows the canonical Google chose for a page.
It is also the right tool for technical health. The page indexing report, sitemaps, Core Web Vitals and enhancement reports describe how Google processes the site, which GA4 cannot see at all. For a site split across subdomains, a Domain property covers every subdomain in one view, a point worth weighing alongside the subfolder versus subdomain comparison.
When to choose Google Analytics 4
Choose GA4 for any question about what organic visitors did. Engagement on organic landing pages, the share of sessions that reached a key event, revenue from organic search, and how organic visitors behave compared with paid or email visitors all come from GA4, because they happen after the click.
It is the place where SEO is judged against the business. The SEO KPIs and reporting guide puts engagement and outcomes at the end of a chain that starts with coverage and visibility; those last two links come from analytics and, for leads and revenue, from the CRM. Campaign tagging on links the business controls keeps paid and email traffic out of the organic channel, which is the commonest cause of inflated organic figures.
GA4 also covers sources Search Console does not. Organic sessions from other search engines, referrals from sites that link to a guide and returning visitors who come back directly all appear in GA4, so it is the tool for questions about traffic as a whole rather than Google Search in particular.
Decision table
| Question | Use | Why |
|---|---|---|
| Which queries does a page show for, and at what position? | Search Console | Only Google records results shown and clicked |
| Is an important page indexed, and which canonical did Google choose? | Search Console | Page indexing and URL inspection |
| Did organic visitors convert, and on which landing pages? | GA4 | Key events happen after the click |
| Did traffic fall because of rankings, demand or tracking? | Both | Search Console for visibility and clicks, GA4 for whether sessions fell with them |
| How does organic compare with paid, email and referral? | GA4 | It records every channel under one set of rules |
| Did click-through drop after a result feature appeared? | Search Console | Impressions, clicks and search appearance by query |
| What revenue does organic search produce? | GA4, with the CRM for offline outcomes | Revenue is recorded on the site and in the business's systems |
Why the numbers never match
A Search Console click and a GA4 session are different events. The click is recorded when someone selects a result on Google's page. The session is recorded only after the landing page loads, the analytics tag runs and the visitor's consent allows it to send data. Anyone who leaves during the load, declines analytics cookies or uses a blocker that stops the tag produces a click with no session.
Coverage differs in both directions. Search Console's web search report covers Google Search alone, with other search types reported separately, while GA4's organic search channel includes every search engine it recognises. A site with meaningful traffic from other engines can see more organic sessions in GA4 than clicks in Search Console for the same period.
The tools also attribute data differently. Search Console assigns results to the canonical URL Google chose, so clicks on a duplicate can appear under another page; GA4 reports the landing page the visitor actually loaded. GA4 classifies each session's source by its own rules, and Google documents that its user and session counts are estimated. Search Console anonymises rare queries and caps its tables; GA4 withholds small rows under data thresholds. Even the reporting day can close at different hours in the two tools.
None of this is a fault. Compare the two for direction and proportion: if clicks and organic sessions move together, the relationship is stable; if one moves and the other does not, look for a tracking, consent, canonical or channel classification change before concluding anything about rankings.
A walking guide publisher reconciles a gap
For a year, Wrenhill Walking Guides has seen GA4 organic sessions run about a fifth below Search Console clicks on the same pages: 14,200 sessions against 18,000 clicks in a typical month. In the month after a new consent banner launches, clicks hold at 18,100 but sessions fall to 12,300, a gap of almost a third. Search Console shows no change in impressions or position, so the team treats the drop as a measurement change, notes the banner date in its annotations log, and reports organic performance from Search Console clicks and GA4 key event rate rather than from session totals until the new baseline settles.
Common mistakes
- Expecting clicks to equal sessions, then chasing a tracking fault that is really a difference in definitions.
- Reporting organic traffic from Search Console alone, which says nothing about what visitors did.
- Reporting SEO from GA4 alone, which cannot explain whether a change came from rankings, demand or indexing.
- Reading site totals in Search Console, with brand, country and device mixed together.
- Leaving the two unlinked, so the Search Console reports never appear alongside GA4's landing page data.
- Treating average position as a rank, when it is a mean across every impression in the period.
- Ignoring consent changes, which move GA4 counts without any change in search performance.
