Google Discover SEO: How to Get Your Content Into the Discover Feed

Google Discover is a content recommendation feed built into the Google app and Chrome's mobile new tab page. It surfaces content to users before they search — without a keyword query — based on their interests, search history, and content engagement signals. For content-heavy sites, Discover can drive more mobile traffic than organic search for individual articles. Understanding how it works and what technical prerequisites it requires is essential for capturing that distribution.

What Google Discover is and how it differs from organic search

Organic search is pull-based: a user types a query, Google matches it to relevant pages, ranks them. Discover is push-based: Google proactively surfaces content it believes a user will find interesting before they express any explicit intent. There is no query to target. There is no keyword to rank for.

Discover infers user interests from:

• Topics and entities they've searched for on Google
• Pages they've visited and how long they spent on them
• YouTube content they've watched
• Google account signals (location history, interests settings)
• Engagement with Discover cards (tapping, scrolling, swiping away, using "Not interested in this source")

Content is matched to these interest profiles by the entities and topics it covers — not by keyword density or backlink anchors. A page about "Formula 1 racing" will appear in the Discover feed of users who regularly search for racing news, regardless of how it's optimised for any specific keyword.

The single most important technical prerequisite: max-image-preview

Google requires a large, compelling image for Discover placement. By default, many sites set restrictive image preview policies that prevent Discover from using full-size images. Without large image previews enabled, Discover either won't surface your content or will show it with a small thumbnail that gets substantially fewer taps.

To enable large image previews, add this to either your robots meta tag or your robots.txt:

HTML meta tag (per page):

<meta name="robots" content="max-image-preview:large">

HTTP header (site-wide via server config or CDN):

X-Robots-Tag: max-image-preview:large

robots.txt (site-wide):

User-agent: Googlebot
max-image-preview:large

The max-image-preview:large directive tells Google it has permission to use your full-resolution image when displaying a preview in Discover, Google News, and other Google products. Omitting this directive or setting max-image-preview:none or max-image-preview:standard significantly reduces Discover exposure.

Additionally, the image itself must be at least 1,200 pixels wide. Images below 1,200px do not qualify for large preview display even if the meta tag is present. Verify that your primary article image (usually the featured image or the first large in-body image) meets the 1,200px minimum.

Image placement and markup for Discover eligibility

Beyond size and the preview permission directive, the image must be associated with the article in a way Google can parse:

Recommended image placement:

• The image should be in the article HTML, not loaded solely via JavaScript or as a background CSS image
• It should appear near the top of the article (before the main body text begins)
• It should have descriptive alt text related to the article topic

Structured data for image association: If you use Article or NewsArticle JSON-LD schema, include an image property pointing to the 1,200px+ image:

{
  "@type": "Article",
  "headline": "Your Article Title",
  "image": {
    "@type": "ImageObject",
    "url": "https://example.com/images/article-hero.jpg",
    "width": 1200,
    "height": 628
  }
}

Google's structured data testing tools will verify whether the Article image is properly linked.

Content signals that influence Discover eligibility

Discover doesn't rank by keyword metrics. The editorial signals that matter:

Freshness. Discover strongly favours recently published content. Articles published within the last 24–72 hours are more likely to surface for topic-matching users than articles published months ago. For evergreen content, a material update (not just a date bump) can trigger a Discover re-evaluation. Date visible on the page (in human-readable form near the headline, not just in JSON-LD) is a positive signal.

Novelty and interest. Discover is designed to surface content users will find engaging and share-worthy — analysis, surprising findings, original reporting, unique takes. Thin summaries of information that's already been widely covered elsewhere don't perform as well as pieces with original angles or exclusive data.

Compelling title without clickbait. The article title is prominent in the Discover card. Titles that are descriptive and curiosity-inducing perform better (more taps) without triggering Google's Discover clickbait policies. Misleading titles (promising information the article doesn't deliver), titles using sensationalist language about health or financial topics, and titles designed primarily to provoke outrage are penalised under Discover's policies.

On-topic depth. Articles that comprehensively cover an entity or topic match more user interest profiles. A 2,000-word explainer on Formula 1 aerodynamics covers more related entities (downforce, diffusers, DRS, CFD) than a 300-word news update, giving Google more signals to match it against user interest profiles.

E-E-A-T signals for Discover

Discover applies Google's E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) quality standards, particularly for content in YMYL (Your Money Your Life) topics — health, finance, legal advice, safety. Signals that support Discover eligibility:

Author visibility. Bylines matter. The author's name should be visually present near the article headline. Author pages that include the author's credentials, professional background, and publication history improve E-E-A-T signals for Discover.

