Sign in Sign up free

Discover Optimization Is Not SEO Optimization - Two Image Signals Most Sites Miss

AI SEO Intelligence

May 25, 2026
Updated November 16, 2026
10 min read
Discover Optimization Is Not SEO Optimization - Two Image Signals Most Sites Miss

Update, November 16, 2026: this post overstated what Google requires. Google's Discover documentation says content "is automatically eligible to appear in Discover if it is indexed by Google and meets Discover's content policies" and "No special tags or structured data are required." Large images - at least 1200 px wide, enabled by max-image-preview:large or AMP - are listed as recommendations "to increase the likelihood of your content appearing in Discover", not as an eligibility floor, so a page without them is not shut out of Discover. The section "What Google's Discover Docs Actually Say" quoted wording that is not on the current page and read it as a hard requirement; it now paraphrases the current documentation instead. Google's case study reports that Kirbie's Cravings' click-through rate rose 79% after it added the meta tag, and Istoé's rose 30%. Google's February 2026 Discover core update post does not list image quality; it names more locally relevant content, less sensational content and clickbait, and more in-depth, original and timely content. We also corrected the body wherever it called the two signals an eligibility floor, a gate or a hard requirement, credited the case study with a thumbnail-or-nothing mechanism it does not describe, cited Google's core update post for ranking inputs it does not name, and gave 1200x675 as Google's example (Google's example is 1280x720). We also removed three claims no source supports: that recipe, product and featured-snippet images "render compressed" without the directive (the robots meta tag specification says only that Google may show an image preview of the default size), that half of Open Graph consumers fall back to thumbnails without og:image:width, and the predictions that Discover will move to 1800-2400 px source images and that 4x3 and 3x2 images get smaller cards. We removed the claim that Discover's render pipeline already handles WebP and AVIF: the Discover documentation names no image formats, and the format list in Google's image SEO guide is for images in Google Search. We narrowed failure mode 3, which said Facebook, LinkedIn and Discover rely on og:image:width: only Facebook's image sharing guide says it uses the width and height tags, to render a shared image without first downloading it, and Google's Discover documentation does not mention og:image:width. The rest of the post is the May 25, 2026 text.

Google published a Search Central case study in which a site called Kirbie's Cravings added one line to its robots meta tag and saw its click-through rate rise 79%; its testimonial credits click-through from Discover. The change was not a content edit, a schema rollout, or a Core Update side effect - it was a robots directive that turned on full-size image previews. Google's own data, Google's own publishing surface, Google's own framing.

If you do not have that directive set, and if your hero images are below 1200 pixels wide, your pages can still appear in Discover, but not with large image cards. The February 2026 Discover Core Update - which shifted Discover audiences dramatically in the same three-week window - did not punish or reward any of those sites for their image setup. It could not. They all had it right. The image signals shape the card, not the ranking.

This post is for everyone who has ever asked "we did all the SEO and we still get no Discover traffic - what is missing?" The answer, for a meaningful share of sites we audit, is two HTML tags.

Key Takeaways

  • Google's Discover documentation recommends large images: at least 1200 pixels wide, 16x9 aspect, more than 300,000 total pixels, with max-image-preview:large or AMP enabled. They are recommendations for large image cards, not requirements: indexed content that meets Discover's content policies is eligible, and no special tags or structured data are required.
  • The robots directive is not Discover-only - it is Search-wide. Google's robots meta tag specification documents it as controlling image preview rendering across Search, Google Images, Discover, and Google Assistant. Discover's documentation lists it, with AMP, as a way to enable large images.
  • The February 2026 Discover Core Update did not punish or reward sites for image setup. Winners and losers both had compliant images. Image signals shape the card; content signals decided the ranking. See our writeup of the February rollout for the redistribution data.
  • Most CMS defaults still ship without the robots directive set. Most editorial workflows still serve hero images at 800 px or 1024 px because that is what the layout uses. The fix is small. The cost of skipping it is a smaller default card in Discover.
  • This is the cleanest case in the audit catalogue where "your SEO is fine, but your Discover cards are small" is true and fixable in one sprint.

What Google's Discover Docs Actually Say

The Google Discover documentation is short, and its image advice is shorter. Google recommends large, relevant images at least 1200 px wide, with more than 300,000 total pixels and a 16x9 aspect ratio, and large previews enabled by the max-image-preview:large setting or by AMP. It also advises against generic images such as a site logo, and against text-heavy images.

These sit in a list of recommendations for making content more likely to appear in Discover. The same page says content indexed by Google that meets Discover's content policies is eligible, and that no special tags or structured data are required.

The page does not say how much large images help. Google's case study gives two data points: after adopting the meta tag, Kirbie's Cravings' click-through rate rose 79% and Istoé's rose 30%. Its illustration contrasts the default thumbnail with large images in Discover. Those are two sites' results, not a general expectation.

Why the Robots Directive Is Search + Discover, Not Discover-Only

The temptation when reading the Discover docs is to file the max-image-preview:large directive under "Discover stuff" and forget about it for any site that does not run a publisher business. That framing misses the original purpose of the tag.

The robots meta tag specification frames max-image-preview as a Search-wide directive, not a Discover-only one. The documented purpose is to give publishers explicit control over how their images appear in Search rich results, including featured snippets, the image carousel, and the visual search surfaces. The same directive that enables large images in Discover controls the preview rendering across Search.

Without the directive, the specification says Google may show an image preview of the default size; large allows a larger preview, up to the width of the viewport. The rule applies to all forms of search results, Discover included, so a site without the directive does not allow large previews in Discover or in Search.

This is why our audit reports the directive as a "Search + Discover" signal, not "Discover-only". The large Discover card is one effect, the preview size in Search is another, and the same single line of HTML affects both.

Why 1200 Pixels Wide Is the Threshold (And Why "Big Enough" Is Not)

We see a lot of sites that serve hero images at 800 px or 1024 px and assume they are "modern-resolution enough" for Google. They are not. The 1200 px number is not a Google opinion about quality. It is the threshold Google's docs name, and it is the threshold below which Discover stops rendering the full-size card.

One piece of context is our own reading, not something Google's docs state: the 1200 px number lines up with the Open Graph 1200x630 social-sharing convention, so sites that have a proper og:image for Facebook and Twitter sharing already have a 1200-wide image asset. The implication is that if your og:image:width is below 1200, you are also serving a sub-optimal social share card to every other platform that consumes Open Graph. Discover names the number explicitly, but the same fix improves LinkedIn previews, Slack unfurls, iMessage cards, and AI citation panels that consume og:image.

The other recommendations (16x9 aspect, >300,000 total pixels, no generic images such as a logo) are downstream. If you nail 1200 wide and use a 1280x720 hero image (Google's own example), you are at 16x9 and 921,600 pixels in one shot. The width number is the one to anchor on. The aspect and pixel-count constraints follow for free.

What February 2026 Taught Us About Image Signals

Our writeup of the February 2026 Discover Core Update covers the publisher redistribution in detail - the publisher list contracted from 172 unique domains to 158, the rollout took 22 days, and Discover traffic patterns shifted dramatically across publisher categories. The piece worth pulling out here is the part that did not happen.

The major losers did not lose because they had bad images. They had proper og:image markup, proper 1200-wide hero photos, the robots directive enabled. So did the major winners. Post-rollout analyses across multiple sources converge on the same finding: image signals were not the differentiator.

What did differentiate winners from losers was the content layer - predicted engagement signals, content originality, editorial freshness, regional relevance. The February update reweighted those. Image signals stayed where they were, doing what they had always been doing: deciding how large a site's cards could be.

The takeaway for everyone outside the top-tier publisher set: content signals decided this update, and image setup did not. Large images are still worth setting up, because they change how your cards look in Discover, but missing them does not keep a page out of Discover.

Why This Is Not "SEO Optimization"

A lot of audit reports lump every Google surface together under "SEO" and treat Discover signals as a footnote. The framing is misleading.

Search optimization is about matching a query - keyword targeting, intent matching, ranking against competing pages for an explicit user input. There is a query string; there is a SERP; there is a measurable position. The optimization loop is well-understood and has been the same loop for two decades, even with the AI Overviews layer on top.

Discover has no query. There is no keyword to target, no intent to match against, no SERP to position on. The algorithm guesses what each individual user is likely to engage with, given their interests and recent behavior. Its signals differ from Search ranking signals. Google's post on the February 2026 Discover core update names three aims: more locally relevant content, less sensational content and clickbait, and more in-depth, original and timely content.

This means a site can be perfectly SEO-optimized and still get zero Discover traffic, because the surfaces use different signals and Google's large-image recommendations for Discover are signals that "good SEO" does not necessarily address. Most CMSes have an SEO plugin that handles meta titles, descriptions, canonical tags, and schema - and silently leaves the max-image-preview directive and og:image:width assertions on the table because those are not Search-ranking signals.

For sites in news, publishing, food, travel, lifestyle, ecommerce - anywhere Discover drives meaningful audience - closing this gap is the highest-leverage 30-minute fix available in 2026. Two HTML lines, one image upload pipeline check, and your pages can get large image cards in Discover. Search rankings do not improve. That is not the point. Large Discover cards are the point.

What Most Sites Get Wrong in Practice

We have audited enough sites in 2026 to call the patterns. Three failure modes account for almost all the missing large-image setups we see.

Failure mode 1 - Robots directive missing entirely. Most CMSes ship without max-image-preview set in the default robots meta tag. WordPress with Yoast does not set it. WordPress with Rank Math does not set it. Custom Jamstack stacks usually do not set it. Sites that set robots directives explicitly almost always set them for indexing intent (index/noindex, follow/nofollow) and leave the preview directives blank, defaulting to small. The fix is one line in the head template. The cost of skipping it, for a publisher-style site, is the large image card in Discover and larger previews in Search.

Failure mode 2 - og:image declared but width below 1200. Editorial workflows often pick whatever image asset the layout uses (800 px wide, 1024 px wide) and pipe it into the og:image meta tag. The image is good quality. It looks fine in the layout. It is below the 1200 px Google recommends, so the page does not qualify for large images in Discover. The fix is to commission or render the hero image at 1200 wide minimum and reference that version specifically in og:image - even if the in-page layout uses a smaller version.

Failure mode 3 - og:image:width meta tag missing entirely. The og:image URL is set, the actual image file is 1600 wide on the CDN, but no og:image:width meta tag exists in the head. Nothing in the HTML then says how wide the image is, so an audit cannot confirm the 1200 px width without downloading the file. Facebook's image sharing guide says the width and height tags let its crawler render a shared image immediately, without downloading and processing it first. Google's Discover documentation does not mention the tag. The fix is to add <meta property="og:image:width" content="1200"> (and the matching height) alongside the og:image URL.

All three failures are visible from outside the site, in the static HTML, with no JavaScript execution needed. Any audit that parses the head can detect them. The fact that audits routinely miss them is a framing problem, not a detection problem - they get filed under "OG tags" or "social sharing" and treated as nice-to-have, when they decide whether a page can get large image cards in Discover.

How to Verify Your Site

Open the page in a browser, view source, and search the head for:

  1. max-image-preview:large - should appear inside a <meta name="robots" content="..."> tag, alongside any existing directives (e.g. index, follow, max-image-preview:large). If your robots meta tag exists but does not contain that token, you are exposed. If the robots meta tag is entirely absent, Google may show an image preview of the default size - same effect.

  2. og:image:width meta tag - should appear with a content value of 1200 or larger on article-like and homepage URLs. If it is under 1200, the image is below the size Google recommends for large Discover images; if it is absent, an audit cannot confirm the width from the HTML.

  3. The actual image file - open the og:image URL directly in a browser. Check the displayed image dimensions (right-click → inspect, or use any image tool). The file itself needs to be 1200 wide or larger; declaring 1200 in the meta tag while serving an 800-pixel JPEG does not help.

If you are running an audit pipeline, both signals can be checked statically without rendering JavaScript. Our audit tool surfaces them as separate findings - one for the width threshold, one for the robots directive - because they fail independently in production and they need separate fixes from different teams (image pipeline vs. head template). When both fail, the fix is two commits, usually in two repos.

What Changes Next

The image signals we cover here are Google's recommendations as of 2026-05. They may change, so check the Discover documentation before you resize an image pipeline.

Start with the two recommended signals: get the directive set, and get the width to 1200 px or more.

Try It On Your Site

Two signals, three failure modes, one set of fixes. The cost of skipping is a smaller default card in Discover. The cost of fixing is two HTML tags and a hero-image-pipeline adjustment. We run both checks as part of every audit on hybridranking.com - the result tells you in seconds whether your pages are set up for large image cards, and which of the three failure modes (if any) applies to you. The audit is free and runs on any public URL.

Pair this writeup with our coverage of the February 2026 Discover Core Update for the redistribution data: the publishers who gained significantly in Discover did not crack a new ranking factor - they had image setup right and benefited from a content-signal reweighting. The publishers who lost by similar amounts also had image setup right; they lost on a different axis. Whether you win or lose the next reweighting depends on the content layer. How large your cards can be depends on the two image signals here.

The HybridRanking Advantage

See What AI Search Sees on Your Page

Run a free audit: AI crawler access, structured data, content structure and technical SEO, with a fix for every issue.