📱 What is Google Discover and how do you optimise for it? (Direct answer)
Google Discover is a proactive content feed on the Google app and mobile browser homepage that surfaces articles, guides, and videos to users without a search query. It is driven by a user's interest graph — built from search history, YouTube watch history, and app activity — rather than keyword intent. To optimise for it: ensure all pages pass Core Web Vitals on mobile, set max-image-preview:large in your robots meta tag, use images at least 1200px wide as hero images, build topical authority on clearly defined subject clusters, and maintain strong E-E-A-T signals (author bylines, credentials, cited sources). There is no direct opt-in; Discover eligibility is earned through quality and page experience signals.
📱 The Google Discover Eligibility Framework
Googlebot
(no crawl block)
Web Vitals
(mobile field data)
+ max-image-
preview:large
and topic
authority
user interest
graph
All five layers must be satisfied for consistent Discover appearances. Missing any single layer — particularly large images or Core Web Vitals — dramatically reduces eligibility regardless of content quality.
Why You Can Trust This Guide
This is the complete guide to Google Discover optimisation — from eligibility factors to image requirements to E-E-A-T. For related deep dives:
- Core Web Vitals (required for Discover): Site Speed & Core Web Vitals Guide →
- E-E-A-T signals that drive Discover eligibility: E-E-A-T & Brand Authority Guide →
- SERP features overview: SERP Features & Zero-Click Searches Guide →
- AI Overview and GEO: GEO & AEO Guide →
1. What Is Google Discover?
Google Discover is a personalised content feed that surfaces articles, videos, and web pages to users without a search query. It appears on the homepage of the Google app (Android and iOS), the mobile browser homepage at google.com on mobile, and as a dedicated swipe-left feed on Android devices. Unlike every other Google product, Discover operates entirely on proactive interest matching — the user does nothing, and Google delivers content it believes they will find valuable based on their activity profile.
From a publisher's perspective, Discover represents one of the most significant organic traffic opportunities on the mobile web. A single article gaining Discover traction can deliver tens of thousands of mobile visits in a 24–48 hour window — traffic that arrives without any search ranking, without any keyword targeting, and from users who had never heard of your site before that moment. The opportunity is substantial and heavily underexploited by most SEO teams, primarily because Discover optimisation requires a different set of signals than traditional search ranking.
On Android: swipe right from the home screen on Pixel devices, or as a feed below the Google Search bar on most Android launchers. In the Google app on iOS and Android: the Discover tab at the bottom of the app. On mobile Chrome and mobile Safari: google.com shows a Discover feed below the search bar when a user is signed in. On desktop: Google Discover does not appear. Virtually all Discover traffic arrives on mobile devices — GSC Discover data consistently shows 98%+ mobile share across all 8 client sites monitored in 2025–2026.
2. How Google Discover Works — The Interest Graph
Discover is powered by what Google calls an interest graph — a user-specific model that infers topics, entities, and content types a user is likely to engage with. Unlike a social media interest graph (built from explicit follows and likes), Google's is largely implicit, assembled from:
- Google Search history — the topics and entities a user has searched for recently and historically
- YouTube watch history — channels, topics, and video types consumed on YouTube
- Web and app activity — websites visited and apps used while signed into a Google account (if Web & App Activity is enabled)
- Location history — geographic signals that surface local and region-relevant content
- Engagement feedback — whether users click and read Discover cards or scroll past, and whether they explicitly follow topics in the Google app
From a publisher standpoint, you cannot directly influence which users see your content. What you can do is ensure that when Google's algorithm matches your content to a user's interest profile, the match results in a feature: your content is indexable, passes page experience requirements, has a strong large-image signal, and demonstrates topical authority on the subject matter that triggers the match.
3. Google Discover vs Google Search — Key Differences
🔍 Google Search
- User types a query — active intent
- Keyword relevance is primary signal
- Rankings are relatively stable over time
- Traffic is predictable and forecastable
- Desktop and mobile traffic
- CTR driven by title, meta, and SERP position
- Keyword research is meaningful
- Core Web Vitals: ranking factor
📱 Google Discover
- No query — passive interest matching
- Interest graph relevance is primary signal
- Traffic spikes and drops unpredictably
- Traffic is highly volatile — not forecastable
- Almost exclusively mobile (98%+)
- CTR driven by large image and headline
- No keyword targeting — topic authority matters
- Core Web Vitals: eligibility requirement
The most important implication of this comparison: Discover is not a substitute for search traffic — it is additive. A site with strong organic search rankings from well-crafted keyword strategies can layer Discover optimisation on top and unlock a second, largely uncorrelated traffic source. Discover traffic doesn't compound or sustain the way search rankings do, but during its spikes it delivers immediate volume that search cannot replicate. Treat it as a bonus distribution channel, not a primary acquisition strategy.
4. Who Gets Traffic from Google Discover?
Not all content types benefit equally from Discover. Understanding which categories perform in the feed helps you prioritise which content to optimise and where to invest in the signals Discover requires.
| Content Type | Discover Performance | Key Signals That Help | Notes |
|---|---|---|---|
| News and current events | Highest — core Discover use case | Recency, publisher authority, large images | Spikes on breaking events; fast decay |
| Entertainment, celebrity, sport | Very high | Freshness, entity recognition, engaging headlines | High volume but low time-on-page |
| Health and wellness | High — especially evergreen | E-E-A-T, author credentials, cited research | YMYL — strict E-E-A-T requirements apply |
| Technology and gadgets | High | Recency on releases, topical depth, large images | Product launches drive spikes |
| Food, travel, lifestyle | Good — seasonal patterns | Visual quality, seasonal interest triggers | Seasonal peaks (summer travel, holiday food) |
| Finance and investment | Moderate — YMYL scrutiny | Publisher credibility, E-E-A-T, no sensationalism | Strict quality assessment; misleading content penalised |
| SEO and digital marketing | Moderate | Timely industry news, authoritative bylines | Topic authority critical — niche interest |
| B2B SaaS and technical guides | Low generally | Topic spikes when technology becomes mainstream news | Niche interest; occasional spikes on AI/tech news |
IndexCraft is not a news or lifestyle site — it publishes technical SEO and AI search guides. Conventional wisdom would suggest limited Discover potential. In Q4 2025, three articles on this site received significant Discover traffic within days of publication: the LLM.txt guide, the AI crawlers robots.txt guide, and an article on Google AI Mode. The pattern was consistent: AI and search technology articles published within 72 hours of a major Google announcement spiked in Discover — not because of direct news coverage but because Discover matched them to users who had been searching for news about those Google developments.
The lesson: even non-news sites can get Discover traffic if their content is published in topical alignment with a breaking interest event — and if the technical eligibility signals (large images, Core Web Vitals, max-image-preview:large) are already in place. Sites that fail on technical prerequisites miss these spikes entirely, even when the content is perfectly timed. — Rohit Sharma
5. Core Web Vitals and Google Discover Eligibility
Google has confirmed that Core Web Vitals are a ranking factor for Discover, just as they are for Search. Pages that fail to meet Good thresholds on mobile are less likely to appear in the feed. The critical difference from Search: for Discover, the mobile dataset is what matters — almost all Discover traffic is on mobile devices, so lab scores on desktop are largely irrelevant.
| Metric | Good Threshold | Why It Matters for Discover | Where to Check |
|---|---|---|---|
| LCP — Largest Contentful Paint | ≤ 2.5s | Discover users are mobile, on varied connections — slow LCP causes immediate bounces from the feed. Google deprioritises pages with poor LCP in Discover ranking. | GSC Core Web Vitals → Mobile; CrUX field data |
| INP — Interaction to Next Paint | ≤ 200ms | Post-click engagement signals matter. Pages where interactions are sluggish show poor experience signals that reduce future Discover eligibility. | GSC Core Web Vitals → Mobile; PageSpeed Insights |
| CLS — Cumulative Layout Shift | ≤ 0.1 | Mobile ads and dynamically loaded content frequently cause layout shifts. CLS failures in Discover content destroy trust and engagement. | GSC Core Web Vitals → Mobile; Chrome DevTools |
Of the three, LCP is the most common failure point for Discover-eligible content. This aligns with the broader web picture — per the HTTP Archive Web Almanac 2025, only 62% of mobile pages pass Good LCP. The fix pattern is the same as for traditional search: optimise the hero image (WebP, explicit dimensions, preload, no lazy-loading on LCP element) and reduce Time to First Byte. See the Site Speed & Core Web Vitals Guide for the full diagnosis and fix workflow.
6. The Image Requirement — Large Previews and max-image-preview
After Core Web Vitals, image configuration is the single highest-impact technical change available for Discover optimisation. Google's Discover cards show either a large image preview (filling most of the card width on mobile) or a small thumbnail (roughly 100×100px in a corner). The difference in click-through rate between these two presentations is substantial — across 8 client sites with GSC Discover data, large preview cards consistently generated 3–7× higher CTR than small thumbnail presentations of the same article.
This is the most commonly missed Discover optimisation. Without this directive, Google will not show large image previews for your pages — regardless of image size. Add it to every page on your site via the HTML head or HTTP response headers. This directive also affects Image Preview in Search results and Web Stories.
<!-- Method 1: HTML meta tag (simplest) --> <meta name="robots" content="index, follow, max-image-preview:large"> <!-- Method 2: If you already have a robots meta tag, add max-image-preview to it --> <meta name="robots" content="max-image-preview:large"> <!-- Method 3: HTTP response header (for pages where meta tag isn't possible) --> X-Robots-Tag: max-image-preview:large
Google's own documentation specifies 1200px minimum width for Discover large preview eligibility. The image should be representative of the article's primary topic — not a decorative illustration or a logo. Use WebP format for optimal loading speed. Serve hero images from a CDN to ensure fast delivery to mobile devices. Set explicit width and height attributes to prevent CLS.
Lazy loading defers image loading until the element is near the viewport. For the primary article hero image — which is the image Google samples for Discover preview — this can delay loading and in some cases cause Google's crawler to miss the image entirely. The hero image (and LCP element) should always load eagerly, with fetchpriority="high" set.
Hero images hosted behind authentication, served only through JavaScript without HTML fallbacks, or blocked in robots.txt will not be discoverable for Discover preview. Check that the image URL is accessible directly (test by pasting it in an incognito browser window) and appears in the page's raw HTML source — not injected by JavaScript alone.
Across two content sites with consistent Discover traffic in Q1–Q2 2026, I ran side-by-side analysis of articles that appeared in Discover with large preview images vs those appearing with small thumbnails. The data in GSC was clear: large preview cards averaged 4.2× higher CTR than small thumbnail cards across the same publication period on the same site. The difference was not random — small thumbnails consistently appeared for pages that either lacked the max-image-preview:large directive or used images under 1200px wide as the page's primary hero.
Adding max-image-preview:large to a site that had never had it generated measurable changes in the GSC Discover report within 4–6 weeks — the proportion of cards showing large previews increased substantially, and average CTR for Discover impressions improved in the corresponding period. This is the highest-ROI Discover optimisation available: a single line of HTML that requires no content changes and no design work. — Rohit Sharma
7. Content Signals That Drive Discover Visibility
Beyond technical eligibility, Discover's algorithm evaluates content quality signals to determine whether a page is worth surfacing to any users at all — and then interest-graph signals to determine which users to surface it to. The content signals map closely to Google's broader quality assessment framework but are weighted specifically for a consumption context (mobile reading without prior search intent).
📊 Google Discover Content Signal Strength — Direct GSC Analysis (8 Client Sites, 2025–2026)
Relative signal importance based on GSC Discover data analysis across 8 client sites, 2025–2026. Not algorithmic weights — observational correlations between signal presence and Discover impression volume.
8. E-E-A-T for Google Discover
Google applies its Search Quality Rater Guidelines — which include Experience, Expertise, Authoritativeness, and Trustworthiness (E-E-A-T) — to Discover content evaluation, and in some ways Discover is where E-E-A-T matters most. Unlike search, where a user explicitly chose to search for information and has at least some existing context, Discover users arrive cold — with no prior intent signal. Google therefore places higher emphasis on publisher and author credibility signals to protect users from encountering low-quality or misleading content unexpectedly.
For YMYL (Your Money Your Life) topics — health, finance, legal, safety — the E-E-A-T bar in Discover is particularly high. A personal finance article from an anonymous author on a new domain with no credible backlinks will not appear in Discover regardless of image quality or Core Web Vitals. The E-E-A-T & Brand Authority Guide covers the full signal set — here is what is specifically most impactful for Discover eligibility:
Every article that you want to appear in Discover should have a clear author byline linking to an author bio page. The bio page should describe the author's relevant expertise, professional history, and external presence (LinkedIn, published works, speaking appearances). Google's quality raters explicitly evaluate whether the content's author has the credentials to write authoritatively on the topic. Anonymous or pen-name authors on YMYL topics are a significant negative signal.
Your site should have a clearly accessible About page explaining who publishes the content, what the site covers, and how content is produced and verified. For news and current events content, Google also looks for editorial policies and correction protocols. Sites with no About page, no contact information, and no editorial transparency signals are significantly disadvantaged in Discover for YMYL topics.
Articles that cite named sources with links to primary research, official data, or verifiable expert statements consistently outperform uncited claims in Discover for health, science, and finance topics. This mirrors the citation signals that also drive AI Overview citations — the same rigour that makes content credible to AI systems also makes it credible to Discover's quality assessment. The 47-site citation study confirmed that named-source attribution is one of the strongest predictors of AI Overview inclusion; the same signal applies to Discover.
9. Topic Authority and Content Depth
Discover's algorithm appears to weight topical authority heavily — sites that publish consistently and deeply on a specific subject area are more likely to appear in Discover for that topic than sites that publish broadly across unrelated subjects. This mirrors the broader topical authority signals that drive search ranking, but in Discover's case the signal appears to function at the site level as much as at the individual article level.
The implication for content strategy: building a topical authority cluster structure — a comprehensive pillar guide supported by multiple related cluster articles — creates the density of subject coverage that signals domain expertise to Discover's algorithm. A site that has published 20 deeply researched articles on technical SEO is more likely to have new technical SEO articles surface in Discover than a site that published one technical SEO article alongside 19 unrelated pieces.
10. Freshness vs Evergreen — What Discover Actually Rewards
A common misconception: Discover is only for news. In reality, Discover surfaces both fresh and evergreen content — but through different mechanisms and with different traffic patterns.
📰 Fresh Content in Discover
- Published within hours or days of a news event
- Matched to users following related topics
- High impression spike, rapid decay (24–72 hours)
- Works best for: news, announcements, event coverage
- Requires publication speed as competitive advantage
- Highly competitive for major news events
📗 Evergreen Content in Discover
- Published previously; resurfaces during interest spikes
- Appears when user interest in the topic grows
- Lower but more sustained impressions over time
- Works best for: guides, how-tos, explainers
- Requires depth and topic authority
- Can appear repeatedly across months or years
The strategic implication: both approaches work, but they require different optimisation priorities. For fresh content: speed of publication, strong Publisher name recognition, and a consistent posting schedule that trains Discover's algorithm to trust your site's recency signals. For evergreen content: depth, E-E-A-T, and topical authority that ensures your guide resurfaces whenever interest in the topic spikes — whether from seasonal patterns, related news events, or shifting user behaviour.
A health and wellness client publishes a mix of news-adjacent content and timeless health guides. In 2025, I noticed a pattern in their GSC Discover report: a guide on sleep hygiene published in 2023 had periodic Discover impressions spikes — not tied to any publication date update, but clearly coinciding with news coverage of sleep science research. The guide itself hadn't been updated; Discover was surfacing it proactively to users whose interest graph included recent sleep health searches or related health news.
The pages that resurfaced most consistently were those with the best E-E-A-T signals: doctor-authored content with clear credential attribution, cited clinical sources, and comprehensive coverage of the topic. The pages that resurfaced least consistently were the news-driven short pieces with no author attribution and minimal cited sourcing — even when they were more recently published. Quality and credibility outlasted recency as a Discover eligibility signal. — Rohit Sharma
11. The GSC Discover Performance Report
Google Search Console provides a dedicated Discover performance report that is the primary measurement tool for any Discover optimisation work. Unlike the standard Search performance report (which shows keyword queries), the Discover report shows no query data — because there are no queries. What it does show is:
In Google Search Console, click Performance in the left sidebar. At the top of the Performance dashboard, look for tabs labelled "Search results," "Discover," and "Google News." Click Discover. If the tab is greyed out or shows "Not enough data to show," your site has not yet received enough Discover traffic to trigger reporting. Sites typically need at least several hundred impressions before data appears.
The Discover report shows Impressions (how many times your page cards were shown in Discover feeds), Clicks (how many times users clicked through), and CTR (clicks ÷ impressions). Average position is not meaningful in Discover the same way it is in Search — focus on impressions and CTR. A high-impression, low-CTR pattern usually indicates small thumbnail images or misleading headlines. A low-impression pattern indicates eligibility or topic authority issues.
Click the Pages tab in the Discover report to see which individual articles are driving the most Discover traffic. This identifies your most Discover-compatible content — study what these pages have in common (image size, topic, E-E-A-T signals, publish date, content depth) and apply those characteristics to future articles. Also check which pages have high impressions but low CTR — these are likely showing small thumbnails and should be image-optimised.
Discover report data typically has a 2–3 day lag compared to Search data. Impressions and clicks on any given day are subject to revision as Google's reporting catches up. Don't make optimisation decisions based on single-day data — look at 28-day rolling windows for directional signal. Discover traffic is inherently volatile; a 90% day-over-day drop is normal, not a crisis. Evaluate performance by month, not by day.
12. The robots Meta Tag and Image Preview Settings
The max-image-preview robots directive is a critical but frequently misconfigured setting. It controls whether Google (and other search engines that support it) can show large image previews of your content in search results, Discover, and other Google surfaces.
| Value | Effect | Discover Impact | When to Use |
|---|---|---|---|
max-image-preview:large | Google can show the largest possible image preview | ✅ Enables large preview cards — highest CTR | Almost every page on every site. Set this globally. |
max-image-preview:standard | Default browser-determined preview size | ⚠️ May show small thumbnails — reduced CTR | Only if you have a specific reason to limit preview size. |
max-image-preview:none | No image previews shown anywhere | ❌ Discover cards appear without images — very low CTR | Only for pages with sensitive images not for public preview. |
| (directive absent) | Google uses default behaviour — typically standard | ⚠️ Likely small thumbnails — significantly reduced CTR | Never — always explicitly set this directive. |
# Method 1: HTML meta robots tag (recommended for most sites) <meta name="robots" content="index, follow, max-image-preview:large"> # Method 2: X-Robots-Tag HTTP response header X-Robots-Tag: max-image-preview:large # WordPress — add to functions.php to apply sitewide via HTTP header add_action('send_headers', function() { header('X-Robots-Tag: max-image-preview:large'); }); # Yoast SEO / Rank Math: This directive is controlled # in Settings → Search Appearance → Max image preview # Ensure it's set to "Large" not "Default" or "None" # Verify implementation: paste your URL into Google's # Rich Results Test and check the page's meta tags output
Ctrl+U) and search for "max-image-preview" to confirm what's actually being served. This conflict is surprisingly common on WordPress sites where the theme and plugin both output robots meta tags.13. Googlebot-News, Google News, and Discover — What's Connected and What Isn't
Google News and Google Discover are separate products with separate crawlers, separate eligibility criteria, and separate content pools. The confusion between them causes two common mistakes: publishers who block Googlebot-News thinking it stops Discover, and publishers who assume they need Google News publisher status to appear in Discover.
Google News
- Crawler:
Googlebot-News(separate UA) - Content: news and journalism primarily
- Eligibility: verification via Google Search Console or Publisher Center
- Block via:
User-agent: Googlebot-News / Disallow: / - Surface: news.google.com, Google News app
Google Discover
- Crawler: standard
Googlebot - Content: any topic — news, guides, entertainment
- Eligibility: earned through quality and page experience
- Block via: block standard Googlebot (also kills Search)
- Surface: Google app, Android feed, mobile.google.com
The practical consequence: if you want to opt out of Google News indexing (for editorial policy reasons, or to avoid Google News content policies) you can block Googlebot-News in robots.txt without any impact on Discover. Conversely, if you are not accepted as a Google News publisher, that has no bearing on your ability to appear in the Discover feed. They are genuinely separate pipelines using different data sources.
14. Google Discover for E-Commerce and Non-News Sites
E-commerce sites and SaaS companies are underrepresented in most Discover SEO discussions because they don't fit the "news publisher" mental model. However, they can earn Discover traffic through the same content signals — with some strategic adjustments.
For e-commerce sites, the highest Discover potential lies in content pages rather than product or category pages: buying guides, comparison articles, trend reports, and seasonal gift guides perform significantly better in Discover than transactional pages. This creates a strong content marketing case: the same articles that support e-commerce SEO by building topical authority also create Discover eligibility, delivering referral traffic to commercial pages from a non-competitive, non-keyword-driven channel.
Product pages rarely appear in Discover because they match transactional intent, not interest-based discovery. But "The 10 Best Running Shoes for Wide Feet in 2026" or "How to Choose a Running Shoe — A Complete Guide" can appear in Discover and drive users to product pages through internal links. Build content pages with the same image quality (1200px+ hero images), E-E-A-T signals (expert bylines on buying guides), and Core Web Vitals as you would for editorial content. These pages serve double duty: organic search ranking for commercial keywords AND Discover eligibility for interest-driven discovery.
15. Google Discover and AI Overviews — The Content Overlap
Google Discover and Google AI Overviews are different products with different mechanisms, but they share a common evaluation framework: both favour content that is well-structured, authoritative, clearly attributed, and backed by strong page experience signals. This means the GEO (Generative Engine Optimisation) work covered in the GEO & AEO Guide also directly supports Discover eligibility, and vice versa.
From the 47-site citation study (October 2024 – January 2025), the signals that most strongly predicted AI Overview citation inclusion — FAQ schema, named-source attribution, question-format H2 headings, direct-answer structure — also correlated with higher Discover impression volumes on the same sites. This is not a coincidence: both systems evaluate content quality through overlapping signals because both ultimately want the same thing — high-quality, trustworthy content that delivers genuine value to users.
16. Tracking Google Discover Traffic in GA4
While GSC's Discover report shows impression-level data, Google Analytics 4 provides the post-click behaviour data: how Discover visitors behave on your site compared to organic search visitors. Setting up proper tracking lets you evaluate whether Discover traffic is actually valuable or just a vanity metric.
GA4 does not automatically separate Google Discover traffic from organic search traffic — both appear under the Organic Search channel. Discover referrals arrive without a search query, so in GA4 they typically appear as sessions with no landing page keyword. To isolate Discover traffic, you need to cross-reference GSC Discover click data with GA4 landing page data for the same time period and match the URLs.
Discover traffic typically shows different engagement patterns than search traffic: higher bounce rates (users often read one article and return to the Discover feed), shorter session duration, and lower pages-per-session. This is expected behaviour — Discover users didn't navigate to your site intentionally. The meaningful metrics are: did they read the article (time on page), and did any measurable conversion action follow the visit (newsletter signup, product view, return visit). Evaluate Discover traffic by these conversion-adjusted metrics, not raw engagement rates.
For content publishers, the key GA4 metric for Discover is new user acquisition. Discover is uniquely positioned to introduce your brand to users who had never searched for you — these are net-new audience members. Track whether Discover-driven new users return (second visit rate), subscribe to newsletters, or exhibit other retention signals. A site that reliably converts Discover visitors into subscribers or returning readers is extracting compounding value from the channel.
17. Common Google Discover Mistakes to Fix
❌ Technical Mistakes
- Missing max-image-preview:large meta tag — the single most common and impactful missing configuration
- Hero images under 1200px wide — ineligible for large preview cards even with the correct meta tag
- loading="lazy" on the primary article hero image — can cause Google not to find the image
- Poor mobile Core Web Vitals (especially LCP > 2.5s) — reduces Discover eligibility and ranking
- Hero image served via JavaScript only (no HTML source) — may not be discovered by Googlebot
- Blocking Googlebot in robots.txt (prevents Discover entirely — this affects Search too)
- Hero image without explicit width/height attributes — causes CLS on load
- SEO plugin overriding max-image-preview:large with a different value — check rendered page source
❌ Content and E-E-A-T Mistakes
- Anonymous articles with no author byline — penalised especially for health, finance, and current events
- Sensational or misleading headlines that overpromise content — active penalty signal
- Thin articles under 500 words published to chase trending topics — low quality assessment
- No "About" page or publisher transparency information on the site
- YMYL content (health, finance) without cited sources or expert authorship
- Unrelated content topics mixed with your niche — dilutes topical authority signals
- Content published without a clear publication date — recency signal missing
- No internal linking between related articles — reduces topic cluster signals
18. Conclusion
Google Discover represents one of the highest-leverage, most underinvested SEO opportunities in 2026. The barrier to entry is not content quality alone — it is the intersection of technical eligibility (Core Web Vitals, image configuration) and content authority (E-E-A-T, topical depth) that most sites fail to execute together. Fix both layers simultaneously and Discover traffic becomes available; fix only one and it stays out of reach.
The single highest-ROI action available: add max-image-preview:large to your robots meta tag and verify every article's hero image is at least 1200px wide. This alone — if it changes your Discover cards from small thumbnails to large previews — can multiply Discover CTR 3–7× without changing a word of content. It takes 15 minutes to implement on most CMSs and requires no design work. Do it first.
Longer term, the Discover investment case is strong because it shares infrastructure with every other Google quality initiative. The same E-E-A-T signals that help Discover also help AI Overviews, featured snippets, and Knowledge Panel citations. The same Core Web Vitals that unlock Discover also improve search ranking. The same large images that qualify for Discover large previews also improve social sharing CTR. None of the work is Discover-exclusive — it is general quality investment that pays across every Google surface simultaneously.
max-image-preview:large to every page. (2) Ensure all hero images are 1200px+ wide with eager loading. (3) Fix any mobile Core Web Vitals failures. (4) Add clear author bylines and bio pages. (5) Build topical authority through cluster content. (6) Monitor in GSC Discover report. This sequence delivers results in roughly that order — start at the top and work down.Google Discover Optimisation Checklist
Technical Requirements (Do These First)
- max-image-preview:large set on all pages — via meta robots tag or X-Robots-Tag header
- Hero images are 1200px+ wide on all article pages
- Hero images served in HTML source (not JavaScript-only injection)
- Hero images have fetchpriority="high" and no loading="lazy"
- Explicit width and height on hero img elements to prevent CLS
- Mobile LCP passes Good threshold (≤ 2.5s in GSC field data)
- Mobile INP passes Good threshold (≤ 200ms in GSC field data)
- Mobile CLS passes Good threshold (≤ 0.1 in GSC field data)
- All article pages indexed by standard Googlebot (not blocked)
- Rendered page source confirmed — verify max-image-preview:large actually appears
- GSC Discover performance report checked — data present means Discover traffic is occurring
- If using Yoast/Rank Math: confirm image preview setting is "Large" in plugin settings
Content and E-E-A-T Requirements
- Every article has a clear author byline with a link to an author bio page
- Author bio page describes credentials, experience, and expertise in the topic
- Site has an accessible About page explaining who publishes content and how
- Articles cite named sources with links to primary research or data
- Headlines are accurate and informative — no clickbait or sensationalism
- Articles include a visible publication date and updated date
- Internal links connect related articles within topic clusters
- Content depth: articles cover topics comprehensively, not superficially
- YMYL content (health, finance): expert or doctor-authored with cited clinical sources
- Publishing cadence: consistent schedule in your niche builds recency trust signals over time
- Never publish misleading or sensational headlines — Discover penalises these actively
- Never publish thin articles (<500 words) to chase trending topics — quality threshold not met
Frequently Asked Questions
What is Google Discover and how is it different from Google Search?
Google Discover is a proactive content feed that surfaces articles, videos, and web pages based on a user's interests, search history, and browsing behaviour — without requiring a search query. It appears on the Google app homepage, the Google mobile browser homepage, and as a dedicated feed on Android. Unlike Google Search, which responds to explicit queries, Discover delivers content passively to users who haven't typed anything. Traffic from Discover is interest-driven and often highly volatile, spiking and dropping based on shifts in user interest rather than ranking position changes.
How do I check if my site is getting Google Discover traffic in Google Search Console?
In Google Search Console, go to Performance in the left sidebar. At the top of the Performance report, you will see tabs labelled "Search results," "Discover," and "Google News." Click the Discover tab to see impressions, clicks, and CTR from Discover specifically. Note that Discover data only appears if your site has received enough Discover traffic to trigger reporting — Google requires a minimum threshold before data is shown. If the tab is greyed out or shows no data, your site has not yet received meaningful Discover traffic. See the Google Search Console Guide for the full GSC walkthrough.
Does my site need to be a Google News publisher to appear in Google Discover?
No. Google Discover and Google News are separate products. Any website can appear in Discover regardless of whether it is a registered Google News publisher. News publishers have a dedicated Google News section in Discover, but the main Discover feed draws from the broader web. Blocking Googlebot-News in robots.txt prevents your content from appearing in Google News but does not prevent Discover appearances — Discover uses the standard Googlebot for indexation.
What image size does Google Discover require for large preview thumbnails?
Google recommends images of at least 1200 pixels wide for large preview thumbnails in Discover. Crucially, you must also set the max-image-preview robots meta tag to "large" — either as a meta tag in your HTML head (<meta name="robots" content="max-image-preview:large">) or as an X-Robots-Tag HTTP response header. Without this directive, Google may only show small thumbnail previews regardless of your image dimensions. Large preview images consistently generate 3–7× higher click-through rates in Discover than small thumbnails, based on GSC data across 8 client sites.
How long after publishing does content appear in Google Discover?
There is no guaranteed timeline. Content typically needs to be indexed by Google first, which can take minutes to hours for well-established sites with good crawl frequency. After indexing, Discover eligibility depends on Google's assessment of interest relevance, content quality, and page experience signals. Fresh content on trending topics can appear in Discover within hours of publication. Evergreen content may appear weeks or months later when Google determines it matches a user's emerging interest. Sites with strong topical authority and good Core Web Vitals tend to have shorter eligibility lags.
How do Core Web Vitals affect eligibility for Google Discover?
Core Web Vitals are a confirmed ranking factor for Google Discover, just as they are for Google Search. Pages that fail Good thresholds — LCP above 2.5s, INP above 200ms, or CLS above 0.1 — are deprioritised in Discover relative to pages that pass. Since virtually all Discover traffic is mobile, mobile Core Web Vitals are the relevant dataset. Check mobile field data in the Core Web Vitals report in Google Search Console, not just PageSpeed Insights lab scores. For the complete CWV fix guide, see Site Speed & Core Web Vitals Guide 2026.
Can evergreen content appear in Google Discover, or is it only for news?
Both fresh and evergreen content can appear in Google Discover. News articles and breaking content are commonly surfaced based on recency, but evergreen guides, how-to articles, and long-form resources also appear — typically when Discover identifies that a user's interest profile aligns with a topic the content covers deeply. Evergreen content in Discover often appears as a spike when a related news event drives interest in the underlying topic. A well-written guide on a topic can receive Discover traffic repeatedly over months whenever the topic becomes seasonally or situationally relevant.
Why does my Google Discover traffic fluctuate so dramatically from day to day?
Discover traffic is inherently volatile because it is interest-driven rather than query-driven. Unlike search rankings — which tend to be stable once established — Discover surfaces your content opportunistically when user interest signals align with your topic. A single article can receive tens of thousands of impressions on one day and near-zero the next. This is normal. Effective Discover strategies accept it and focus on the aggregate: total Discover impressions and clicks over rolling 28-day windows, rather than daily comparisons. Publishing consistent content that covers a specific topic deeply tends to produce more consistent Discover appearances over time.
What is the Discover interest graph and how does Google decide what to show each user?
Google Discover uses what it calls an interest graph — a user-specific model built from search history, YouTube watch history, location data, app usage, and websites visited when signed into a Google account. Google also considers implicit signals: how long users spend reading specific content types, which Discover cards they engage with versus scroll past, and whether they explicitly follow topics in the Google app. Publishers cannot directly control which users see their content. The best approach is to produce high-quality, topically authoritative content on clearly defined subjects — Discover's algorithm then matches that content to users whose interest graph aligns with the topic.
Does E-E-A-T affect visibility in Google Discover the same way it affects Search rankings?
Yes, and in some respects more directly. Google applies its Search Quality Rater Guidelines — which include E-E-A-T assessment — to Discover content evaluation. For YMYL topics (health, finance, safety, legal), E-E-A-T signals are especially heavily weighted. Practical E-E-A-T improvements that directly help Discover: clear author bylines with verifiable credentials, an author bio page with demonstrated expertise, publication dates on all content, references to primary sources, and a well-established publication history in your content niche. See the E-E-A-T & Brand Authority Guide for the complete signal set.
Can I appear in Google Discover without appearing in Google News?
Yes — these are completely separate surfaces. Google News is a dedicated news aggregator that gives preference to Google News publisher-verified outlets. Discover is a broader interest feed available to any well-indexed website. You can receive substantial Discover traffic without ever being accepted as a Google News publisher or verified media outlet. Blocking Googlebot-News in robots.txt only affects your Google News visibility — your Discover eligibility is determined by the standard Googlebot crawl and your page experience signals.
Does blocking Googlebot-News in robots.txt prevent Google Discover appearances?
No. Googlebot-News and the standard Googlebot are two separate crawler user agents. Blocking Googlebot-News (User-agent: Googlebot-News / Disallow: /) prevents your content from being included in Google News feeds but has no effect on Google Discover. Discover uses content indexed by the standard Googlebot. If you want to control Discover appearances, focus on page experience signals, image preview settings, content quality, and topical authority — not Googlebot-News rules. Conversely, blocking the standard Googlebot would affect both Search and Discover eligibility simultaneously.
📚 References & Sources
- Google Search Central — Google Discover Content Policies — Official Google documentation on eligibility requirements, content policies, image specifications, and the max-image-preview directive for Google Discover.
- Google Search Console Help — Discover Report Documentation — Official GSC documentation explaining the Discover performance report, what metrics are available, how data is collected, and minimum reporting thresholds.
- Google News Publisher Center — Discover and Google News Guidelines — Official guidelines covering the distinction between Google News and Google Discover eligibility, content requirements, and publisher policies.
- HTTP Archive Web Almanac 2025 — Core Web Vitals pass rate data (48% mobile, 62% LCP). Cited for Discover eligibility context on the proportion of mobile sites passing CWV thresholds.
- Google Search Central — Robots Meta Tag Reference — Full specification for the robots meta tag, including the max-image-preview directive values and their effects on image preview behaviour across Google surfaces.
- Rohit Sharma — GSC Discover Report Analysis, IndexCraft (2025–2026) — Direct Google Search Console Discover performance report analysis across 8 client sites. Source for the 3–7× CTR difference between large and small image preview cards, the 98%+ mobile traffic share observation, and the B2B site Discover spike pattern documented in the experience boxes.
- Rohit Sharma — AI Citation Pattern Study, IndexCraft (October 2024 – January 2025) — Proprietary 47-site citation pattern study. Cited for the correlation between AI Overview citation signals and Google Discover impression volumes — the E-E-A-T and content structure signals that predict both outcomes.
The complete E-E-A-T implementation guide — author signals, publisher credibility, topical authority, and the trust signals that drive both Discover eligibility and Google Search ranking. Essential reading for any YMYL publisher.
Read E-E-A-T guide →Core Web Vitals are a Discover eligibility requirement. The complete guide to LCP, INP, CLS diagnosis and fixes — including the LCP image optimisation workflow that directly improves Discover eligibility.
Read Site Speed & CWV guide →How Google surfaces content across SERP features — featured snippets, PAA, local packs, AI Overviews, and Discover. Understand the full landscape of non-traditional Google traffic sources.
Read SERP Features guide →The content quality signals that drive AI Overview citations are the same signals that drive Discover eligibility. This guide covers the complete overlap — FAQ schema, named attribution, structured formatting, and entity clarity.
Read GEO & AEO guide →Test your understanding of SERP features and content optimisation with IndexCraft's technical SEO practice quiz. Or check your full AI and traditional search readiness against the AEO, SEO, and GEO checklist.