Google Discover referrer
Google Discover is a personalised mobile content feed, separate from search results. Visits it drives can arrive with a google.com referrer or, from the Google app, with the referrer reduced or absent, making Discover hard to isolate in analytics. Google Search Console reports Discover performance directly, and is the authoritative source.
Discover is a feed, not search
Google Discover surfaces content in a personalised mobile feed rather than in response to a typed query. A tap from Discover can send a google.com referrer that looks like organic search, or — when it opens inside the Google app — arrive with the referrer reduced or absent.
Because of this overlap, analytics referrers alone cannot reliably separate Discover from ordinary Google organic traffic.
- Discover is a personalised feed, not a query result
- Referrer can resemble google.com search or be reduced
- Analytics struggles to isolate Discover
Search Console is the source of truth
Google Search Console provides a dedicated Discover performance report showing impressions and clicks from Discover specifically. For understanding Discover, treat Search Console — not the analytics referrer — as authoritative, just as you would for organic search queries.
How it appears in analytics and logs
A Discover-driven visit may carry a google.com referrer indistinguishable from search, or arrive from the Google app with a reduced referrer. Analytics alone struggles to isolate Discover; Search Console reports it as its own channel.
Diagnostic use case
Recognise why Discover traffic is hard to separate from search referrers, and use Search Console's Discover report as the source of truth.
What WebmasterID can help detect
WebmasterID records the referrer when sent and normalises google.com, but does not invent a Discover label where the signal is ambiguous; it points to Search Console's Discover report for authoritative Discover data.
Common mistakes
- Trying to isolate Discover from the analytics referrer alone.
- Assuming a google.com referrer is always classic search, never Discover.
- Ignoring Search Console's dedicated Discover report.
Privacy and accuracy notes
The referrer is browser-controlled; its absence from the app is normal, not a failure. WebmasterID reads the referrer when present and never re-identifies a visitor when it is missing.
Related pages
- Google organic search referrer
Visits from Google organic search arrive with a google.com referrer, but the query string no longer carries the keyword: Google moved organic search behind HTTPS and reports keyword '(not provided)'. To see which queries drove clicks, Google Search Console is the authoritative source, not the analytics referrer.
- Google News referrer
Google News drives traffic from its news.google.com web surface and from the Google News mobile app. Web clicks commonly pass a news.google.com referrer, while app opens can reduce or omit it. Recognising the app-versus-web split is key to attributing Google News traffic correctly.
- AI search analytics
See how Google surfaces, including feeds, reach your pages.
Sources and verification notes
- Google — Discover performance report (Search Console)Search Console reports Discover as its own channel.
- MDN — Referrer-Policy
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.