Google Discover SEO

TL;DR — Google DiscoverGoogle Discover is a personalized, mobile-first content feed built into the Google app, Chrome's mobile New Tab page, and google.com that surfaces articles and videos based on a user's interests and activity — not a response to a search query. There's nothing to 'rank' for in the traditional sense; eligibility is governed by Discover's content policies plus the same helpful-content, image, and page-experience signals Google Search already uses. is a feed — the cards of articles and videos you see in the Google app and on Chrome’s mobile home screen. Google pushes it to people based on their interests, so there’s no search and no keyword to rank for. You can’t optimize for a Discover query because there isn’t one. What you can do is make your content eligible: get it indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., follow Google’s content rules, write honest titles, and give it a big high-quality image.

What Google Discover actually is

Most SEO is about search: someone types a query, and you try to rank for it. Discover works the other way around. It’s a feed of articles and videos that Google shows people before they search anything — in the Google app, on the Chrome mobile New Tab page, and on google.com — based on what Google thinks each person is interested in. Google’s own words: Discover “shows people content related to their interests, based on their Web and App Activity.” When Google launched it back in 2018, the tagline was literally “no query required.”

That one fact changes everything. There’s no keyword to target, no position to climb, no SERP to analyze. So if you came here looking for “Google Discover ranking factors,” the honest answer is that there isn’t a ranking-factors list the way there is (loosely) for search. There’s eligibility instead.

How you get in (eligibility, not ranking)

The good news is that there’s no special setup. Google says content is automatically eligible to appear in Discover once it’s indexed and it follows Discover’s content policies — “no special tags or structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. are required.” Being eligible isn’t a promise you’ll appear, but you don’t have to do anything technical to qualify.

The things that genuinely help, per Google:

• Don’t use clickbait. Titles and images that over-promise or hide what the content is actually about work against you here.
• Write honest headlines that capture what the piece is really about.
• Skip sensationalism — outrage-bait and shock tactics are things Google actively tries to suppress in Discover.
• Use big, high-quality images. Large, relevant images are the single most visible Discover lever — a great image is what makes a card worth tapping. (More on the exact size in the Advanced tab.)
• Give people a good page experienceGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data. — fast, mobile-friendlyWhether a page is easy to use on a mobile/touch device — legible text without zooming, tap targets sized and spaced to avoid mis-taps, content that fits the viewport with no horizontal scrolling, and no intrusive interstitials. Distinct from mobile-first indexing and Core Web Vitals., easy to read. Discover is a mobile surface first and foremost.

The thing most people get wrong

Discover traffic comes and goes, and that’s normal. A single article can suddenly send you a flood of visits from Discover for a few days and then drop back to almost nothing — permanently. That isn’t a penalty and it usually doesn’t mean you did anything wrong. Google says it directly: treat Discover as supplemental traffic, not something to build your business around. If you get a spike, enjoy it, but don’t rebuild your whole content plan around chasing the next one.

Want the exact image specs, the content policies, and what the February 2026 Discover core update changed? Switch to the Advanced tab.

TL;DR — Discover is a feed, not a query response — there’s no keyword to target, only eligibility. Content is eligible automatically once indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. and policy-compliant; no special markup is required. The documented levers: avoid clickbait/sensationalism, use honest titles, ship large high-quality images (≥1200px wide, >300k pixels, 16:9, with max-image-preview:large + og:image/schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor.), and deliver a good page experienceGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data. on a mobile-first surface. Content policies (ads disclosure, no misleading previews, transparency/ bylines) are the enforcement layer and can trigger a Discover-specific manual action. Traffic is spiky and non-recurring by design — Google calls it supplemental. The Feb 2026 Discover core update (a first) targeted clickbait, local relevance, and topic-by-topic expertise. There’s no public “Discover algorithm” — be honest about the opacity.

Discover is a feed, not a SERP

I want to plant this flag before anything else, because it reframes the whole article: Discover is not a response to a query. There’s no search box in the loop. Google decides, based on a person’s Web & App Activity, that a piece of content might interest them, and it puts a card in their feed. That means there is nothing to rank for in the traditional sense — no keyword, no position, no SERP. Any article you read that hands you a numbered list of “Discover ranking factors” is, at best, describing correlations someone inferred, not documented mechanics. Keep that distinction in your head and most of the confusion around Discover disappears.

This is the same framing our news SEO hub uses, and it’s worth restating: you optimize for search by targeting queries; you make yourself eligible for Discover and then hope the feed picks you.

How content becomes eligible

Google is refreshingly clear here: “Content is automatically eligible to appear in Discover if it is indexed by Google and meets Discover’s content policies. No special tags or structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. are required. Note that being eligible to appear in Discover is not a guarantee of appearing.” And because Discover is part of Search, “Discover makes use of many of the same signals and systems used by Search to determine what is helpful, people-first contentThe Helpful Content Update (HCU) was a series of Google updates starting in August 2022 that added a site-wide, machine-learning classifier to demote content made primarily to rank rather than to help people. In March 2024 it was folded into Google's core ranking system..”

