Reference guide · search-console · Published 2026-08-16 · 3 min read
Google Discover versus Search explained
Google Discover versus Search explained: interest-based feed, no queries, eligibility signals, and why standard SEO advice does not apply.
- ·Feed, not a query
- ·What gets in
- ·Measuring it in GSC
A feed, not a query
Google Search answers a question someone typed: a query triggers a ranked list. Google Discover, by contrast, is an interest-based feed shown to a user who has expressed no query, a topic or news stream Google assembles from their history, apps, and activity. There is no search box and no ranking against a keyword.
That single difference changes how you should think about the content that reaches each surface. A page that performs in Search does not automatically surface in Discover, and the Discover report in Search Console is where you would see any of it. This page explains the mechanics behind their separate rows.
The eligibility signals
Google does not publish a fixed formula for Discover, but the practical signals are consistent.
| Requirement | What it means in practice |
|---|---|
Indexable and not anti-noindex | The page must be crawlable and indexable, the same baseline as search |
| Followed and not blocked | Discover favours pages that respect noindex and other directives |
| High quality and original | Thin, scraped, or clickbait-style pages rarely surface |
| Timely and topical | Fresh, relevant content tracks better than evergreen reference |
| Compelling and robust visuals | Large, descriptive hero images are a known Discover strength |
A page designed around a keyword title and a keyword URL is built for Search. A Discover-friendly page is built to be immediately interesting when someone sees it with no query, which usually means a strong story or strong imagery, not a colourless "how to choose X" page.
Click behaviour matters, and returns are uneven
In Search, clicks are responses to a ranked query, ranging from informational to transactional. In Discover, the user is scanning a feed and taps only what grabs them, so the interaction is skewed toward news, sport, entertainment, and visual content. Traffic can also be "in-and-out": high impressions with a low click-through rate because the headline did not earn the tap, or a spike that fades before it would ever rank in Search.
Because there are no queries, there is no "query filtering" to segment Discover traffic, and it does not appear in the performance report's web search results; it has its own filter and its own report. A site that targets serious, keyword-led, transactional intent should treat Discover as a bonus and not rework its content around the feed.
Measuring it without guessing
The Discover report in Search Console shows impressions, clicks, and CTR per page for the Discover surface. The honest check for any content:
- Confirm the page earns Discover impressions at all, the report will tell you over a few weeks.
- Look at click behavior, not just impressions; a Discover impression with no click is not a win.
- Compare the same content in Search. If it ranks and converts in queries but never surfaces in the feed, that is normal and does not indicate a fault.
Discover is part of Google's surfaces, but it runs by its own rules. Get the search-crawling and indexing baseline right, then treat the feed as an extra channel whose performance you measure separately, never as a replacement for search rankings.