Marketing Strategy7 min read

How to Identify Google Search Traffic in Your Analytics (and Why It Never Matches Search Console)

On November 12, 2026, Google published a page explaining exactly what a click from Google Search looks like when it reaches your website. Here is what that means for a service business trying to tell which calls, forms, and booked jobs actually started on Google.

Brian Pierce

Brian Pierce

Coastal Solutions Media Team

Service business owner comparing website analytics with Google Search Console data

How Do You Identify Google Search Traffic on Your Website?

You identify Google Search traffic by the HTTP Referer header the browser sends when someone clicks a Google result. Google sends only the domain, such as https://www.google.com/ or a country domain like google.co.uk. Most analytics tools file those visits under organic search automatically. The search query itself is never included.

That definition comes straight from a page Google added to its Search Central documentation on November 12, 2026, titled "Identify Google Search traffic in your web analytics or server logs." It is a short, technical page, but it answers a question service business owners ask us constantly: why does my analytics say one thing, Search Console say another, and my phone say something else entirely?

What Does a Google Search Visit Look Like?

Google Search uses what is called an origin referrer policy. In plain terms, when someone clicks through to your site, the browser tells your site which domain they came from, and nothing more. No path, no query parameters, no keywords.

Google lists these values by source:

Where the click happenedReferer value your site receives
Google Search on the webhttps://www.google.com/ or a local Google domain, such as https://www.google.co.uk/
Google app on Androidandroid-app://com.google.android.googlequicksearchbox/https/www.google.com when the app opens the link in a browser tab, otherwise the google.com value
Google app on iOShttps://www.google.com/ or a local Google domain

Google also notes that Discover traffic uses the same values as the surface where the person was reading Discover, and that other services served from the same domains, Google Images for example, send the same values. So "came from google.com" covers more than the ten blue links.

Google's page does not list a separate referrer value for AI Overviews or AI Mode. Based on that list, there is no documented way to separate a visit from a link in an AI answer from any other Google Search click in your own analytics. To see how often your pages appear in those features, use the Search Console generative AI performance report, which counts impressions by page.

Why Does Some Google Traffic Show Up as Direct?

Even though Google sends a referrer, the visitor's browser or operating system can drop it before it reaches you. Google names several common cases:

  • Private browsing modes and anti-fingerprinting protections
  • Opening a search result in a new tab, in some browsers
  • Moving from a native mobile search widget to an external browser
  • Privacy extensions or strict browser settings

When the referrer is missing, most analytics tools have nothing to go on and record the visit as direct. That is why a service business with a healthy Google presence can still see a large direct number. Some of those people typed your address. Some came from Google and simply arrived without a label.

On top of that, Google points out that JavaScript-based tracking may not record every visit at all, because of browser privacy settings, consent banners, and ad blockers. If a visitor declines analytics cookies or blocks the script, that session may never appear in your reports, no matter where it came from.

Why Don't Analytics and Search Console Numbers Match?

Search Console and your analytics measure different events, so they will not agree. Search Console records a click the moment someone selects your result on Google. Analytics records a session only after your page loads and the tracking code runs. Privacy tools, redirects, and paid traffic widen the gap further.

Google lists the main technical reasons:

  • Privacy settings and client configurations. Extensions, ad blockers, and consent choices can block the analytics script or strip the referrer.
  • Redirects on your site. A JavaScript or meta refresh redirect can replace the Google referrer with your own page's address. Redirects that drop the query string also drop ad parameters such as gclid. A redirect that sends a stricter Referrer-Policy header can remove the referrer entirely.
  • Different measurement methods. A click that never finishes loading, because the visitor hit back or lost signal, is a Search Console click with no analytics session.
  • Paid versus organic. Search Console reports only organic clicks from Google Search. Your analytics may include Google Ads traffic in its totals, depending on configuration.

Google's companion guide on Analytics and Search Console says the two most comparable numbers are Search Console clicks and Analytics sessions, and it recommends watching the general pattern rather than expecting a one-to-one match. If clicks rise and organic sessions rise with them, the story is consistent. If clicks rise and sessions fall, look for a tracking or redirect problem.

What Should a Service Business Check First?

Most analytics platforms recognize Google's referrer values on their own, so if organic search looks strangely low, the cause is usually in your setup rather than in Google. Google specifically calls out custom channel rules, referral exclusions, and filters that reclassify Google visits as referral or direct.

