Identify Google Search Traffic in Analytics: A Singapore Guide

Identify Google Search Traffic in Analytics: A Singapore Guide

Identify Google Search Traffic in Analytics: A Singapore Guide

Identify Google Search Traffic in Analytics: A Singapore Guide

Identify Google Search Traffic in Analytics: A Singapore Guide

Illustration of an analytics chart beside a Google Search referral source label.

Google published official guidance on 12 November 2026 on how to identify Google Search traffic in analytics. In an entry dated 12 November 2026 on the Latest Google Search documentation updates page, Google says: “Added a new page about identifying traffic from Google Search using HTTP Referer headers.” The reason given is: “To document how site owners can identify and track traffic from Google Search in their web analytics systems.”

The official documentation, last updated 2026-11-12 UTC, is a measurement guide for Singapore consumer brands who compare Google Analytics, or another analytics tool, with Search Console, and who wonder why the figures differ. It is not a ranking update, not the November 2026 core update, and not a server-log tutorial.

What the new page covers, and what the Referer header cannot tell you

Google says that, in addition to Search Console, you can identify traffic from Google Search in your own analytics or server logs by inspecting the HTTP Referer header sent when someone clicks a Google Search link to your site. Referer is the official name of that header, and this article keeps that spelling.

Google says: “The Referer header doesn’t include the search query that the user entered. To see which queries bring users to your site, use the Performance report in Search Console.” It also notes that it uses an origin referrer policy, so the header contains only the scheme and host of the referring page, not the URL path or the query parameters.

Our recommendation: use Search Console for queries, and use the official Referer values to see how those visits are classified in analytics, rather than expecting the header to reveal the search terms.

The official Referer values

For Google Search on the web, Google lists https://www.google.com/ or a local Google domain, such as https://www.google.co.uk/ or https://www.google.co.jp/. Those are the official local-domain examples. Local Google domains are included, and a Singapore property should check its own domain in analytics against that official list.

For the Google app on Android, Google lists an android-app value when the app opens the link in a browser tab, or https://www.google.com/ (or a local Google domain). For the Google app on iOS, it lists https://www.google.com/ (or a local Google domain).

Google also says: “Traffic from Discover uses the same values as the surface where the user viewed Discover, such as the Google app or Google Search on the web.” And: “Other Google services that are served from the same origins (for example, Google Images) send the same Referer values, so this traffic is also included when you match these patterns.” A Referer match therefore does not separate Google Images from Search.

The header can be blank in official cases such as private browsing, some new tabs, a move from a native mobile search widget to an external browser, or privacy extensions and strict browser settings. JavaScript-based tracking may also miss visits because of privacy settings, consent choices or ad blockers.

Our recommendation: match your analytics against the official Referer list, including any local Google domain that appears in your own data, and do not invent extra values.

What to check if Search traffic is missing, or shows as referral or direct

Most analytics tools already treat these official values as organic Google Search traffic. Google says: “If Google Search traffic is missing or shows up as referral or direct traffic, check whether custom channel rules, referral exclusions, or filters in your analytics configuration are reclassifying it.”

If you also look at server logs, keep that check short: count landing-page requests only, not requests for images, CSS or JavaScript, because those can carry your own page URL as the Referer. Google says: “To count visits from Google Search, only look at requests for the landing pages themselves.” This is not a logging tutorial.

Our recommendation: if Google Search traffic is missing, or appears as referral or direct, start with those configuration checks, rather than treating the gap as a traffic loss.

Why analytics often will not match Search Console 1:1

Google says: “Identifying Search traffic on your site using the Referer header isn’t exact, and the data recorded in your web analytics system or server logs often doesn’t match 1:1 with the clicks reported in Search Console.”

The official reasons are technical, not a ranking report. Privacy settings, extensions, ad blockers or user consent choices can block analytics scripts, strip URL query parameters, or suppress the HTTP Referer header. Redirects on your site, including client-side or meta refresh redirects, may replace the Referer with your own page URL. Redirects that do not keep the query string can drop URL parameters such as gclid, and a redirect that sends a stricter Referrer-Policy header can also remove the Referer. The two systems also measure different events: Search Console records a click when a user selects a link in Google Search, whereas analytics records a visit or session only after the destination page loads and the tracking code runs. Search Console reports only organic clicks from Google Search and does not include clicks on Google Ads, whereas analytics might include paid traffic, depending on how you configure it.

For the broader question of why marketing numbers can differ across tools, see our guide to why marketing numbers can differ. This article stays with Google’s official Search-specific list.

A gap between the two reports is not, on its own, evidence that rankings dropped. Official guidance does not promise that changing a channel rule or a redirect will bring the totals together.

Our recommendation: treat a difference as a measurement issue to check against the official reasons, not as proof that rankings fell.

A practical 90-day check

Compare the same period in Search Console and in analytics. Check custom channel rules, referral exclusions and filters. Inspect redirects on key landing pages, including whether query parameters are kept and whether a stricter Referrer-Policy is sent. Keep organic Google Search separate from paid Google Ads in the analytics view you use for the comparison.

Set one performance target around completing that measurement check, not around a promised change in the two totals.

We are planning to fold this kind of Search-and-analytics check into Growth System 90, our 90-day planning approach, so the official Referer guidance is reviewed alongside SEO work.

In practice: pick one period, run the checks above, and record how organic Search is classified in analytics. For wider SEO support in Singapore, see our SEO service page.

Hypothetical illustration, not a client example: a Singapore skincare brand notices that Search Console clicks are higher than Google organic sessions in analytics for the same dates. The team checks channel rules and a client-side redirect on the campaign landing page, and does not treat the gap as a ranking loss.

FAQs

How can I identify Google Search traffic in my analytics?

In addition to Search Console, Google’s 12 November 2026 documentation says you can identify that traffic by inspecting the HTTP Referer header sent when someone clicks a Google Search link to your site. Most analytics tools already treat the official values as organic Google Search. If the traffic is missing, or shows as referral or direct, check custom channel rules, referral exclusions, or filters.

Why don’t my analytics numbers match Search Console clicks?

Google says identifying Search traffic from the Referer header is not exact, and analytics or log data often will not match Search Console clicks 1:1. Official reasons include privacy settings, redirects, different measurement methods, and the fact that Search Console counts organic Search clicks only, not Google Ads clicks.

What Referer values does Google Search use?

For Search on the web, Google lists https://www.google.com/ or a local Google domain, and gives examples such as https://www.google.co.uk/ and https://www.google.co.jp/. It also lists values for the Google app on Android and iOS. Use the official list rather than inventing a Singapore domain example.

Does this include Google Discover or Google Images?

Google says Discover traffic uses the same Referer values as the surface where the user viewed Discover, such as the Google app or Google Search on the web. Other Google services served from the same origins, including Google Images, send the same values, so those visits are also included when you match the patterns.

Does a gap between analytics and Search Console mean my rankings dropped?

No. Google frames these gaps as a measurement issue, not as a ranking report. A difference can come from privacy settings, redirects, tracking that only fires after the page loads, or paid traffic being mixed into an analytics total. It is not, on its own, evidence that a core update or a ranking change caused the gap.

Can I see the search query from the Referer header?

No. Google says the Referer header does not include the search query. To see which queries bring users to your site, use the Performance report in Search Console.