Is Google Really Sending You Traffic? How to Identify Google Search Visits in Analytics and Server Logs

Search Console says Google sent your website thousands of clicks last month. Your analytics shows far fewer organic sessions. Your developer's server logs tell a third story. Which one is right?

If you've ever sat in a monthly review trying to explain why the numbers don't match, you're not alone. It's one of the most common questions business owners ask their SEO team.

On 12 November 2026, Google published a new Search Central page that answers part of that question directly: Identify Google Search traffic in your web analytics or server logs. It explains exactly what Google Search sends when someone clicks through to your site, why that signal is sometimes missing and why your tools will never match perfectly.

This guide turns Google's documentation into practical checks you can run on your own website.

Quick answer: When someone clicks a Google Search result, the browser usually sends an HTTP Referer header containing only Google's domain, such as https://www.google.com/ or a local domain like https://www.google.co.in/, without the search query. Most analytics tools use that to label the visit as organic search. Visits from Google can still show up as direct or referral when the Referer is blocked by privacy settings, removed by your own redirects or reclassified by your analytics settings. Search Console counts clicks; analytics counts page loads that run the tracking code, so the numbers won't match one to one.

What Google's new documentation says

Google sends only the domain, never the query

Google says Google Search uses the "origin" referrer policy. That means the Referer header contains only the scheme and host, such as https://www.google.com/, and not the page path or any query parameters. The search query is never included. To see which queries bring people to your site, Google points you to the Performance report in Search Console.

The Referer values to look for

Google lists these values by source:

1. Google Search on the web: https://www.google.com/ or a local Google domain, such as https://www.google.co.uk/ (for India, that's typically https://www.google.co.in/).
2. Google app on Android: android-app://com.google.android.googlequicksearchbox/https/www.google.com when the app opens the link in a browser tab, or https://www.google.com/ (or a local Google domain).
3. Google app on iOS: https://www.google.com/ or a local Google domain.

Google adds that Discover traffic uses the same values as the surface where the person viewed Discover, and that other Google services served from the same origins, such as Google Images, send the same values.

That Android app value matters. If your custom reports or log scripts only look for values starting with "https://", they will miss it.

Why the Referer is sometimes blank

Even with Google's policy, the browser or operating system may drop the Referer for privacy reasons. Google lists common cases:

1. Private browsing and anti-fingerprinting protections
2. Opening search results in a new tab, in some browsers
3. Moving from a native mobile search widget to an external browser
4. Privacy extensions or strict browser settings

JavaScript-based tracking can also miss visits because of privacy settings, consent choices and ad blockers. When a visit arrives with no Referer, most tools count it as direct.

Key takeaways

1. Google Search sends only its domain as the Referer, never the search query.
2. Look for Google web domains and the Android Google app value.
3. Blank Referers are normal; they usually show up as direct traffic.

Why Google traffic shows up as direct or referral

Some of the causes are outside your control. Several are on your own website, and those are worth fixing.

Redirects on your site

Google says client-side redirects, such as JavaScript or meta refresh redirects, may replace the Referer with your own page's URL. So a visitor from Google can look like they came from your own site. Redirects that don't keep the query string drop parameters such as gclid, used for Google Ads tagging. And a redirect that sends a stricter Referrer-Policy header can remove the Referer entirely.

If you've recently redesigned or moved your website, check this first. Our guide to 301, 302, 307 and 308 redirects explains why server-side redirects are the safer choice.

Analytics settings that reclassify Google

Google notes that most analytics systems recognise these Referer values automatically. If Google traffic is missing, or appears as referral or direct, check for:

1. Custom channel rules that put google.com or google.co.in into the wrong group
2. Referral exclusions (sometimes called unwanted referrals) that accidentally include Google domains
3. Filters that remove traffic from certain hostnames or countries
4. A tracking tag missing from some templates, such as landing pages, blog posts or a separate booking site

Counting the wrong requests in server logs

When a page loads, the browser also fetches images, CSS and JavaScript files. For those requests, the Referer is your own page's URL, not Google. Google's advice is to count only requests for the landing pages themselves.

Why analytics and Search Console will never match exactly

This is the conversation every marketing team has eventually. Google's documentation lists the main technical reasons:

1. Different measurements: Search Console records a click when someone selects your result in Google Search. Analytics records a session only after the page loads and the tracking code runs. If the page is slow, or the visitor leaves before it loads, there's a click but no session.
2. Privacy and consent: browser settings, extensions, ad blockers and consent choices can block analytics scripts or strip the Referer.
3. Redirects: client-side redirects and lost query strings change how visits are attributed.
4. Paid vs organic: Search Console only reports organic clicks. Your analytics may include Google Ads traffic depending on how it's set up.