Publisher information. The About page, contact information, editorial policy, and corrections policy contribute to publisher trustworthiness signals. Sites without clearly identified publishers are less likely to receive sustained Discover distribution.

Person JSON-LD on author pages. Person schema with sameAs linking to the author's LinkedIn, Twitter/X, or Wikipedia page strengthens entity-level authorship signals.

Factual accuracy. Sites that have received manual actions or have been fact-checked as inaccurate are suppressed in Discover. There's no single technical fix for this — it's a consequence of editorial quality over time.

Core Web Vitals and mobile performance

Discover traffic is entirely mobile. Users tap a Discover card on their phone and land on a mobile page. This makes mobile Core Web Vitals — particularly INP (responsiveness to tap interactions) and CLS (layout stability during page load) — directly relevant to Discover performance.

A page with Poor LCP or Poor INP that surfaces in Discover will generate low engagement (users abandon slow-loading pages before reading) and over time Google deprioritises pages with poor post-tap engagement signals. Good CWV supports sustained Discover distribution; Poor CWV undermines it even for topically relevant content.

Check your LCP, CLS, and INP in Google Search Console → Core Web Vitals, and per-URL in DeepSEOAnalysis. Mobile performance is more likely to be Poor than desktop for most sites.

How to measure Discover traffic in Google Search Console

Google Search Console provides a dedicated Discover report, but it only appears when a property has accumulated enough Discover impressions to display (Google does not show data below a privacy threshold).

If your site receives Discover traffic:

• GSC → Overview → scroll to the Discover section, or navigate to Search results → Search type: Discover
• Metrics: Impressions, Clicks, CTR per page
• No position data (Discover doesn't have numbered rankings)
• Filter by page to see which articles are being surfaced
• Filter by date to identify spikes correlating with publication dates of specific articles

If the Discover report doesn't appear in your GSC property, the site either hasn't accumulated enough Discover impressions yet or hasn't been surfaced in Discover. Verify your max-image-preview:large setting is in place first.

Common reasons sites don't appear in Discover

Missing or restrictive image preview policy. The most common technical cause. Verify with browser DevTools: load any article page and inspect the <meta name="robots"> tag — it should include max-image-preview:large. A missing directive (default) or max-image-preview:standard limits Discover image rendering.

Images below 1,200px. Verify your primary article images in the image dimensions inspector. Featured images that resize below 1,200px on upload or through CMS processing fail the threshold.

Noindex on article pages. Pages with noindex are excluded from Discover as well as organic search. Verify that article pages and blog post pages don't have noindex set by mistake (common on staging sites that were launched without removing noindex).

AMP without a canonical. If articles are AMP-only (no canonical HTML version), Discover may show the AMP page. If the AMP page has rendering or structured data issues, Discover eligibility is reduced.

Low E-E-A-T signals. Sites with no visible authorship, no About page, no publisher information, or a history of inaccurate content face Discover suppression. This is a long-term editorial quality issue, not a quick technical fix.

FAQ

Can I specifically optimise for Google Discover like I do for keyword rankings?

Not in the same direct way — there's no keyword to target. Discover optimisation focuses on: (1) technical prerequisites (max-image-preview:large, 1,200px+ images); (2) topical and entity depth (covering topics comprehensively so Google can match your content to relevant interest profiles); (3) freshness (publishing regularly in your topic area); (4) E-E-A-T signals (authorship, publisher information, factual accuracy); and (5) mobile performance (CWV). Beyond these, Discover distribution depends on your content matching users' inferred interests — a factor that's partly outside your control.

Is Google Discover only for news sites?

No — while news publishers were among the first major beneficiaries, Discover surfaces any type of content: how-to guides, product reviews, educational articles, opinion pieces, explainers. Any niche can benefit from Discover if the content is high-quality, topically relevant to discoverable user interests, and meets the technical prerequisites. Niche topic sites (cooking, personal finance, travel, health) often report strong Discover traffic for their best articles.

Does max-image-preview:large affect anything besides Discover?

Yes. The max-image-preview directive affects image preview sizes across Google products: Discover, Google News, and Google Image Search snippets. Setting max-image-preview:large benefits image search visibility as well as Discover. There is no downside to allowing large previews for published article images — the directive doesn't affect copyright protection or restrict how images are displayed on your own site.

How long does it take to start receiving Discover traffic?

There's no fixed timeline. New sites with strong E-E-A-T signals and proper technical setup (max-image-preview:large, 1,200px images) may see Discover traffic within weeks of publishing high-quality content in a topic area with strong user interest. Established sites that add the max-image-preview:large meta tag often see Discover impressions within a few crawl cycles. Track in GSC → Discover — if the report doesn't appear, the site either hasn't accumulated enough impressions or hasn't been surfaced yet.