Why does Google not provide any Discover data in Analytics?

Why is this lack of data in Analytics a problem?

The reality is harsh: Google Discover does not send any metrics to Google Analytics. No identifiable traffic source, no dedicated custom dimension. Everything that comes through Discover remains invisible in the interface most SEO teams use daily to monitor their performance.

This silence is not trivial. It forces a fragmented traffic analysis: on one side, Search Console for Discover, on the other, Analytics for everything else. It is impossible to know whether a Discover user converted, how long they stayed on the site, or if they bounced immediately. This results in a complete analytical blind spot on a channel that can generate millions of clicks.

What metrics remain accessible in Search Console?

Google limits access to three basic indicators in the Performance > Discover tab of Search Console. Clicks indicate how many users actually visited your site from a Discover carousel. Impressions measure how many times your content appeared in a user's feed. The CTR simply divides clicks by impressions.

These three metrics hardly suffice to detect an abnormal visibility variation. But they do not allow understanding why an article performs or collapses. No reliable device type segmentation, no demographic data, no conversion path. Search Console remains a detection tool, not a strategic analysis tool.

Can we bypass this limitation with workarounds?

Some practitioners attempt to inject custom UTM parameters into indexed URLs to trace Discover in Analytics. The problem: Google does not guarantee that these parameters will be retained when displayed in the feed. Others use scripts to cross-reference timestamps from Search Console with those from Analytics, but accuracy remains approximate.

Server-side tracking could theoretically identify a typical Discover user behavior pattern — short session, high bounce rate, no prior search. But this remains fragile reverse engineering that requires technical resources that few teams can sustainably mobilize.

• No Discover referral source exists natively in Google Analytics
• The only available data is found in Search Console: clicks, impressions, CTR
• It is impossible to cross-reference Discover with behavioral or conversion segments in Analytics
• Workarounds (UTM, server tracking) remain fragile and not guaranteed by Google
• This fragmentation forces juggling between two distinct tools to analyze performance

Is this statement consistent with observed practices on the ground?

Yes, and that's precisely what is frustrating. Teams managing high-traffic editorial sites have noticed this since the product's launch: no reliable trace in Analytics. Traffic often appears as 'Direct' or '(not set)', which completely skews attribution reports. Some observe a spike in sessions without identifiable source exactly when Search Console shows a Discover peak.

Let's be honest: this situation probably suits Google. By isolating Discover in Search Console, they avoid direct comparisons to classic Search in Analytics. Marketing teams cannot easily demonstrate that Discover converts less or generates lower engagement. [To be verified]: there is no official communication explaining this technical choice.

What nuances should be added to this statement?

John Mueller speaks of a 'specific referral source,' which leaves the door open for future evolution. But after several years of stagnation, one must be realistic: Google has no urgency to integrate Discover into Analytics. The product remains experimental in some countries, and advertising monetization takes precedence over analytical transparency.

Another nuance: some sites see Discover traffic appearing under 'google.com / referral' in Analytics, but this is inconsistent and often mixed with other Google sources. One cannot build reliable reporting on such an ambiguous category. The advice remains the same: consider Search Console as the only source of truth for Discover.

In what cases does this rule not apply?

If you are using a complete proprietary analytics stack — server tracking, user-agent parsing, correlation with server logs — you could theoretically isolate part of the Discover traffic. But it's advanced tinkering that requires technical infrastructure only large publishers possess. And even then, accuracy remains lower than what Google could provide natively.

For the majority of sites, the rule applies without exception: no Discover in Analytics, period. Therefore, it is necessary to adapt reporting processes by manually exporting Search Console data and cross-referencing it with Analytics metrics using scripts or dashboards like Looker Studio. It's time-consuming, but it's the only viable option.

What should you concretely do to track Discover correctly?

First step: connect Search Console to Looker Studio (formerly Data Studio) to automate Discover data exports. This allows you to create dashboards that aggregate clicks, impressions, and CTR over custom periods. Without this automation, you will waste a lot of time manually exporting CSV files each week.

Second step: set alerts in Search Console to be notified in case of a sudden drop or spike in Discover impressions. Discover traffic is extremely volatile — an article can generate 500,000 impressions in 48 hours and then completely disappear. An alert lets you react quickly if Google suddenly removes content from its feed.

What errors should be avoided in analyzing Discover data?

Never directly compare Discover and Search performance in Search Console. The two channels have radically different distribution logic: Discover proactively pushes content, Search responds to explicit intention. A CTR of 2% is excellent in Search but mediocre in Discover, where users scroll passively.

Also, avoid overinterpreting daily variations. Discover operates on unpredictable algorithmic waves: an article can explode on a Tuesday and collapse the next day for no apparent reason. Focus on weekly or monthly trends, not on 24-hour fluctuations that often mean nothing.

How to check if your site is eligible for Discover?

First, ensure you meet the minimum technical criteria: large images (at least 1200px wide), AMP optional but recommended, fresh and frequently updated content. If you see no data in the Discover tab of Search Console after several weeks, it's likely that Google does not consider your content eligible.

Then, test the perceived quality: Discover favors authority sites with high E-E-A-T. If your domain is new or little known, it will be nearly impossible to appear in the feed. Conversely, if you are an established media outlet with identified authors and daily updates, you have a real chance of capturing significant Discover traffic.

• Connect Search Console to Looker Studio to automate Discover reports
• Set alerts for sudden variations in impressions in Search Console
• Never directly compare Discover and Search CTRs — the logic is incomparable
• Analyze weekly trends rather than daily fluctuations
• Check technical criteria: large images, fresh content, high E-E-A-T
• Accept volatility as a constant of Discover — no guaranteed stability