Google's separate guide on using Search Console and Google Analytics together adds more differences. Search Console reports on the canonical URL, while analytics reports any URL with the tag. Search Console includes non-HTML pages like PDFs. And Google Analytics automatically excludes known bots, while Search Console doesn't necessarily filter them out. Google recommends comparing Search Console clicks with Analytics sessions, as they're the most comparable metrics.

The practical rule: use Search Console for queries, impressions and clicks from Google Search, and use analytics for what visitors do after they arrive. Look at trends in both, not identical totals.

A practical checklist to find your real Google traffic

Here's the checklist we use when a client's organic numbers look wrong.

1. Compare trends, not totals

Put Search Console clicks and analytics organic sessions for the same pages and dates side by side. If both rise and fall together, your tracking is broadly fine. If one drops sharply while the other doesn't, investigate.

2. Check that every page has the tag

Open your key landing pages, blog posts and booking pages and confirm the analytics tag fires. Template changes, new landing page builders and separate booking or payment domains are common gaps.

3. Review channel rules and exclusions

Look for Google domains in referral exclusions, custom channel groups and filters. Make sure google.co.in and the Android Google app value are treated as organic search, not referral.

4. Audit redirects

Test old URLs, campaign URLs and your home page with a redirect checker. Replace JavaScript and meta refresh redirects with server-side 301 or 308 redirects where possible, and make sure redirects keep query strings so gclid and UTM parameters survive.

5. Check your Referrer-Policy header

If your site or redirect sends a very strict Referrer-Policy, it can strip the Referer on the way through. Ask your developer to review the header on redirects and key pages.

6. Analyse server logs properly

If you use logs, filter for requests to HTML landing pages only, match the Referer against Google's listed values and ignore image, CSS and JavaScript requests. Remember that Googlebot crawling your pages is not a visitor. Google explains how to verify Googlebot so you don't confuse crawls with real visits.

7. Watch for direct traffic spikes

A sudden rise in direct traffic at the same time as a fall in organic traffic often points to a tracking or redirect change, not a real loss of Google visitors. Check what changed on the site that week.

Key takeaways

1. Compare Search Console clicks with analytics sessions as trends, not exact totals.
2. Fix tag gaps, channel rules and client-side redirects first.
3. In logs, count only landing page requests and don't treat Googlebot as visitors.

What this means for hospitals, clinics and local businesses

For a hospital or clinic, a "drop in Google traffic" can trigger panic and rushed changes. Before anyone rewrites service pages or cuts the SEO budget, check the tracking. Patients often search on phones inside the Google app, open results in new tabs or use privacy settings, all of which can push visits into direct.

The numbers that matter most are still appointments, calls and enquiries. If organic sessions dip but bookings from your website hold steady, the problem may be measurement, not visibility. Our guide to tracking AI Max traffic in Google Ads covers the paid side of the same measurement challenge.

How Pengwin Solutions helps

We provide SEO services and website development for businesses across India, including hospitals and clinics. For measurement problems like these, we offer:

1. Tracking audits: checking tags, channel rules, exclusions and consent settings across your site
2. Redirect and header reviews: finding client-side redirects, lost query strings and strict Referrer-Policy headers
3. Log analysis: separating real Google visits from crawlers and asset requests
4. Clear reporting: a monthly SEO report that connects Search Console, analytics and real enquiries

Frequently asked questions

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

Check the HTTP Referer. Google Search sends only its domain, such as https://www.google.com/ or a local domain like https://www.google.co.in/, and the Android Google app can send an android-app value. Most analytics tools use this to label the visit as organic search.

Does the Referer show the keyword someone searched?

No. Google Search uses the origin referrer policy, so the Referer contains only the scheme and host, without the path or query. To see the search queries that bring people to your site, use the Performance report in Google Search Console.

Why is my Google traffic showing as direct?

The browser may drop the Referer because of private browsing, privacy extensions, opening results in new tabs or moving from a search widget to a browser. Client-side redirects on your site and analytics settings such as referral exclusions can also hide Google as the source.

Why don't Google Analytics and Search Console numbers match?

They measure different things. Search Console counts clicks in Google Search, while analytics counts sessions after the page loads and the tag runs. Consent choices, ad blockers, redirects, canonical URLs and paid traffic settings also cause differences.

Should I count Googlebot visits in my server logs as traffic?

No. Googlebot requests are crawls, not visitors. Verify Googlebot using Google's documented method, and count only landing page requests from real browsers whose Referer matches Google's listed values.

Can redirects affect my Google traffic data?

Yes. Google says JavaScript and meta refresh redirects may replace the Referer with your own URL, redirects that drop the query string lose parameters like gclid, and a stricter Referrer-Policy on a redirect can remove the Referer completely.

Get a clear picture of your Google traffic

Call +91 90326 18332, email hello@pengwinsolutions.com, or contact Pengwin Solutions for an SEO and tracking audit that shows how much traffic Google really sends you, and what it's worth in enquiries.