The Discover performance report in Google Search Console shows how many times your pages appeared in Google Discover (impressions), how many times people tapped them (clicks) and the click-through rate, broken down by page, country, date and Discover appearance. Most people read it like the Search report. That is the mistake. Discover has no queries and no positions, and its traffic arrives in spikes rather than steady lines. Read it as a log of which topics caught interest and when that interest faded, not as a rankings dashboard.
What the Report Shows and Where to Find It
Open Search Console, choose your property, and look under Performance in the left menu. If your site has enough Discover visibility, you will see a “Discover” entry next to “Search results”. The default view shows total clicks and impressions for the last three months, and you can extend the date filter back up to 16 months. Google’s Discover documentation on Search Central says the report covers content that appeared in Discover in that 16-month window, includes traffic from Chrome, and “fully tracks a site’s Discover traffic across all surfaces where users interact with Discover.”
That matters because your analytics tool is not a complete Discover record. GA4’s default channel group list, as documented in Analytics Help, has no Discover channel, so Discover visits are folded into other channels. When the two disagree, treat the Discover performance report as the record and GA4 as the place to see what those visitors did next. The guide to GA4 channel groupings explains how GA4 sorts traffic.
Why the Report Is Missing or Looks Thin
Search Console Help states that the report appears only once your property reaches a minimum number of Discover impressions. Google does not publish that number. A missing Discover entry almost always means low volume, not a broken setup or a verification problem. Check three things before assuming anything else:
- Property scope. Metrics are credited to the canonical URL. If your canonicals point to another domain or protocol variant, the data lands in that property, not the one you are looking at.
- Eligibility. Per Google’s Discover documentation, pages must be indexed and meet Discover’s content policies. No special markup is required, but eligibility is not a guarantee of appearing.
- Images. Google recommends large images at least 1,200 px wide, enabled with the
max-image-preview:largerobots setting (or AMP). Our Meta Robots Tag Generator writes the tag correctly.
If those check out, you don’t have enough Discover exposure yet. The Google Discover explainer covers how the feed picks content.
How Discover Counts Impressions, Clicks and CTR
The definitions are specific and they shape how you should read every number. These come from Search Console Help:
| Metric | How Google counts it | How to read it |
|---|---|---|
| Impressions | Counted when the card is scrolled into view, either as a standard card or in a carousel. | Reach. How often Discover chose to show you to someone. Not a measure of demand. |
| Discover clicks | Counted when the user opens the item. Sharing or other actions do not count as a click. | Traffic actually delivered to your site. |
| Average CTR | Clicks divided by impressions. | How well the card (image plus headline) earned the tap. |
For Web Stories, the impression is counted for the story viewed in Discover. Read the three numbers as a set, never alone.
Dimensions and the Filters Worth Using
The report has four dimensions: Page (the canonical URL), Country, Dates and Discover appearance. There is no query or position, because nobody typed anything, and no device dimension.
Discover appearance splits traffic into AMP articles, News Showcase, Web Story and Videos. For most sites this tab is near-empty, which confirms the traffic comes from standard article cards. The filters that earn their keep:
- Date granularity. Daily, weekly or monthly. Weekly or monthly smooths the spikes. The 24-hour view shows hourly data in your browser’s local time, the right lens for a post spiking right now.
- Compare. You can compare two date ranges or two countries, but only one comparison at a time.
- Custom (regex) page filter. Uses RE2 syntax and is case-insensitive by default. Filtering by folder (say
/recipes/) shows which content type Discover favours on your site.
Discover CTR Is Not Search CTR
In search results, an impression means someone asked a question and your page was listed. In Discover, an impression means a card scrolled past someone who was not looking for you. Expect Discover CTR to behave differently from search CTR, and never benchmark one against the other or against CTR curves built for search rankings.
The only fair comparison for Discover CTR is your own pages against each other, in the same country and appearance type, over similar windows. A page with high impressions and weak CTR is telling you the topic got picked but the card didn’t persuade. That is usually the image or the headline, both of which you control. Run headline variants through the Headline Analyzer and check how the share image crops in the Open Graph Preview before publishing. Neither is a Discover preview, just a cheap check on the two elements your card is built from.
A Five-Pass Routine for Reading the Report
Most guides stop at “filter by page.” This routine answers the questions that matter: what worked, why, for how long, and what next.
- Pass 1, the shape. Set 16 months, monthly granularity. Is Discover a steady line, a series of isolated spikes, or a cliff? A cliff that lines up with a dated Google update needs a different response than a slow fade.
- Pass 2, the winners. Switch to the Pages tab, sort by clicks for the last three months. Write down the top 10 to 20 pages and their topics.
- Pass 3, the lifespan. Click into each winner and switch to daily. Note how long it earned impressions after it first appeared. You will usually see news-style pages that light up for a few days and evergreen pages that resurface repeatedly. That split shows which kind of content Discover rewards on your site.
- Pass 4, the card. For winners with weak CTR relative to your other winners, review the lead image and headline.
- Pass 5, the hit rate. Count how many pages you published in the last quarter, then how many appear in the Discover table at all. This ratio tracks whether your topic selection is improving, and it swings far less than total clicks.
Worked Example: Diagnosing a Discover Drop
Take a hypothetical food blog whose weekly Discover clicks fall by roughly half over a month.
First, compare the last 28 days to the previous 28 days and open the Pages tab with the comparison on. The drop is concentrated: two seasonal recipe pages that drove most of last month’s Discover clicks have gone quiet while the rest of the site is flat. That is lifecycle, not a penalty.
Second, filter by country. A drop limited to one country points to a market-level change. Google’s February 2026 Discover core update, for instance, launched for English-language users in the US first, so check the Search Central blog before touching anything.
Third, check whether newer posts earned any Discover rows at all. If last quarter’s hit rate held up, the site is fine and simply needs its next seasonal batch. If newer posts are missing entirely, look at what changed on the template: images, robots directives, canonicals. The traffic drop diagnosis guide walks through the wider version of this process.
Reading Common Patterns
| What you see | Likely cause | What to check |
|---|---|---|
| Report missing entirely | Below Google’s impression threshold | Canonical property, eligibility, large-image setting |
| High impressions, low CTR on one page | Topic was picked, the card wasn’t persuasive | Lead image crop, headline clarity |
| Sudden site-wide drop on a known date | Google update or policy issue | Search Central blog, Manual actions report |
| Gradual fade, same top pages | Normal lifecycle of spiking content | Hit rate of newer posts |
| Newer posts never appear | Template change (images, robots, canonicals) | Crawl the template, compare before and after |
| Chart total higher than table total | Row thresholds and the 1,000-row table cap | Nothing is broken. Use the API for full rows |
For the template checks, SEO Rocket’s real-crawler technical audit (Screaming Frog-backed, with JavaScript rendering) surfaces canonical mismatches, redirect chains and broken links across the whole site in one pass. Those quietly scatter Discover credit across URLs. You can spot-check a single URL with the free Canonical Tag Checker.
Data Limits, and How to Get Past 1,000 Rows
Search Console Help lists the limits behind most “the numbers don’t add up” complaints:
- Row thresholds. A page row appears only if it meets a minimum impression threshold. Below-threshold data still counts toward site totals, which is why the chart can exceed the table.
- 1,000-row table. The UI table shows at most 1,000 rows.
- Canonical credit. Duplicate URLs show zero clicks and impressions. If a parameterised or syndicated version is chosen as canonical, its stats go there.
- Pacific Time. Daily data is grouped in Pacific Time, except the 24-hour view, which uses your browser’s local time. GA4 uses whatever reporting time zone you set, so daily totals can differ between the two.
- Preliminary data. Today’s and sometimes yesterday’s data is provisional and shown as a dotted line. Data usually lands within two to three days.
If you publish at volume, the interface is a sample. The Search Console API’s Search Analytics query method accepts type set to discover, returns up to 25,000 rows per request, and lets you page through further results with startRow. Google notes it returns top rows, not guaranteed every row. Bulk Data Export to BigQuery also carries the Discover appearance fields (Web Story, video, AMP), except News Showcase, which Google says is not supported there.
The other payoff is history. The report holds 16 months, so comparing this November with the November two years ago means storing the data yourself; a monthly page-by-day export into a sheet is enough. The Search Console performance report guide covers the equivalent approach for search data.
The Separate Generative AI Report for Discover
Search Console Help now documents a second report: the generative AI performance report for Discover. It shows how your site performs in generative AI features inside Discover, and its help page says that, as of August 31, 2026, these insights have been rolled out to all websites worldwide.
The only metric it documents is impressions: links to your site that users saw in those AI features, counted once per result per session. Clicks are not mentioned. Use it as a visibility signal, then check the main Discover performance report for clicks to the same pages.
Turning Discover Winners Into Durable Traffic
The highest-value use of the Discover performance report is not chasing the next spike. It is spotting topics with proven interest, then building search demand around them, because search traffic does not evaporate when a feed moves on. Google’s own Discover documentation calls Discover traffic “less predictable or dependable” than keyword-driven visits and advises treating it as supplemental.
Take your Pass 2 winners and run their topics through SEO Rocket’s keyword research, which uses real Ahrefs data for volumes, difficulty and intent, to find the evergreen queries sitting next to each spike. Then brief the follow-up pages in the article writer, whose validation gates check length, title and meta limits before anything ships. This is the same playbook proven across 1,000,000+ ranking pages: use the volatile channel to learn what resonates, and the stable channel to keep it. The Discover optimization guide covers the content side in depth.
FAQ
Why don’t I have a Discover report in Search Console?
The report appears only after your property passes a minimum number of Discover impressions. Google does not publish the threshold. It usually means low Discover exposure, not a setup error.
How far back does Discover data go?
Up to 16 months. The default view is the last three months.
Can I see which queries triggered Discover impressions?
No. Discover is not query-driven, so the report has no query or position data. Group by page and country instead.
Does the Discover performance report include Chrome?
Yes. Google’s Discover documentation says the report includes traffic from Chrome and tracks Discover across all surfaces where users interact with it.