A practical checklist for a local service company:

  1. Review channel rules and filters. Make sure nobody added a rule years ago that lumps google.com into a custom "referral" group, or a filter that excludes it.
  2. Look for client-side redirects. Old landing pages that bounce visitors to a new URL with JavaScript can erase the Google referrer. Server-side 301 redirects, which this site and most modern platforms use, are the cleaner choice.
  3. Check your consent banner. If analytics only loads after consent, expect organic sessions to undercount, and do not panic when they do.
  4. Count landing pages, not assets, in server logs. Google notes that when a browser loads your images, CSS, and scripts, it sends your own page as the referrer. Only the request for the page itself carries the Google value.
  5. Use Search Console for queries. The referrer never contains the search term. Google says to use the Search Console Performance report to see which queries bring people to your site.

If any of that sounds unfamiliar, it is the kind of plumbing our SEO, AEO, and GEO service and local SEO service check before reporting a single number.

Where Analytics Stops: Calls, Profiles, and Booked Jobs

Here is the part that matters most for plumbers, roofers, HVAC companies, med spas, and every other business where the customer picks up the phone. A large share of Google-driven demand never becomes a website session at all.

  • Calls from your Google Business Profile. Someone taps Call on your profile and the conversation starts without your website loading. Your profile's own performance data is the place to see those actions. Our Google Business Profile optimization guide covers what to watch there.
  • Calls after a site visit. A visitor reads your service page, then dials the number from memory or from the truck wrap they saw last week. Analytics sees a session with no conversion.
  • Visits that arrive unlabeled. As above, privacy tools can strip the referrer, so the lead looks like direct traffic.

That is why we tell owners not to judge search by analytics alone. The more reliable record is the lead itself. When every call, form, and text lands in a CRM pipeline with its landing page, any UTM tags, and a simple "how did you hear about us?" answer, you can see which booked jobs started on Google, even when the analytics trail goes cold. Many businesses also add UTM parameters to the website link on their Google Business Profile so those visits are separated from regular organic results in analytics. It is not required, but it makes reporting cleaner.

The other half is responding fast. A Google visitor who calls while your crew is on a job and hears voicemail is a lost lead that no report will ever show. Missed-call text back or an AI receptionist keeps that conversation alive, and logs the source while it does.

A Simple Monthly Routine

You do not need a data team. Once a month:

  1. Note Search Console clicks and impressions for the month, plus generative AI impressions as a separate line.
  2. Note organic search sessions in your analytics. Compare the trend with Search Console clicks, not the exact number.
  3. Glance at direct traffic. A sudden jump with a matching drop in organic often means a tracking or redirect change, not a real shift in behavior.
  4. Pull leads and booked jobs by source from your CRM. This is the number that pays the bills.
  5. Write down anything you changed on the site that month so next month's comparison has context.

The generative AI report guide linked above also covers non-Google sources, such as visits from ChatGPT, which belong in the same routine as a separate line.

Getting Started

Google's new page will not change your rankings. It does remove some guesswork about what a Google visit is and why your reports disagree. If you want someone to check your analytics setup, redirects, and lead source tracking end to end, you can request a free growth audit.

Common questions

Frequently asked questions

How can I tell if a website visit came from Google Search?

Check the HTTP Referer header. Google says clicks from Google Search on the web send https://www.google.com/ or a local Google domain, and the Google app on Android can send an android-app:// value. Most analytics tools recognize these automatically and classify the visit as organic search.

Does the referrer show which keyword someone searched?

No. Google Search uses an origin referrer policy, so the Referer header contains only the scheme and host, with no page path or query. Google says to use the Search Console Performance report to see which queries bring people to your site.

Why does my Google traffic show up as direct in analytics?

Browsers and operating systems sometimes remove the referrer for privacy. Google lists private browsing, anti-fingerprinting protections, some new-tab behavior, moving from a mobile search widget to a browser, and privacy extensions. Custom channel rules or filters in your analytics can also reclassify Google visits.

Why are my Search Console clicks higher than my analytics sessions?

They measure different events. Search Console counts a click when someone selects your result, while analytics records a session only after the page loads and tracking code runs. Ad blockers, consent choices, client-side redirects, and visitors who leave before the page loads all widen the gap.

Can I see AI Overviews traffic separately in Google Analytics?

Google’s documentation does not list a separate referrer value for AI Overviews or AI Mode, so those visits look like other Google Search clicks in analytics. The Search Console generative AI performance report shows how often your pages appeared in those features, counted as impressions.

What is the best way for a service business to track leads from Google?

Record the source on the lead itself. Store the landing page, any UTM parameters, and a how-did-you-hear-about-us answer for every call, form, and text in your CRM. Analytics misses phone calls from your Google Business Profile and unlabeled visits, but the lead record does not.