Using Search Console and GA4 together (organic meets conversion)
GA4 tells you what visitors did; Search Console tells you what they searched to arrive. Linked, they answer the question neither can alone: which queries actually drive revenue.
Search Console knows what happened before the click — queries, impressions, positions. GA4 knows what happened after — engagement, conversions, revenue. Neither can see the other half, and linking them gives you the one report that spans both: which search queries bring traffic that actually converts. The link takes two minutes and the resulting reports are hidden by default, which is why most properties have the integration and never use it.
What each tool actually knows
| Search Console | GA4 | |
|---|---|---|
| Queries | Yes | No |
| Impressions and position | Yes | No |
| Click-through rate | Yes | No |
| On-site behaviour | No | Yes |
| Conversions and revenue | No | Yes |
| Attribution across channels | No | Yes |
The gap in the middle is the interesting part. Search Console tells you a query drives 4,000 impressions and a 2% click-through rate. GA4 tells you organic search converted at 1.8%. Neither tells you whether that query produced converting visitors.
Linking them
In GA4: Admin → Product links → Search Console links → Link. Choose the property and the web stream.
Then — and this is the step everyone misses — publish the reports. The Search Console reports are created but hidden by default:
- Go to Reports → Library.
- Find the Search Console collection.
- Publish it.
Until you do that, the link exists and no report shows it. A surprising number of properties are linked and unused for exactly this reason.
What the joint reports give you
Two reports appear:
Queries — search queries with impressions, clicks, and click-through rate, joined to GA4 landing-page behaviour.
Google organic search traffic — landing pages with both the Search Console metrics and GA4 engagement and conversion data.
The second is the more useful of the two, because it answers the question neither tool answers alone: which pages earn search traffic that converts?
The four analyses worth doing
1. High impressions, low click-through
The page ranks and nobody clicks. This is a title and meta description problem, not a content or tracking problem, and it is the cheapest fix in search: rewriting a title tag can move click-through materially without touching rankings.
2. High clicks, low engagement
People arrive and leave. Either the page does not deliver what the query promised, or you are ranking for a query with different intent than you assumed. Check the queries driving that page before rewriting anything.
3. High traffic, zero conversions
Common on informational content, and not necessarily a problem — informational pages serve the top of the funnel. It becomes a problem when the page has obvious commercial intent and no path forward. Add the next step rather than assuming the traffic is worthless.
4. Low traffic, high conversion rate
The most actionable pattern and the most frequently missed. A page converting at 8% from 200 monthly visits is worth more attention than one converting at 0.3% from 20,000. Find where it ranks, and whether a position improvement is achievable.
The limitations to know before you trust it
Attribution differs. Search Console counts a click; GA4 counts a session. Blocked tags, consent declines, immediate bounces, and redirects all mean GA4 sees fewer sessions than Search Console sees clicks. Expect the numbers not to match, and do not spend a day reconciling them.
Query data is sampled and thresholded. Search Console withholds low-volume queries for privacy reasons, so query totals will not sum to your click totals.
Date ranges differ. Search Console data lags by a couple of days; GA4 is closer to real time. Comparing a range that includes the last two days compares complete data to incomplete data.
The join is at the landing-page level, not the session level. You cannot follow an individual user from query to conversion, only see the aggregate relationship.
Using both tools during a migration or redesign
The joint view is at its most valuable when something changes structurally, because it separates two things that otherwise look identical.
After a site migration, traffic to a page can fall for two very different reasons: the page lost rankings, or the page still ranks and something broke on arrival. Search Console alone cannot distinguish them; neither can GA4.
Read them together:
- Impressions down, click-through steady → a ranking or indexing problem. Look at redirects, canonicals, and crawlability.
- Impressions steady, clicks down → a title, description, or snippet problem. The page still ranks; it stopped being clicked.
- Clicks steady, GA4 sessions down → not a search problem at all. The tag broke, or consent behaviour changed. Go to the conversions-dropped runbook.
That third row is the one people miss, and it is the reason to check both tools before rewriting content that was never the problem.
Consent affects the GA4 half
Everything on the GA4 side of the join is subject to consent. A user who declines analytics consent still appears in Search Console — the click happened — but produces no GA4 session.
So a page with a high Search Console click count and a low GA4 session count may reflect consent decline rather than a tracking bug, particularly for EEA-heavy traffic. Check your consent rate before concluding something is broken. Verifying Consent Mode covers the checks.
FAQ
Why can I not see Search Console data in GA4 after linking?
Because the reports are hidden by default. Go to Reports → Library, find the Search Console collection, and publish it.
Why do Search Console clicks not match GA4 sessions?
They measure different things — a click versus a session that GA4 successfully recorded. Blockers, consent declines, immediate bounces, and redirects all create a gap. Some divergence is normal.
Can I see conversions by search query in GA4?
Only at the landing-page level. Query data joins to pages rather than to individual sessions, so you can see which pages earn converting search traffic but not attribute a conversion to a specific query.
Does linking Search Console to GA4 improve my rankings?
No. It is a reporting integration only and has no effect on how Google ranks your pages.
Which tool should I trust for organic traffic numbers?
Search Console for clicks, impressions, and queries; GA4 for on-site behaviour and conversions. Each is authoritative for its own side of the click.
Organic traffic is only useful if the conversions get recorded — check yours with the free tracking audit on any URL.
See where your tracking stands
Run the same 13-check audit referenced in this post against any URL. No signup, results in seconds.