Search Console and Google Analytics are usually opened for different reasons: one to see how a site appears in Google, the other to see what visitors do. Used together they can say more about where a site’s search opportunity lies than either does alone, but only if the limits of each are respected when the numbers are set side by side. This article covers what Google says about each tool, what it says about combining them, and our own reading of how that helps with understanding a market. It complements our piece on what the Performance report can and cannot tell you; we do not repeat how its numbers are counted.
Two tools, two halves of the visit
Google’s guide to using Search Console and Google Analytics data for SEO divides the work cleanly. Search Console provides data about how a site performs in Google Search: impressions, clicks and the queries that bring people to it. Google describes it as focusing on activity before a person arrives. Google Analytics provides data about visitors’ interactions with the site, such as the pages they visit, how long they stay and what actions they take, and where the audience comes from across channels such as email, referrals, social platforms, paid search and organic search.
Google’s overview of Search Console adds that it also covers crawling, indexing problems and which sites link to yours. The guide states the split as a rule of thumb: the source of truth for search performance is Search Console, and for behaviour inside the site it is Google Analytics.
Clicks and sessions: the pair Google says to compare
Google says comparing Search Console performance data with Analytics organic traffic is particularly helpful when attributing conversions, such as transactions, newsletter sign-ups or lead forms, to Google Search traffic. It also says plainly that the tools use different metrics and systems, so the data will not match completely. To see the general pattern, it recommends focusing on the two most comparable metrics: Search Console clicks and Analytics sessions.
Google’s dashboard template, built in Looker Studio, filters Analytics to sessions where the source is google and the medium is organic. It also advises choosing the same country and device filters in both tools, so that mobile in Australia in one is compared with mobile in Australia in the other. For per-query joins by country, device or landing page, it points to Search Console bulk exports and the Analytics BigQuery export, or to the blending feature in Looker Studio.
Reasons the numbers diverge, and which ones you can fix
Google’s guidance on discrepancies is practical. A small difference can be ignored, because the systems are different. What matters is that the general trends follow the same pattern. A big difference is worth investigating, and Google lists the common reasons while admitting that some cannot be debugged effectively because of how the systems work:
- Implementation. Analytics depends on a tag, so a missing tag on some pages, or other configuration problems, affects the data. Search Console data is processed uniformly by Google, so site configuration affects it less.
- Consent. If users opt out of tracking, Analytics data can be skewed.
- Timezone. Analytics lets you choose one; Search Console reports in Pacific Time.
- Attribution. Search Console counts every click in Google Search, while Analytics offers three attribution models.
- Canonical URLs. Search Console reports on the canonical URL, while Analytics reports any URL that carries the tracking code, so URL counts are likely to be higher in Analytics.
- Traffic breakdowns and file types. Search Console splits traffic into web, image, video, news and Discover, and includes non-HTML pages such as PDFs if they are shown or clicked, which Analytics may not measure.
- Bots. Analytics excludes known bots automatically, while Search Console does not necessarily filter them.
Of these, the implementation, consent and file-type items are the ones a site owner can act on. The rest are properties of the tools. Our reading is that this separation turns “the numbers disagree” into a short list of known causes to rule in or out.
Reading demand and gaps from the combined picture
Google’s guide is about monitoring traffic, not sizing opportunity, so what follows is our reading, not Google’s advice.
Search Console tells you which queries and pages a site already appears for, and how often those appearances turn into clicks. Google’s Performance report help says the report can show which queries bring traffic and which pages have the highest and lowest click-through rate. Google’s combined-data guide describes clicks and click-through rate as showing whether search snippets are persuading people to click. Applied to a market view, in our reading, pages with many impressions and a low click-through rate mark searches where the site is visible but not persuasive.
Analytics adds what happens next. Google points to its Landing page report, filtered to Google organic sessions, as a way to see how useful a page is to organic traffic and how well it drives engagement and conversions. In our reading, a page that attracts clicks but loses visitors immediately has a different problem from a page that attracts few clicks, and the market conclusions differ: one is a content or intent mismatch, the other a visibility gap.
Google’s definitions of impressions, position and clicks add two cautions. Position is the topmost position a link held, averaged across queries, and it is recorded only when a link gets an impression. Data is also attributed to the canonical URL Google selects.
What neither tool can show about the market
Both tools describe a site that already exists in search. Search Console reports only where the site appeared, and Google notes that a query in the list may not show the site if you run it yourself, because results depend on the time, place, device and recent history of the searcher. Analytics reports only visits that arrived. Neither shows demand the site has never been shown for, who else holds those results, or how hard they would be to enter.
Google has no documentation page on competitor analysis or on sizing a search opportunity that we could find, so nothing about those is attributed to it here. Our view, labelled as such, is that the combined data is best treated as a record of what the site has earned so far, and the questions about the rest of the market need other evidence, stated as such.
Where this fits at Cultured Digital: starting a strategy from what the data can and cannot say
Our SEO Strategy work begins by finding where the opportunity actually is, and the first group in its scope, Understand the market, covers search opportunity analysis, competitor analysis, and keyword research and search intent. We weigh how many people search, how hard the results are to enter and what the site is able to do about it, because demand alone is not an opportunity. Measurement is its own group in the same scope, covered in the Measure guide: measurement design and reporting that answers business questions.
We do not promise rankings or traffic numbers. We set out the opportunity and the evidence, and measure against it, and part of that is saying what is known, and what is not.