So the prerequisites are just: (1) get indexed, and (2) don’t violate the policies. Everything else is about improving your odds of being shown, not unlocking a gate.

The levers Google actually documents

Google’s own recommended-practices list is the closest thing to an optimization checklist that exists. It says to avoid clickbait and misleading previews, use titles and headlines that capture the essence of the content, avoid sensationalism, provide content that’s timely or offers unique insight, include compelling high-quality images (“especially large images that are more likely to generate visits from Discover”), use og:image or schema.org markup to specify that large image, and “provide an overall great page experience.” Let me pull out the parts that actually move the needle.

Images are the big one. Discover is a visual feed, and the image is what earns the tap. Google’s spec: “At least 1200 px wide; High resolution of more than 300,000 total pixels…; 16x9 aspect ratio.” But the image only shows up large if you’ve unlocked large previews with the max-image-preview:large robots directive (also enabled automatically by AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories.). If your pages send max-image-preview:standard or none, Discover cannot show a large image no matter how good it is — so this one robots meta setting is a genuine hard gate on the most important lever. Google adds practical cropping advice too: it tries to auto-crop for landscape use, so “be sure your images are well-cropped and positioned for landscape usage,” “avoid using generic images (for example, your site logo),” and “for best results, avoid using text-heavy images.”

Titles that match the content. The recommendation is to “use page titlesThe title tag is the HTML title element in a page's head that specifies the document's title. It's the primary source for the SERP title link and a confirmed light ranking factor — but since August 2021 Google doesn't always show it verbatim. and headlines that capture the essence of the content” — not to write the most tantalizing thing you can. Which flows straight into the anti-clickbait rule.

No clickbait, no sensationalism. Google names these explicitly, twice — once in the best-practices doc (“Avoid clickbait…by using misleading or exaggerated details in preview content” and “Avoid sensationalism tactics that manipulate appeal by catering to morbid curiosity, titillation, or outrage”) and again, more pointedly, in the February 2026 core update (below). Short-term engagement bait points in the opposite direction of what Discover rewards.

Page experience and mobile. The last documented bullet is simply “provide an overall great page experience.” Discover lives almost entirely on phones, so mobile experience isn’t a nice-to-have here. Rather than re-explain Core Web Vitals or mobile-first indexingTechnical SEO is the practice of making a site easy for search engines to crawl, render, index, and (now) be eligible for AI answers. It's the foundation that lets your content and links rank — not a ranking trick of its own., I’ll point you to those — the point is that the same page-experience and mobile-friendliness work you’d do for search is exactly what Discover leans on.

One more, on freshness: Discover isn’t only for breaking news. Google says older content can appear “if it’s helpful and relevant to individuals based on their interests.” So while content freshnessSearch works in three stages — crawling, indexing, and serving (ranking). A page has to clear each one to appear in results: getting crawled doesn't mean you're indexed, and getting indexed doesn't mean you rank. and timeliness clearly help, evergreen pieces are eligible too — don’t assume you need to be a news site.

The content policies — the enforcement layer

Separate from the best-practices page, there’s a distinct Discover content policies document, and this is the part a lot of competing content skips. To be eligible, content “must not violate Google Search’s overall policies, Google Search’s spam policies,” or a named list of feature policies (dangerous content, deceptive practices, harassing content, medical content, sexually explicit content, and so on). Three of these are worth calling out because they’re concrete:

• Ads & sponsored content must be disclosed: “Advertising and other paid promotional material on your pages should not exceed your content… Sponsorship… should be clearly disclosed to readers.”
• Misleading content is banned: “We don’t allow preview content that misleads users to engage with it by promising details which aren’t reflected in the underlying content.”
• Transparency is a named Discover policy, not a vague E-E-A-T gesture. News sources should provide “Clear dates and bylines; Information about the authors, publication, and publisher; Information about the company or network behind the content; Contact information.”

That transparency requirement is the cleanest, most literal link between Discover eligibility and E-E-A-T — authorship and bylines aren’t just quality-rater folklore here, they’re written policy. And the policies have teeth: “When we find content or behavior that violates these policies, we may remove the content from Discover… If your site violates one or more Discover content policies, Discover manual actions may appear in your Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. under Security & Manual actions.” A Discover-specific manual action is a real thing you can receive.

Why Discover traffic spikes and disappears

This is the part every publisher eventually learns the hard way, so let me be blunt about it up front — it’s normal. Google’s own docs: “Traffic from Discover is less predictable or dependable when compared to keyword-driven search visits. Given its serendipitous nature, you should consider traffic from Discover as supplemental to your keyword-driven search traffic.”

Google lists three reasons the traffic moves around, and none of them are “you got penalized”: changing interests (as people’s interests shift, the feed shows them other things), content types (Google adjusts which kinds of content the feed emphasizes), and updates to Google Search (since Discover is an extension of Search, a Search update can move Discover traffic — and, notably, “it may be that there’s nothing you need to do after an update”).

