Google explains how to identify Search traffic in analytics and logs

Use Google’s new referrer documentation to compare Search Console clicks, landing-page requests, and analytics sessions.

Sonar compares three records of arrivals at the same doorway.

Google published a guide on November 12 explaining how to identify traffic from Google Search in analytics and server logs. The HTTP Referer header can show that a landing-page request came from a Google origin. The same origin can also appear on clicks from Discover or Google Images. Search terms are absent from the header. Google’s traffic identification guide

Compare three counts for one landing page

Pick a page with steady search traffic and a complete seven-day period. Export its Google Search Console clicks for that period. In your edge or server logs, count document requests to the landing page with a recognized Google origin or the documented Android Google app referrer. Exclude requests for images and scripts. In analytics, pull sessions that began on the same page and were classified as Google organic. Align dates and time zones, and check whether your reports use the same URL version.

The counts describe different events. Search Console records an organic click. Logs capture requests that reach the logging layer. Analytics records sessions according to its own tracking and classification rules. Record which layer supplied the logs because an origin-only log can miss pages served by a cache.

Use the gap to decide what to inspect

If Search Console clicks hold steady and logged arrivals are still visible, but analytics sessions drop after a consent banner change, check whether the analytics tag fires after consent. If requests move to another URL after a migration, follow the redirect chain and compare the initial request with the final landing page. These are diagnostic examples. Each needs a controlled browser test or log inspection to confirm the cause.

Keep known paid traffic separate using your campaign data. Label any remaining referrer-only count as Google-origin landing requests because the header cannot reliably separate Google surfaces. For AI assistants that send their own referrers, use the GA4 guide to AI search referrals.

Keep learning

Continue this topic

Community discussion

Discuss: Google explains how to identify Search traffic in analytics and logs

Have a question, a useful example, or a different perspective? Join the discussion, share evidence, and help other readers reach a better answer.

0 replies Moderated
No replies yet.

Be the first to ask a focused question, share a practical example, or add useful evidence.

Ask a question or join the discussion

Share evidence, a useful example, or a clear question. Be specific, stay on topic, and challenge ideas without attacking people. First-time replies may be held for moderation.