Reference guide · search-console · Published 2026-08-16 · 4 min read
Reading the Search Console Discover report
Reading the Search Console Discover report: what the feed metrics mean, why there is no query dimension, and how to report on page and country.
- ·What Discover measures
- ·The five groupings
- ·Common mistakes
What Discover measures
The Discover report in Search Console shows how your site performs in Google Discover, the interest feed in the Google app and on Android. It lists, page by page, the clicks and impressions your content earns in that feed. Discover is a different product from search: a result appears because of the topics and interests a user follows, not as an answer to a typed query, and eligibility is governed by Discover's content policies. On the report, that difference shows up as a page and country centric view with no query dimension: you cannot ask Google which keywords produced the clicks.
The report only appears once a property has reached a minimum number of Discover impressions, so a quieter site simply will not have the tab. The default window is the last three months, and you can change it. When the property is eligible, the report shows total clicks and impressions, and you can group the data by page, country, appearance type, or day.
The five groupings
Group the table with the same small set of dimensions used across the performance report:
| Dimension | What grouping by it tells you |
|---|---|
| Page | Which pages earned the clicks and impressions, assigned to the canonical like everywhere else |
| Country | Which markets the feed audience came from |
| Type | Which Discover entry type produced the result |
| Date | How the feed traffic trends within your date range, daily or weekly |
Filters behave the same way: date, page, and country filters appear next to the existing filters, and you can compare two groups, for example impressions from two countries in the same range. The report shares the standard console logic, so the comparison controls work as in the performance report.
The load-bearing difference
The structural fact that trips most people is that the Discover report has no query dimension. There is no keyword breakdown because Discover is not query driven, there is nothing to rank for in the traditional sense, and the report is a content level measure, not a keyword one. The report groups by page, country, type, and date only.
The absence of a query dimension is not a limitation in the dashboard; it is the accurate model of how the feed works. Discover matches content to interests, so to understand it, look at the page and country groupings and compare them against search performance instead of hunting for a keyword list.
Common mistakes
Looking for a keyword breakdown
There is none, and the report is not broken. If you are used to the search term coverage view in search performance, remember the feed does not have queries at all.
Reading single small rows
One page can earn an impression plus a 0% or 100% CTR from one row. A single tiny row is statistically meaningless; read the page and country big rows over a range, not a one row spike.
Judging after a bursty week
Discover is famously bursty, one heavily shared article can dominate a week. Compare three to six month totals before concluding anything.
How to act
- Open the report and set the date range to a meaningful long window (three to six months).
- Group by page, sort by clicks, and list the top five earned pages.
- For each page, identify the topic and the country it won at.
- Compare with search performance. A page that wins in both channels argues for writing more on that theme, while a page that only wins Discover argues for a faster production loop on its topic.
The report only tells you what the feed noticed; it does not say why a page floated. Decide whether the page earned impressions because of topic fit, helpfulness, or pure timing, and treat the tab as a measuring stick for content, not as a puzzle box.
Prevention
Review Discover content on a monthly cadence rather than reacting to spikes, and keep the top page cohort short so week to week changes stay visible in the report. Bragging rights only arrive after the page itself is genuinely useful, so fix the content and the experience first, then let the report confirm the improvement.