The reps have said the same thing for years, more vividly. John Mueller: “the traffic tends to be very on or off… suddenly you get a lot of traffic from Discover. And then our algorithms might at some point say it doesn’t make sense to show it that much in Discover anymore and then the traffic goes away.” His advice: “if you do see a lot of visibility from Google DiscoverGoogle Discover is a personalized, mobile-first content feed built into the Google app, Chrome's mobile New Tab page, and google.com that surfaces articles and videos based on a user's interests and activity — not a response to a search query. There's nothing to 'rank' for in the traditional sense; eligibility is governed by Discover's content policies plus the same helpful-content, image, and page-experience signals Google Search already uses., I think that’s fantastic. I just would be careful and kind of realize that this is something that can change fairly quickly.” Gary Illyes put the practical conclusion most sharply back in 2019: “I just hope people realize that this may go away overnight and they don’t build their whole business model around it.”

So: a good article spiking then dropping to near-zero is the expected behavior of an interest-based feed. It is not, by itself, a penalty signal.

The February 2026 Discover core update

The freshest reason this topic matters right now: on February 5, 2026, Google announced the February 2026 Discover core update — notably the first core update Google has ever announced as specific to Discover rather than to Search generally. (Normal core updates affect Discover too; this was the first one framed as a Discover update.) Google said the update would improve the experience by:

• “Showing users more locally relevant content from websites based in their country”
• “Reducing sensational content and clickbait in Discover”
• “Showing more in-depth, original, and timely content from websites with expertise in a given area”

The most useful part for publishers is Google’s framing of expertise as topic-by-topic, with a concrete example: “a local news site with a dedicated gardening section could have established expertise in gardening, even though it covers other topics. In contrast, a movie review site that wrote a single article about gardening would likely not.” The takeaway is that both narrow-niche and broad sites can qualify — but on the strength of demonstrated depth in a topic, not just publishing volume.

Google said the rollout could take up to two weeks and was launching to English- language US users first, expanding to other languages and countries “in the months ahead.” As with any core update, “some sites might see increases or decreases; many sites may see no change at all.” Publisher reaction in the Search Engine Roundtable thread was the usual mixed picture — some reporting they were “90-95% down” and others that their site “did start showing up again on Discover” — but treat those as anecdotal forum comments, not data. The volatility they describe is exactly what Google warns about above.

What you can’t do — and being honest about the opacity

A few things are worth stating plainly so you don’t waste effort:

• You can’t target keywords. There’s no query. Keyword targeting is a search concept that doesn’t map onto a feed.
• There’s no special schema trick. No structured data is required for eligibility. The only markup-adjacent lever that matters is max-image-preview:large (a robots directive, not schema) plus optional og:image/schema.org image markup to hint which image Discover should prefer.
• The Follow/RSSAn RSS or Atom feed is an XML file listing a site's most recently published or updated URLs. Search engines accept it as a sitemap-style discovery signal for fresh content — not a replacement for a full XML sitemap. feature is gone. Google used to let users “Follow” a site’s feed inside Discover, and site owners could specify a preferred feed. Google has removed that guidance because the Follow feature is no longer shown in Discover — don’t build an RSS/<link> tactic around it.
• There is no public “Discover algorithm.” Unlike, say, the documented Core Web Vitals thresholds, Google has never published ranking-factor-style documentation for Discover. What exists is an eligibility/best-practices page and a content- policies page. Anyone selling you “the 11 Discover ranking factors” is inferring from correlation. I’d rather tell you that than pretend otherwise.

Monitoring your Discover performance

You can see your Discover data in Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance.. Google: “If you have content on Discover, you can monitor your performance using the Performance reportThe Google Search Console report that shows how your site actually performed in Google Search, built from real impressions and clicks. It reports four metrics — clicks, impressions, average CTR, and average position — and keeps the most recent 16 months of data. for Discover. This report shows impressions, clicks, and CTR for any of your content that has appeared on Discover in the last 16 months… The Discover performance report includes traffic from Chrome, and fully tracks a site’s Discover traffic across all surfaces.” Note that the Discover filter only shows up in Search Console once you’ve had enough Discover impressions to cross the reporting threshold — no data doesn’t necessarily mean no eligibility, just not enough volume yet. I’m not going to re-teach the report mechanics here; the closest existing sibling on this site is the general Performance reportThe Google Search Console report that shows how your site actually performed in Google Search, built from real impressions and clicks. It reports four metrics — clicks, impressions, average CTR, and average position — and keeps the most recent 16 months of data. write-up, and a dedicated Discover-report deep dive is the right home for the 16- month window, impression counting, and Discover-specific filtering when it’s built.

Should you optimize for Discover at all?

For publishers, the stakes are real. Chartbeat data on 565 US/UK publishers, reported by Search Engine Land, found that “Discover is now the primary driver of Google referrals” for that cohort, with traditional Search referrals down to roughly 19% of Google-driven traffic by July 2025. So Discover isn’t a novelty — for many news sites it’s the main event.

But that’s exactly why the “supplemental, can vanish overnight” warning matters more, not less, the more Discover-dependent you become. My honest read: do the work that overlaps with everything else you should already be doing — genuinely good content, honest titles, strong original images, fast mobile pages, clear authorship — and treat any Discover traffic as upside. Don’t chase Discover- specific gimmicks, and don’t let a Discover spike lull you into thinking you’ve built a durable channel. Diversify so that the day Discover moves on (and for any given article, it will) you’re not left with nothing.

