Why do the numbers from Analytics, Search Console, and My Business never match?

Why do these tools display different data even though they all belong to Google?

The three platforms operate on distinct technical architectures with radically different business objectives. Search Console analyzes the behavior of Googlebot and pre-click interactions in SERPs. Analytics measures user sessions post-click, using a JavaScript script that requires a full browser. My Business, meanwhile, aggregates local engagement metrics (calls, directions, profile views) that have no equivalent in the other two tools.

This divergence is not a bug—it's a logical consequence of incompatible methodologies. Search Console counts impressions even if the user never clicks. Analytics only sees complete visits where the tag fires. My Business records actions that sometimes generate no website visits. Wanting to align these numbers is like comparing apples, oranges, and tractor tires.

What are the concrete methodological differences between these three tools?

Search Console is based on Google's server logs. Every request that triggers an impression is recorded, even if the user scrolls without clicking. The CTR calculated here reflects a SERP → site conversion rate, not an engagement metric.

Analytics operates through a client-side JavaScript tag. If a browser blocks scripts, if the user exits before the full load, or if the page crashes—no session is recorded. Visitors with ad blockers, anti-tracking extensions, or browsers set to strict mode simply disappear from the stats. In some tech-savvy audience segments, the gap can reach 15 to 25 % of invisible traffic.

My Business compiles offsite interactions: direct calls from the listing, GPS directions requests, photo views, messages. These actions trigger no measurable web visits in Analytics. A restaurant may have 500 My Business views and 50 clicks to the site—the two metrics measure completely different intentions.

Do these gaps invalidate the usefulness of these tools for SEO management?

No, but it requires segmenting the analysis by tool without seeking perfect reconciliation. Search Console remains the go-to tool for technical diagnostics: crawling, indexing, traffic-generating queries. It is the only reliable source for measuring actual impressions in SERPs and identifying opportunities for position gains.

Analytics is used for conversion management: bounce rate, session duration, user journeys, goals. Search Console data feeds into content strategy and ranking; Analytics measures whether that traffic converts. My Business manages local visibility and proximity engagement—a completely separate metric universe.

• Each tool measures a different stage of the funnel: SERP visibility (Search Console), site engagement (Analytics), local actions (My Business)
• The collection methodologies are intentionally incompatible: server logs vs JavaScript tags vs third-party interactions
• A gap of 10-30 % between Search Console and Analytics is structurally normal based on technical configurations and audiences
• Trying to reconcile these numbers line by line is a waste of time—the key is to understand what each source measures
• For client reporting, clarifying these differences prevents misunderstandings about traffic volumes and false alarms of sharp drops

Does this explanation hold up against real-world observations?

Yes, and it's even underestimated. On sites with high mobile or tech audiences, the gap between Analytics and Search Console can explode. Modern browsers with integrated tracking prevention (Safari ITP, Firefox ETP, Brave) block or severely limit third-party tags. We regularly observe sites with 20-35 % of invisible organic traffic in Analytics while Search Console records it accurately.

The problem complicates over multi-domain sites or those with redirects. Search Console attributes the click to the final domain after redirection, while Analytics may attribute it to the intermediate domain if the tag fires beforehand. HTTPS to HTTP email campaigns often break the referrer—Analytics classifies it as direct, Search Console as organic. Result: discrepancies that seem absurd but are technically coherent.

Why doesn't Google provide automatic reconciliation?

Because it would make no methodological sense. Reconciliation would imply diluting the accuracy of one tool or the other to force an artificial alignment. Search Console would lose its ability to measure pre-click impressions, Analytics would distort actual sessions. Google's product teams deliberately maintain this separation to preserve metric integrity.

What's missing is a clear educational documentation explaining the sources of discrepancies on a case-by-case basis. Help pages exist but remain cryptic for a non-technical person. A comparative table of methodology / use cases / known limits would be infinitely more useful than a clumsy reconciliation tool. [To be verified]: Some claim Google is testing unified views internally, but nothing has officially leaked.

In what cases do these discrepancies become suspicious and warrant investigation?

A gap of 10-30 % is normal. Beyond 40-50 %, or if the gap changes abruptly, there is probably a technical issue. Frequent causes: poorly implemented Analytics tag (dodgy asynchronous triggering, double tagging, tag absent on some pages), incorrectly configured Search Console filter (HTTP vs HTTPS property), 302 redirection instead of 301 breaking attribution.

Another red flag: Search Console shows clicks while Analytics sees no corresponding organic sessions. This can signal a tracking problem (tag absent, JavaScript blocked on the server, overly restrictive CSP), or a bot scraping phenomenon that appears as organic traffic in Search Console but is blocked before reaching Analytics. In this case, cross-referencing with raw server logs becomes essential.

What should be done when a client reports conflicting numbers?

First, never promise that the numbers will align. Clearly explain that Search Console and Analytics measure different stages of the user journey. Use a simple metaphor: Search Console counts people who see the storefront, Analytics counts those who walk through the door and stay long enough to trigger the sensor. Both metrics are true; they just do not measure the same thing.

Next, identify the source of truth for each KPI. Visibility and positions: Search Console. Conversions and engagement: Analytics. Local reputation: My Business. If the client wants a single number for "SEO traffic," prioritize Search Console for raw organic clicks and Analytics for traffic that converts. Document this choice in reporting to avoid re-evaluations every three months.

How can we audit the reliability of these three sources on a given site?

The first step: ensure that the Search Console properties adequately cover all variants of the site (HTTP/HTTPS, www/non-www, mobile version if separately hosted). A missing property = invisible clicks. Also verify that the XML sitemap is declared correctly and that coverage data is being reported accurately.

On the Analytics side, test the tag triggering on a representative sample of pages with an ad blocker disabled, then enabled. If the tag doesn't fire, it’s likely that the code is poorly placed (in an iframe, after a blocked script, conditioned by poorly managed cookie consent). Check the view filters as well: a filter that's too broad or poorly configured bot filtering can mask real traffic.

For My Business, make sure the listing is verified and up to date. My Business statistics only come in for validated listings. If there are multiple listings for the same entity (unmerged duplicates), the data fragments and becomes unusable. An audit of local listings is essential before any serious analysis.

What interpretation errors should be absolutely avoided?

Never use Search Console impressions as a proxy for Analytics traffic. An impression is meaningless until it turns into a click, and even less so into an engaged session. A site can have 100,000 impressions and 500 clicks—if the CTR is disastrous, that’s the signal to optimize the meta descriptions and titles, not to rejoice over the volume of impressions.

Avoid panicking if Analytics shows fewer sessions than the clicks from Search Console. This is mathematically normal as soon as part of the audience blocks JavaScript or exits before the page fully loads. The gap only becomes suspicious if it exceeds 40-50 %, or if it changes abruptly without an identified technical reason.

• Document in reporting which source is authoritative for which KPI (visibility = Search Console, conversions = Analytics)
• Verify that all domain variants (HTTP/HTTPS, www/non-www) are properly declared in Search Console
• Test the Analytics tag triggering with and without ad blocker on a sample of pages
• Audit the Analytics filters and bot filtering to ensure they are not masking real traffic
• Merge duplicate My Business listings to centralize local statistics
• Cross-reference with raw server logs if the Search Console / Analytics discrepancy exceeds 50 % without a technical explanation