How to Connect Google Analytics to Google Search Console
A five minute job that puts what people searched for next to what they did once they arrived. Neither tool shows both halves alone. The payoff is narrower than most people expect. It is still worth the five minutes.
Why Bother
Search reporting knows what people typed and stops at the click. Analytics knows what happened after the click and cannot see what was typed. Joining them lets you look at one page and see both, which is the only reason to do this.
The question it answers. Did the right people arrive.
A page can attract plenty of search appearances and plenty of visits while the two have nothing to do with each other. Seeing the searches alongside the behaviour shows whether the traffic matches the intent.
The finding it produces most often. A mismatch.
A page appearing for searches it does not really answer, receiving visitors who leave immediately. That is one finding rather than two half findings from separate tools.
Why it is not automatic. Two separate products.
They are built by the same company and they are genuinely separate systems with separate access. Connecting them is a deliberate act rather than something that happens on its own.
How long it takes. Minutes.
Assuming you have the access described in block four. The work is in having the right permissions rather than in the connecting.
What it is worth to a small business. One habit.
Anybody who has to open two separate tools to answer one question tends to open neither. Removing that friction is the practical value here. It matters more for a business without a marketing department than for one with an analyst.
Who never gets round to it. Nearly everybody.
It is a small job with no deadline attached, which is precisely the sort of task that stays undone for years. Block six is about when to do it instead.
What You Actually Get
Less than people assume. The joined reporting is a specific, limited view rather than a merging of the two tools. Knowing its shape prevents the disappointment of hunting for something that was never going to be there.
What appears. Search data inside analytics.
Which searches brought people in, alongside what those people did afterwards, presented in analytics rather than in the search tool.
The level it works at. Landing pages.
The joining happens at the level of the page somebody arrived on. That is the unit both tools have in common. It is why the view is narrower than either tool alone.
What that excludes. Everything not a landing page.
You cannot follow the search through a whole visit. Nor attach a query to a purchase three pages later. The connection is made at the door and does not travel further into the building.
What it is genuinely worth. Convenience.
Everything visible here can be assembled by looking at both tools separately. What you gain is not having to, which is a real benefit for anybody who will otherwise not bother.
How far back it goes. Not far.
The joined reporting generally begins working from the point of connection rather than reaching backwards through your history. Another reason to do it early rather than when somebody finally wants the view.
What it is not. A new capability.
No data is created by linking. Two existing sets are shown next to each other, which is worth understanding before anybody presents it as an upgrade.
What It Does Not Do
It does not reconcile the two sets of figures. Clicks in one and visits in the other will still disagree after linking, exactly as they did before. Anybody expecting the connection to resolve that will be disappointed.
Why they still disagree. Different counting.
One counts an event in Google's results and the other counts code running on your page. Putting the two views side by side does not change either measurement.
What linking changes about it. Nothing at all.
The gap is structural. It exists for reasons of consent, blocking and definition, none of which a connection between two dashboards can touch.
Where that is explained properly. The comparison guide.
Our comparison of the two tools covers why the figures were never meant to match. This page will not repeat it, since one page in our guides owns that argument.
What to do about the discrepancy. Stop measuring it.
Compare each tool against its own history rather than against the other. A stable gap is normal and only a sudden change in it is worth investigating.
One thing worth checking after linking. That both cover the same site.
If the gap suddenly looks enormous, the two properties may not be describing the same thing, which is block five.
What You Need Before Starting
Two kinds of access and one thing that has to match. The access is where most attempts stall, because businesses frequently discover they hold one end and somebody else holds the other.
Editing rights on the analytics property. The first.
Enough permission to change the property's configuration rather than simply read its reports. Viewer access is not sufficient.
Verified ownership of the search property. The second.
Not merely access to it. You need to be recorded as an owner, which is a higher level than being able to look at the reports. Verifying a site covers how that is established.
The same website at both ends. The thing that must match.
Both properties have to be describing the same site, in the same version of its address, which sounds obvious and is where the failures come from.
Where businesses get stuck. Split access.
The developer verified the search property, the agency set up analytics and the business owns neither. Nobody can complete the link without asking somebody.
The order that avoids the problem. Own both, then link.
A business that holds the top level of each property can complete this in one sitting. One that has to email two suppliers for permissions frequently abandons the job halfway.
What to do about that. Fix ownership first.
It is a better use of an afternoon than the connection itself. Our setup guide covers why the business should hold the top level on both.
The Address Version Problem
A website can be reached at several versions of its address. With or without the leading letters, with or without a trailing slash, secure or otherwise. If your search property was set up on one version while the site actually serves another, the joined view arrives empty and nothing announces why.
How the mismatch happens. Years ago, quietly.
Somebody verified a property before the site moved to a secure address. Or before a redirect was put in place. It was never revisited.
What it looks like. Empty or partial.
Either nothing at all. Or a fraction of what you expect, with most pages missing. Both are the same cause and neither produces an error message.
The version that avoids it. A domain property.
A search property covering every version of the address, rather than one exact form of it. That removes this entire class of problem and is worth setting up for that reason alone.
How to check quickly. Compare the two.
Look at the address on the search property and the address on the analytics stream and confirm they describe the same thing. That is a two minute check and it resolves most cases.
Why this matters beyond linking. The search data itself.
A property on the wrong version has been under reporting your search performance the entire time, which is a bigger finding than the connection failing.
Do It During Setup
This belongs in the initial configuration alongside everything else that takes five minutes and never gets revisited. A business setting up analytics today should do this before closing the tab, because there is no natural moment later when it becomes urgent.
Why it gets postponed. Nothing breaks without it.
The two tools work perfectly well unlinked. There is no error, no prompt and no consequence, which is exactly why it sits undone for years.
What postponing costs. The habit.
Somebody who has to open two tools to answer one question generally opens neither. The connection makes a monthly review slightly easier, which is what keeps it happening.
Where it fits in the order. After verification.
Set up analytics, install it, verify the search property, then link them. Doing it in that order avoids the access problem in block four entirely.
What to do if you are years in. Do it anyway.
It applies going forward and it takes the same five minutes. There is no penalty for having waited beyond the reporting you did not have.
What to look at first once linked. Your best pages.
Take the pages that produce enquiries and read the searches bringing people to them. Our guide to organic traffic covers what to do with that. Everything sits on the Google Analytics guide.
One tool stops
at the click.
The other
starts there.
Linking them lets you look at a single page and see both the searches that brought people to it and what they did once they arrived. Nothing breaks without it, which is exactly why it sits undone for years on properties that are otherwise perfectly well configured.
What we check when we join them up:
If your search property was set up on an old version of your address, it has been under reporting you the whole time.
Every guide.
One tool.
Getting it installed and configured properly, reading the reports without being misled, measuring outcomes rather than activity, the advanced reporting and what to do when the numbers look wrong.