A note on Bing: Microsoft has a rough equivalent, Microsoft Start (the feed on Edge’s New Tab page, MSN, and the Microsoft Start app). It’s not a surface most people optimize for directly, and Microsoft doesn’t publish detailed technical guidance comparable to Google’s Discover docs — but the same general principles (quality, no clickbait, clear authorship, strong images) transfer if you publish news.

AI summary

A condensed take on the Advanced version:

• Discover is a feed, not a query response. No keyword to target, no SERP position — only eligibility. It’s pushed to people based on Web & App Activity in the Google app, Chrome mobile New Tab, and google.com.
• Eligibility is automatic once a page is indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. and policy-compliant. “No special tags or structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. are required.” Eligible ≠ guaranteed to appear.
• Documented levers: avoid clickbait and sensationalism; write honest titles; ship large high-quality images (≥1200px wide, >300k pixels, 16:9) with max-image-preview:large + og:image/schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. so Discover can show a large thumbnail; provide a good page experienceGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data. on a mobile-first surface. Evergreen content is eligible too, not just news.
• Content policies are the enforcement layer: ad/sponsorship disclosure, no misleading previews, and transparency (bylines, author/publisher/contact info). Violations can trigger a Discover-specific manual action in Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results..
• Traffic is spiky and non-recurring by design. Google calls it supplemental and “less predictable or dependable” than search; Mueller describes it as “on or off”; Illyes warned not to build a business model on it. A spike-then-drop is normal, not a penalty.
• Feb 2026 Discover core update (a first-of-its-kind) targeted clickbait/ sensationalism, local relevance, and topic-by-topic expertise.
• Be honest about opacity: there’s no public “Discover algorithm,” no keyword targeting, no schema trick, and the Follow/RSSAn RSS or Atom feed is an XML file listing a site's most recently published or updated URLs. Search engines accept it as a sitemap-style discovery signal for fresh content — not a replacement for a full XML sitemap. feature is gone. Monitor in Search Console’s Discover filter.

Official documentation

Primary-source documentation from Google. Discover-specific guidance is thinner than Search guidance by design — this is essentially the whole official set.

Google — Discover

• Discover and your website — the core doc: eligibility, recommended practices, image specs, why traffic changes, and the Performance reportThe Google Search Console report that shows how your site actually performed in Google Search, built from real impressions and clicks. It reports four metrics — clicks, impressions, average CTR, and average position — and keeps the most recent 16 months of data. pointer.
• Discover content policies — the enforcement layer: ads/sponsorship, misleading content, transparency, and manual actions.
• Google’s February 2026 Discover core update — the first Discover-specific core update announcement (clickbait reduction, local relevance, topic-by-topic expertise).
• Introducing Google Discover (2018 launch) — the original “no query required” framing and the “800 million people” figure.

Related Google docs (cross-surface levers)

• Robots meta tag & max-image-preview — the directive that unlocks large image previews in Discover.
• Search Console — Performance report — where the Discover filter lives.

Quotes from the source

On-the-record statements from Google. Each link is a deep link that jumps to the quoted passage on the source page.

Google — what Discover is and how eligibility works

• “Discover is a part of Google Search that shows people content related to their interests, based on their Web and App Activity.” — Discover and your website, Google Search Central. Jump to quote
• “Content is automatically eligible to appear in Discover if it is indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. by Google and meets Discover’s content policies. No special tags or structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. are required. Note that being eligible to appear in Discover is not a guarantee of appearing.” Jump to quote
• “As part of Google Search, Discover makes use of many of the same signals and systems used by Search to determine what is helpful, people-first contentThe Helpful Content Update (HCU) was a series of Google updates starting in August 2022 that added a site-wide, machine-learning classifier to demote content made primarily to rank rather than to help people. In March 2024 it was folded into Google's core ranking system..” Jump to quote

Google — the recommended practices (images, titles, clickbait, page experienceGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data.)

• “Include compelling, high-quality images in your content that are relevant, especially large images that are more likely to generate visits from Discover.” Jump to quote
• “At least 1200 px wide; High resolution of more than 300,000 total pixels (for example, a 16:9 image that’s 1280x720 pixels would have 921,600 total pixels and satisfies this specification); 16x9 aspect ratio.” Jump to quote
• “Google tries to automatically crop the image for use in Discover… avoid using generic images (for example, your site logo)… For best results, avoid using text-heavy images.” Jump to quote

Google — traffic volatility

• “Traffic from Discover is less predictable or dependable when compared to keyword-driven search visits. Given its serendipitous nature, you should consider traffic from Discover as supplemental to your keyword-driven search traffic.” Jump to quote

Google — the content policies

• “We don’t allow preview content that misleads users to engage with it by promising details which aren’t reflected in the underlying content.” — Discover content policies, Google Search Help. Read the policy

John Mueller, Google — on/off traffic (via Search Engine Journal’s reporting of the Feb 5, 2021 SEO Office Hours)

