Google explains how to find search traffic in Analytics and logs

Google explains how to find search traffic in Analytics and logs
3 min read

Google has published a page on its Search Central documentation listing the HTTP Referer header values sent when a user clicks on a link from Google Search leading to another site. Presented as new in Google’s update log, it explains how publishers can identify and track this traffic in their analytics tools.

The same values are also sent by Discover and Google Images, according to the page. A visit reported with the referrer google.com therefore indicates that Google sent the user, without specifying whether it came from Search, Discover, or Images.

The values sent

Google Search applies the “origin” referrer policy: only the scheme and host of the originating page appear in the header. Neither the page path, query parameters, nor the search query itself are transmitted, and the page refers to the Search Console Performance report for queries.

On the web, Google Search sends either https://www.google.com/, or one of many local domains, such as https://www.google.co.uk/. The Google app on iOS sends the same value. On Android, it can send these options or android-app://com.google.android.googlequicksearchbox/https/www.google.com when the link opens in a browser tab.

According to the page, Discover traffic carries the values of the surface where it was viewed, “such as the Google app or Google Search on the web.” In February 2021, Google began routing Discover traffic on Chrome through the google.com referrer instead of googleapis.com, to match that of Discover in the Google app.

Why the numbers differ from Search Console

A visit from Google Search can arrive without a referrer. According to the page, the browser or operating system may remove this header for privacy reasons, in private browsing, when opening in a new tab depending on the browser, or when switching from a mobile search widget to an external browser.

When this traffic appears in analytics software, it is typically classified as organic traffic from Google Search. If it is classified as Referral or Direct, custom channels, referrer exclusions, or filters may have reclassified it.

The page recommends counting only queries to landing pages, and not images, CSS, and JavaScript files, which also carry the page URL as a referrer. Client-side redirects can replace the referrer with the site’s URL. A redirect that removes the query string eliminates parameters like gclid, commonly used in ad tagging, and a redirect with a stricter Referrer-Policy header can remove the referrer.

Search Console records a click as soon as a link is selected, while an analytics tool only counts a visit after the page loads and the tracking script executes. This script can be blocked by ad blockers, consent choices, or privacy settings. Search Console only tracks organic clicks, while analytics totals may include Google Ads traffic depending on the site’s configuration.

What changes for publishers

To separate Discover clicks from Search clicks, the page indicates using the Discover report in Search Console rather than referrer data. Its last update was on November 12 and does not cover AI Mode or AI Overviews. The standard Performance report counts clicks in these two categories, with no appearance type to distinguish them.

If paid landing pages are redirected, the redirects must preserve the query string, as losing a gclid is another gap noted by the page. As of November 13, it does not mention the google.com/goto redirect links present in search results, which DataForSEO dates to late August. Any potential revision would appear in Google’s update log.

S’abonner
Notification pour
guest

0 Commentaires
Le plus ancien
Le plus récent Le plus populaire
0
Nous aimerions avoir votre avis, veuillez laisser un commentaire.x