Linking the two takes five minutes, and afterwards half the people who did it hunt through the menu for the new reports in vain. Not because anything went wrong, but because there is one more step after the last click, and the setup itself never mentions it. The reports are there. They are just invisible.
This piece walks the setup including that step, then states plainly where the limit of the integration sits (it is tighter than almost anyone expects), and shows the one view that makes the whole exercise worth it.
What the link actually gives you
The two tools see two halves of the same movement. Search Console knows the route to your site: which query, which position, how often shown, how often clicked. GA4 knows the route across it: how long someone stayed, how far they scrolled, whether a form went out at the end. Kept apart, that is two reports you jump between while adding the numbers up in your head. Linked, it is one table: query, click, behaviour, enquiry.
The point is not convenience. It is the question nobody could answer before. Not "which page gets clicks" but "which clicks turn into money".
What you need first
Three prerequisites, and most attempts fail on the second:
- The Editor role on the GA4 property. Read access is not enough.
- Verified owner status on the Search Console property. Not merely a user with full access that a colleague granted you, but owner. That is a different tier, and it is usually missing precisely when an agency set Search Console up years ago.
- A data stream in GA4 to attach the link to.
If ownership is what you lack, that is an access problem, not a technical one. How to put both accounts in your own name from the start is covered in setting up Google Search Console.
The setup, including the step everyone misses
- In GA4, click Admin at the bottom left.
- Under Product links, open Search Console links.
- Link, pick the matching Search Console property, attach your web data stream, confirm.
- And now the step nobody announces: in the left navigation go to Reports, then to Library at the bottom. Find the Search Console collection, open the three-dot menu on its card, and choose Publish.
Only after step four does the entry appear in the navigation. The collection ships unpublished on purpose, and because step three ends with a success message, the setup feels finished. If you cannot see the Library at all, you do not have Editor rights.
Google can move these labels around at any time, and has done so more than once. The logic stays put: link under product links, make visible in the library.
After linking, give it time. Search Console data becomes available roughly two days after it is collected, in Search Console itself just as much as in GA4. An empty report on setup day is normal, not a fault.
The two reports and the question each one answers
The collection brings two reports, and they answer different things.
Queries. The searches people used to arrive, with impressions, clicks, CTR and average position. At heart this is the Search Console performance report, rendered inside GA4. The question: what are the people who land on my site actually searching for?
Google organic search traffic. Landing pages with the Search Console metrics and the GA4 metrics beside them, so impressions and position sit in the same row as engagement time and conversions. The question: which landing page earns its keep, and which one only collects clicks?
The second one is the valuable report. The first is convenience.
The limit almost nobody states clearly
Here comes the disappointment, and it is better known upfront: the search query cannot be combined with your own events and dimensions. There is no row saying "query X produced three form submissions". In the queries report you can only break the data down by Search Console dimensions; in the landing page report only by country and device. That is the whole range.
The reason is not malice but privacy and the data model: Google releases queries in aggregate only and does not tie them to individual sessions. The one bridge between the two worlds is the landing page.
Which leads to a recommendation that has nothing to do with tools and everything to do with how your site is built: if you want to know which search intent brings you customers, different intents need different landing pages. A page that simultaneously ranks for "heat pump cost", "heat pump grants 2026" and "heat pump servicing" can never tell you which of those three intents pays. Three pages can. That is the real lever hiding behind this limit, and it is worth more than any reporting trick.
Why the numbers never match
The first reaction to the new report is almost always: "Search Console says 4,200 clicks, GA4 says 2,500 organic sessions. Which one is right?" Both. They measure different things, and the direction of the gap is predictable: clicks are almost always higher than sessions.
The causes, largest first:
- The cookie banner. Anyone who declines produces no session in GA4. On European sites this is usually the single biggest item. How to estimate your consent rate is in consent mode and your GA4 data.
- A click is not a session. Someone who hits back before the measurement script loads has been clicked and not counted.
- Ad blockers. They block GA4, not the counting on Google's side.
- Different bot filtering. Both filter, but not the same things.
- Time zones. Search Console cuts the day differently from your GA4 property. On daily comparisons that produces visible jumps; on monthly totals it barely registers.
- Redirects. When a clicked URL redirects, Search Console counts the old address and GA4 the new page. The total matches, the row does not.
As an experience value rather than a rule: organic sessions at sixty to eighty percent of clicks is unremarkable. At thirty percent, go and look at the banner. More sessions than clicks means something is wrong with channel attribution, and then direct traffic in GA4 is the place to look, starting with whether internal links carry campaign parameters.
The one view that makes it worth it
Open the organic search traffic report and read four patterns out of it. Each one means a different job.
Many clicks, no conversions. The page attracts people and loses them. Two possible reasons, and you can tell them apart: if engagement time is high, it was read and then not acted on, so the next step is missing on the page. If it is low, the page broke the promise the search result made. Which of the two engagement-time figures you should be reading here, and what counts as high, is in showing engagement time in GA4.
Few clicks, good conversion rate. This is the most interesting row in the whole report and the one most often overlooked. Here the content works, nobody just sees it. The lever is not the copy but the visibility: serve more related queries, link to it internally, sharpen the snippet.
Many impressions, hardly any clicks. The decision happens in the search result, not on the page. Whether that is down to position, intent or the snippet is sorted out in impressions but no clicks.
Pages that do not appear at all. What gets clicks is in the report. What is missing is nowhere, and that is often the bigger news. Compare the list against your most important service pages. If one of them is absent, that is not a reporting question but an indexing or visibility one.
Time windows: save the data before it goes
Search Console keeps sixteen months, and the GA4 report shows no more than sixteen months either. GA4 has its own retention setting for your event data, and out of the box it sits well below the maximum. Anyone who never touched it has too little history for year-over-year work.
Two consequences. Set retention in the admin section to the highest value available: it does not apply retroactively, which makes it a thing better done today than next year. And export the key tables once a quarter if you need comparisons across longer spans.
When the built-in reports are not enough
Two routes beyond them, both of which cost effort.
A reporting tool such as Looker Studio can pull both sources and join them on the landing page. That gives you free-form tables and your own metrics, but it demands that you build the join correctly, and it repays sloppiness with unusable numbers whenever the URL formats of the two sources do not match exactly (trailing slash, parameters, upper and lower case).
The BigQuery export gives you the raw data and therefore everything the reports refuse. It also demands SQL and a billing account, and for a site with two hundred pages that is a cannon aimed at a sparrow.
Traffalyzer does exactly this join for you: landing pages, their queries and the behaviour metrics in one view, without marrying two accounts and a reporting tool. Deciding which of the four patterns above is this month's job is still yours.
Where to start
- Check whether you are listed as an owner in Search Console, not just a user.
- Link it under Admin, product links.
- Publish the collection in the library, or you will see nothing.
- Wait two days before getting annoyed about empty reports.
- Set data retention to the highest available value.
- Open the organic search traffic report and walk the four patterns.
- Pick one row and work on it. Not twenty.
Frequently asked questions
How do I connect GA4 to Search Console?
In GA4 go to Admin, find the product links section, open Search Console links, and connect the matching property to your web data stream. Then publish the report collection in the library, otherwise it stays invisible in the menu. You need the Editor role in GA4 and verified owner status on the Search Console property.
Why can I not see the Search Console report in GA4?
Nine times out of ten because the collection is not published. It ships unpublished by default, and the link itself still reports success. Go to Reports, then Library, find the Search Console collection and publish it. If you cannot see the library, you lack the rights. If the reports are there but empty, wait two days.
Why do clicks in GA4 and Search Console disagree?
Because they count different things: Search Console counts a click in the search result, GA4 counts a session on your site. Between the two sit the cookie banner, people leaving before the measurement script loads, ad blockers, different bot filters and shifted day boundaries. Clicks are therefore almost always higher than organic sessions. Only when sessions exceed clicks is something genuinely wrong.
Can I see which query led to a conversion?
No, and that is a hard limit rather than a settings problem. Google releases queries in aggregate only and does not connect them to individual sessions. The connection exists solely through the landing page. If you want to follow intent through to a sale, put separate intents on separate landing pages, and the page becomes the proxy for the intent.
Do I even need the link?
Not strictly; you can use both tools side by side. It saves the jumping back and forth and puts reach and behaviour for a landing page in one row, which is exactly the view decisions come out of. Five minutes of setup for a permanently better view is a good trade.
What permissions do I need?
The Editor role on the GA4 property and verified ownership of the Search Console property. The second is the more common hurdle: full access as a user is not enough. If an agency created the Search Console property back then, you need to be added as an owner, and you should do that regardless of this integration.
How long is the data kept?
Search Console keeps sixteen months, and the GA4 report shows no more than that. On top of that, your own GA4 event data follows the property's retention setting, which sits below the maximum out of the box. It does not apply retroactively, so it is a setting worth getting right early.
Can I link more than one Search Console property?
One link applies per data stream. If you run both domain and URL-prefix properties, pick the one that covers your actual scope, usually the domain property. With several websites in one GA4 property you need a separate link per data stream.
Why are pages in the report that no longer exist?
Because Search Console counts backwards: clicks from four months ago stay in the history even if the URL now redirects or is gone. If an old URL is still gathering fresh impressions, though, that is a hint that a redirect is missing or that Google still treats the old address as the right one.