• “the traffic tends to be very on or off… suddenly you get a lot of traffic from Discover. And then our algorithms might at some point say it doesn’t make sense to show it that much in Discover anymore and then the traffic goes away.”
• “if you do see a lot of visibility from Google DiscoverGoogle Discover is a personalized, mobile-first content feed built into the Google app, Chrome's mobile New Tab page, and google.com that surfaces articles and videos based on a user's interests and activity — not a response to a search query. There's nothing to 'rank' for in the traditional sense; eligibility is governed by Discover's content policies plus the same helpful-content, image, and page-experience signals Google Search already uses., I think that’s fantastic. I just would be careful and kind of realize that this is something that can change fairly quickly.” Read the coverage Relayed source — Mueller’s spoken remarks as reproduced by Search Engine Journal; confirm against the original office-hours recording before treating as final.

Gary Illyes, Google — don’t bet the business on it (via Search Engine Roundtable’s reporting of a Nov 8, 2019 tweet)

• “I just hope people realize that this may go away overnight and they don’t build their whole business model around it.” Read the coverage Relayed source — a tweet reproduced by Search Engine Roundtable; confirm against the original post before treating as final.

John Mueller, Google — the Feb 2026 core update, topic-by-topic expertise

• “Since many sites demonstrate deep knowledge across a wide range of subjects, our systems are designed to identify expertise on a topic-by-topic basis. So whether a site has expertise in multiple areas or has a deep focus on a single topic, there’s equal opportunity to show up in Discover.” — Google’s February 2026 Discover core update, Google Search Central Blog. Read the announcement

Discover mistakes — and what to do instead

The most common Discover myths, each paired with why it’s wrong and what to actually do. Most of these come from treating Discover like search.

❌ “There’s a Discover algorithm / ranking-factors list I can reverse-engineer.” Why it’s wrong: Google has never published ranking-factor documentation for Discover the way it has (loosely) for Search. What exists is an eligibility/best- practices page and a content-policies page. Numbered “Discover ranking factors” lists are industry inference, not confirmed mechanics. Do instead: Follow the documented eligibility levers and content policies, and hold everything else as an unproven hypothesis.

❌ “You optimize for Discover with keywords.” Why it’s wrong: There’s no query in Discover. Keyword targeting is a search concept that doesn’t map onto a feed. Do instead: Optimize the content, the title’s honesty, the image, and the page experience — not a target term.

❌ “A Discover traffic drop means I got penalized.” Why it’s wrong: Google (and Mueller) describe fluctuation as the normal behavior of the feed — driven by changing user interests, feed-composition changes, or unrelated Search updates. A spike-then-drop is expected. Do instead: Confirm it’s a Discover-wide pattern (check the Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. Discover filter) before assuming a quality problem; often there’s nothing to fix.

❌ “Special schema/structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. gets me into Discover.” Why it’s wrong: No special tags or structured data are required for eligibility. Do instead: Set max-image-preview:large (a robots directive) so a large image can show at all, and optionally use og:image/schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. image markup to hint the preferred image. That’s the only markup-adjacent lever that matters.

❌ “Clickbait or a viral, sensational headline will get me picked up.” Why it’s wrong: Google explicitly names avoiding clickbait and sensationalism as recommended practices, and the Feb 2026 core update specifically targeted reducing them. Engagement bait points the wrong way. Do instead: Write a headline that honestly captures the piece, and let a strong, relevant image do the “make me tap” work.

❌ “Once I’m in Discover, I’ll stay in Discover.” Why it’s wrong: Both the docs and Mueller’s “on or off” description say the opposite — visibility can disappear “fairly quickly,” and that’s expected. Do instead: Treat Discover as supplemental; diversify so no single article’s Discover spike is load-bearing for your traffic.

❌ “RSSAn RSS or Atom feed is an XML file listing a site's most recently published or updated URLs. Search engines accept it as a sitemap-style discovery signal for fresh content — not a replacement for a full XML sitemap. / the Follow feature is how I grow a Discover audience.” Why it’s wrong: The Follow feature has been removed from Discover, and Google no longer documents it as a Discover lever. Do instead: Ignore Follow/RSS as a Discover tactic; it’s history.

❌ “Discover is only for breaking news, so evergreen content is pointless.” Why it’s wrong: Google says older content can appear “if it’s helpful and relevant to individuals based on their interests.” Do instead: Don’t withhold evergreen pieces from your Discover thinking — a genuinely useful evergreen article with a strong image is eligible too.

”I’m not getting Discover traffic (or I lost it) — where do I start?”

Work top-down. Most Discover problems are either an eligibility gate (image directive, policy issue) or the normal volatility of the feed — not something exotic.

Discover eligibility checklist

A quick pass to confirm you’re eligible and giving yourself the best odds:

