Google Discover data

Google Discover reporting has natural variability. Google expects differences between Search Console and other tools. Google’s processes data in Pacific Time, delivers it in one-day batches and considers it preliminary for two days. These factors make it unlikely for Discover data to line up neatly with analytics based on different time zones or processing rules.

Clicks vs. page views

A Discover click reflects a tap in Google’s feed. A page view reflects what happens once the visitor reaches your site. Immediate bounces, reloads, redirects, consent screens, and recirculation will always create divergence between the two. Because they capture different stages of the visit, Discover clicks and on-site pageviews won’t ever map 1:1.

What to expect

This feature is designed to show which posts are appearing in Discover, how prominently they’re being surfaced, and the patterns behind that visibility. A core aim is to surface this activity in real time so teams can take advantage of the opportunity while it’s happening. It’s not intended to produce precise numeric agreement with on-site analytics. Therefore, our 9% discrepancy tolerance for other analytics platforms vs. Parse.ly does not apply here; Discover traffic behaves differently and varies widely across publishers, devices, and regions.

Ongoing accuracy improvements

We continue to refine the model as Google’s inputs evolve. Over time, the relationship between click-based signals and on-site behavior will continue to stabilize but unlikely to achieve parity.

Calibration with Google Search Console data

Starting in July 2026, Parse.ly will re-calibrate our distribution of historical Google Search and Discover data. A separate project will address improvements to recent data (for the past 3 days). See the product update for more information.

The calibration optimizes for article-level accuracy: for each article on each day, the adjusted split between Google Search and Google Discover closely matches the split GSC reports for that article. Site-level aggregate totals may still differ from GSC because Parse.ly measures page views and GSC measures clicks, which capture different stages of a visit (see the clicks vs. page views section above).