• Key pages are indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. (eligibility prerequisite #1).
• No Discover manual action in Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. > Security & Manual actions.
• max-image-preview:large is set (or the page uses AMPAMP (Accelerated Mobile Pages) is an open-source web framework Google launched in 2015 to make mobile pages load near-instantly via restricted HTML/CSS/JS and CDN caching. It was never a ranking factor and, since June 2021, is no longer required for Top Stories.) — the hard gate on large images.
• Each article has a large, relevant, original image: ≥1200px wide, >300k total pixels, 16:9 — specified via og:image or schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor..
• Images are not your logo, not text-heavy, and cropped/positioned for landscape.
• Titles are honest — they capture the essence of the content, no clickbait or exaggerated preview details.
• No sensationalism (outrage/shock/titillation bait).
• Ads/sponsorship disclosed and not exceeding the content.
• Transparency present: clear dates, bylines, author/publisher info, and contact information.
• Page is fast and mobile-friendlyWhether a page is easy to use on a mobile/touch device — legible text without zooming, tap targets sized and spaced to avoid mis-taps, content that fits the viewport with no horizontal scrolling, and no intrusive interstitials. Distinct from mobile-first indexing and Core Web Vitals. (Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data.) — Discover is mobile-first.
• You’re monitoring the Discover filter in Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance.’s Performance report.
• You’re treating Discover traffic as supplemental, not the foundation of your traffic plan.

SOP: New-article Discover readiness pass

A repeatable pre-publish check to run on every article that could plausibly earn Discover traffic. Takes a few minutes and closes the gaps that actually gate eligibility.

1. Confirm the article will be indexable. No noindex, not blocked in robots.txt, canonical points to itself. If it can’t be indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., it can’t be eligible for Discover.

2. Verify the large-image directive. Check that the page (or site-wide default) sends max-image-preview:large. This is the most-missed gate — without it, Discover can’t show a large thumbnail regardless of image quality.

3. Ship a Discover-grade image. One relevant, original image ≥1200px wide, >300k total pixels, 16:9, referenced in og:image (and/or schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor.). Not the logo, not text-heavy, cropped for landscape. This is the single most visible lever.

4. Sanity-check the headline. Does the title honestly capture the piece? Strip anything that over-promises, withholds the point, or trades on outrage/shock. If it reads like bait, rewrite it.

5. Confirm transparency signals. Visible publish date, a real byline linked to a meaningful author bio, and site-level publisher/contact info. These are named Discover content policies, not optional polish.

6. Run the mobile/page-experience check. Load it on a phone (or run Core Web Vitals). Discover is mobile-first; a slow or clumsy mobile page undercuts everything above.

7. Log a baseline, then leave it alone. After publishing, note the date so you can later attribute any Discover spike or drop in the Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. Discover filter. Don’t tweak reactively on day one — Discover volatility is normal.

Recurrence: run steps 1–6 on every publish; run step 7 as a weekly glance at the Discover filter for anything that spiked.

Prompts for a Discover readiness review

Audit a draft card and article

Paste the headline, dek, draft body, proposed og:image URL and dimensions, and the robots meta value. Expect an evidence-based readiness review, not a prediction that the article will appear in Discover.

Review this article for Google Discover readiness using only these documented levers:
- The page must be indexed and comply with Search and Discover content policies.
- The headline and preview must accurately reflect the article, without clickbait,
  withheld details, sensationalism, or outrage bait.
- The proposed image should be relevant, high quality, at least 1200 px wide, more than
  300,000 total pixels, suitable for a 16:9 landscape crop, and not generic or text-heavy.
- Large previews require max-image-preview:large; og:image or image markup identifies
  the preferred image.
- The page should clearly show dates, bylines, author/publisher information, ownership,
  contact details, and sponsored-content disclosure where applicable.

Return pass, review, or fail for each item and quote the supplied evidence. Separate hard
eligibility/policy problems from best-practice improvements. Flag claims or image facts
that require a human to verify. Do not invent a Discover score, keyword target, ranking
factor, or guarantee of traffic.

[PASTE HEADLINE, DEK, ARTICLE, IMAGE DETAILS, ROBOTS VALUE, AND TRANSPARENCY ELEMENTS]

Compare headline promise with article delivery

Paste several headline/body pairs from one topic. Expect mismatch flags plus editorial questions; the model should not rewrite unsupported facts.

Check each supplied Google Discover headline against its article body.

For every pair, identify the central promise made by the headline and preview, show where
the body fulfills it, and flag exaggerated, withheld, or sensational details that the
article does not support. Also note whether the article adds timely or original insight
rather than merely repackaging the topic.

Return a table with: accurate as written, needs clarification, or misleading; the exact
evidence; and the smallest truthful headline adjustment. Preserve the supplied facts and
tone. Do not add urgency, certainty, names, numbers, or conclusions absent from the body.

[PASTE HEADLINE/BODY PAIRS]

Mental models for Google Discover

1. Feed, not SERP. Discover pushes cards from inferred interests; it does not answer a query. There is no keyword position to target, so conventional rank-tracking logic does not describe the opportunity.

2. Eligibility is not distribution. IndexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., policy-compliant content is automatically eligible, but eligibility never guarantees an impression. Technical and policy checks open the door; an opaque personalized feed decides whether and when a card is shown.

3. Hard gates versus probability levers. Indexability and policy compliance are gates. max-image-preview:large controls whether a large preview can be used. Honest headlines, strong images, original insight, topic expertise, and mobile page experienceGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data. improve the conditions without becoming public ranking-factor guarantees.

4. A spike is an episode, not an annuity. Interests, content mix, and Search systems change. Evaluate Discover as supplemental, volatile distribution and avoid turning one article’s burst into a durable traffic forecast.

5. Expertise is topic-shaped. The February 2026 update’s example makes depth within a topic the useful unit. A broad publisher can demonstrate expertise in a well-developed section; a one-off article outside its pattern does not establish the same signal.

Discover readiness reference

Image and preview requirements

Eligibility, optimization, and reporting

Do not confuse these surfaces

• Search: query-driven; keywords and ranked results exist.
• Discover: personalized, queryless feed; traffic can switch on and off.
• Google News / Top Stories: news eligibility and ranking, with different policy and distribution mechanics.

Check the live Discover image gates in DevTools

Open the article, then paste this into the browser’s DevTools Console. It reports the robots preview directives, resolves the og:image, loads it, and checks the documented width, pixel-area, and approximate 16:9 criteria. This is a page-output check, not proof that Google will select the image or distribute the article.

(() => {
  const robots = [...document.querySelectorAll('meta[name]')]
    .filter((meta) => /^(robots|googlebot)$/i.test(meta.getAttribute('name') || ''))
    .map((meta) => ({
      name: meta.getAttribute('name'),
      content: meta.getAttribute('content') || '',
    }));

  const preview = robots
    .flatMap((meta) => meta.content.split(',').map((part) => part.trim().toLowerCase()))
    .find((part) => part.startsWith('max-image-preview:')) || 'not declared';

  const rawImage = document
    .querySelector('meta[property="og:image"], meta[name="og:image"]')
    ?.getAttribute('content');

  if (!rawImage) {
    console.table({
      maxImagePreview: preview,
      largePreviewAllowed: preview === 'max-image-preview:large',
      ogImage: 'missing',
    });
    return;
  }

  const imageUrl = new URL(rawImage, document.baseURI).href;
  const image = new Image();
  image.onload = () => {
    const width = image.naturalWidth;
    const height = image.naturalHeight;
    const pixels = width * height;
    const ratio = width / height;
    console.table({
      maxImagePreview: preview,
      largePreviewAllowed: preview === 'max-image-preview:large',
      ogImage: imageUrl,
      dimensions: `${width}×${height}`,
      widthAtLeast1200: width >= 1200,
      pixelsOver300k: pixels > 300000,
      approximately16by9: Math.abs(ratio - 16 / 9) < 0.08,
    });
  };
  image.onerror = () => console.error('The og:image could not be loaded:', imageUrl);
  image.src = imageUrl;
})();

The ratio check uses a small tolerance because a landscape image can be cropped; inspect the actual composition yourself to confirm the subject survives a 16:9 crop and that the asset is neither generic nor text-heavy.

Tools for Discover card preflight and reporting

• Open Graph & Social Preview — fetch a live page, verify its Open GraphOpen Graph (OG) tags are `<meta>` elements in a page's head, defined by the Open Graph protocol (ogp.me, created by Facebook), that describe a page as a shareable object — its title, description, image, URL, and type. They control how a link preview card looks when the page is shared on Facebook, LinkedIn, Slack, Discord, WhatsApp, and iMessage. They are not a direct Google ranking factor, though Google reads og:title, og:image, and og:site_name as inputs to how a result appears. image and dimensions, and preview how the headline/image pair renders across card surfaces. Use it to catch missing or unsuitable og:image output; it cannot tell you whether Discover will select or distribute the page.
• Browser DevTools — run the script in the Scripts lens on the live article to inspect max-image-preview and the resolved image dimensions in rendered output.
• Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. Discover Performance reportThe Discover report — Google's own label is 'Performance report (Discover)' — is a separate tab in Google Search Console's Performance section showing how your content performed in the Google Discover feed: impressions, clicks, and average CTR by page, country, date, and appearance type. It only appears once a property has crossed a minimum Discover-impression threshold. — the source of Discover impressions, clicks, and CTR once the property has enough impressions for the report to appear. Absence of the report is not proof that content violates eligibility rules.
• Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. URL InspectionA Google Search Console feature that reports how Google sees one specific URL on a property you own. By default it shows the last-indexed snapshot; a separate \"Test live URL\" mode fetches the current version. — confirm the page is indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. and inspect the rendered output when eligibility is in doubt; Discover has no separate submission tool.
• Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. Manual Actions — check for a Discover policy action when a site-wide visibility loss coincides with an actual policy notice, rather than assuming every traffic drop is a penalty.

Ongoing Discover performance metrics

Discover is volatile, so segment by article, topic, and publish cohort and compare with the property’s own history. A missing Discover reportThe Discover report — Google's own label is 'Performance report (Discover)' — is a separate tab in Google Search Console's Performance section showing how your content performed in the Google Discover feed: impressions, clicks, and average CTR by page, country, date, and appearance type. It only appears once a property has crossed a minimum Discover-impression threshold. can simply mean the reporting threshold has not been reached.

Discover impressions

• Metric: Impressions reported in Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results.’s Discover Performance reportThe Google Search Console report that shows how your site actually performed in Google Search, built from real impressions and clicks. It reports four metrics — clicks, impressions, average CTR, and average position — and keeps the most recent 16 months of data..
• What it tells you: How often eligible content was actually distributed as a Discover card; it measures feed exposure, not keyword rank.
• How to pull it: Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. → Performance → Discover, segmented by page and date; export by topic or publishing cohort when comparing editorial patterns.
• Benchmark / realistic range: Establish the property’s own baseline. Because interests and feed mix change, no universal impression target or stable article curve is defensible.
• Cadence: Weekly for editorial review and monthly for topic/cohort trends; interpret individual spikes as volatile leading exposure rather than recurring traffic.

Discover clicks

• Metric: Clicks from Discover cards in the same Search Console report.
• What it tells you: The visits generated by feed distribution after a card is shown.
• How to pull it: Search Console → Performance → Discover → Clicks, grouped by page, date, and topic; keep it separate from query-driven Web Search clicks.
• Benchmark / realistic range: Compare articles with similar impression opportunity and topic context against your own historical cohorts. Do not forecast a permanent run rate from a short burst.
• Cadence: Weekly while stories are active and monthly in the broader channel review; this is an outcome of impressions and card appeal.

Discover CTR

• Metric: Click-through rate reported for Discover impressions.
• What it tells you: How often shown cards earn a click, reflecting the combined headline, image, topic, and audience context—not a single isolated ranking factor.
• How to pull it: Search Console → Performance → Discover → Average CTR, reviewed by page and topic alongside impression volume.
• Benchmark / realistic range: Use medians from comparable pages on the same property. Low-volume CTR is unstable, and there is no honest cross-site Discover target.
• Cadence: Monthly or by completed article cohort; avoid optimizing daily noise or turning CTR into permission for clickbait.

Test yourself: Google Discover SEO

Five quick questions on how Discover works and how to be eligible. Pick an answer for each, then check.

Resources worth your time

My related writing

• The Beginner’s Guide to Technical SEO — where publisher-specific surfaces like Discover sit relative to the technical foundation every site needs.

My speaking

• How Search Works (SlideShare) — my walkthrough of crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor., renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM., indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., and ranking; useful background since Discover reuses Search’s signals. (My standing disclaimer applies: “This is my understanding of systems… not going to be 100% complete or accurate.”)

From around the industry

• Discover and your website (Google Search Central) — the primary source for eligibility, image specs, and why traffic changes.
• Discover content policies (Google Search Help) — the enforcement layer most guides skip.
• Google’s February 2026 Discover core update (Google Search Central Blog) — the first Discover-specific core update, in Google’s own words.
• Google’s John Mueller Explains Inconsistent Discover Traffic (Search Engine Journal) — the “on or off” quotes on why Discover traffic vanishes.
• Google Warns: Don’t Build Your Business Around Google Discover Traffic (Search Engine Roundtable) — Gary Illyes’ “may go away overnight” warning.
• What is Google Discover? A complete guide for publishers & SEOs (Search Engine Land) — a fuller publisher-oriented guide (read its “ranking factors” claims as industry inference, not confirmed mechanics).
• Google traffic to news publishers is steady, but it isn’t traditional Search (Search Engine Land) — Chartbeat/PressGazette data on how dominant Discover has become for publishers.

Google Discover

Google Discover is a personalized, mobile-first content feed built into the Google app, Chrome's mobile New Tab page, and google.com that surfaces articles and videos based on a user's interests and activity — not a response to a search query. There's nothing to 'rank' for in the traditional sense; eligibility is governed by Discover's content policies plus the same helpful-content, image, and page-experience signals Google Search already uses.

Related: Content Freshness, Core Web Vitals

Google Discover

Google describes Discover as “a part of Google Search that shows people content related to their interests, based on their Web and App Activity.” The important word is feed: Discover is content Google pushes to a person — in the Google app, on Chrome’s mobile New Tab page, and on google.com — based on what it thinks they’re interested in, rather than a response to something they typed. When Google launched it in 2018, the tagline said it plainly: content surfaced “with Search, no query required.”

Because there’s no query, there’s no keyword to target and no SERP position to climb. That reframes the whole optimization problem. Content becomes eligible to appear automatically once it’s indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. and compliant with Discover’s content policies — no special tags or structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. are required — but eligibility is never a guarantee of appearing.

The practical levers publishers actually control are the ones Google documents: avoiding clickbait and sensationalism, using titles and images that honestly reflect the content, supplying a large high-quality image (via max-image-preview:large plus og:image or schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. markup), and delivering a good overall page experienceGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data.. Beyond that, Discover is deliberately opaque — there’s no public “Discover algorithm” the way there’s a documented spec for Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data..

The trait everyone runs into is volatility. Google itself says Discover traffic is “less predictable or dependable when compared to keyword-driven search visits” and should be treated as supplemental. A single article can spike hard from Discover and then drop back to near-zero — that’s the normal, documented behavior of an interest-based feed, not a penalty.

Related: Content Freshness, Core Web Vitals