Do big images really enhance your visibility in Google Discover?

Why does Google focus on visuals in Discover?

Discover operates like a stream of personalized recommendations, not like a classic SERP. The user isn’t searching for anything—they’re scrolling.

In this context, the visual hook becomes the primary click criterion. A striking image catches the eye even before the title is read. This logic is similar to social media, where the format dictates engagement.

What does "large image" mean for Google?

Mueller remains vague. Google officially recommends images that are at least 1200 pixels wide to trigger the large display in Discover.

The 16:9 or 4:3 ratio seems to be favored. However, there is no clear confirmation on the maximum tolerated weight or the impact of formats like WebP or AVIF—crucial for performance nonetheless.

Does this recommendation apply to all content?

Not really. Discover already prefers certain types of content: news, visual tutorials, recipes, lifestyle. A technical B2B site has little chance of appearing regardless of the image size.

Discover traffic remains volatile and difficult to predict. Some sites lose 80% of their Discover traffic overnight, without explanation. Relying solely on this would be risky.

• Images ≥ 1200 px trigger large display in Discover
• The 16:9 or 4:3 ratio seems optimal for visual engagement
• Discover favors lifestyle content, news, tutorials—not technical B2B
• Discover traffic is volatile: never make it the primary source
• No clear specs on weight, compression, next-gen formats (WebP, AVIF)

Is this statement consistent with field observations?

Yes, but with a big caveat: the impact varies greatly by sector. Lifestyle, food, and travel sites see measurable effects. Corporate, SaaS, and finance sites? Almost none.

We have observed sites that quadrupled their image sizes and saw their Discover traffic increase by 30-40%. Others saw absolutely no difference. The type of content and domain authority seem to be just as influential as the visuals.

What nuances should be considered?

Google doesn’t say, "Put up large images and you’ll appear in Discover." It says: "If you are in Discover, large images perform better." That’s a significant nuance.

Another point: increasing image sizes impacts Core Web Vitals, particularly LCP. If you go from 800 px to 1600 px without optimizing compression and lazy loading, you’ll hurt your performance. [To be verified] whether Google adjusts its Discover algorithm to account for this trade-off.

In what cases does this rule not apply?

If your site doesn’t produce “discoverable” content—news, tutorials, lifestyle—don’t waste your time. Discover does not crawl the entire web, it follows specific content patterns.

Similarly, if your Discover traffic is already at zero: optimizing images won’t miraculously trigger appearance in the feed. Google first needs to consider your content relevant to its recommendation algorithms. And there, we have almost no visibility into the exact criteria.

What steps should be taken to optimize images concretely?

First, identify if your site has Discover potential. Check your Search Console, “Discover” section. If you already have traffic, even if low, it’s worth optimizing. Otherwise, focus on other levers.

Next, upgrade your images: minimum 1200 px wide, 16:9 or 4:3 ratio, aggressive compression (WebP, or AVIF if your stack permits). Use srcset to serve the appropriate size for the screen. And test the impact on your LCP—if it worsens, adjustments are needed.

What mistakes should be avoided?

Avoid putting huge images everywhere without discretion. Target contents eligible for Discover: news articles, visual guides, recipes, DIY. No need to oversize the image for a terms and conditions page.

Also, avoid neglecting alt tags, title tags, and schema markup ImageObject. Google uses these signals to understand the visual context. A 2000 px image without relevant alt text is a missed opportunity.

How can I check if my site is compliant?

Inspect your key articles with the Lighthouse tool: check image weight, format, and lazy loading. PageSpeed Insights will tell you if your LCP is degraded by visuals.

Monitor the Search Console, Discover tab: if your traffic stagnates or drops after a visual upgrade, it’s a sign that the performance/size trade-off isn’t optimal. Adjust accordingly. Let’s be honest: these optimizations require a solid technical workflow—automated compression, CDN with on-the-fly resizing, continuous monitoring. If your team lacks the infrastructure or time, engaging a specialized SEO agency for an audit and personalized support can significantly accelerate results.

• Check existing Discover traffic in Search Console before investing time
• Upgrade key images: ≥ 1200 px, 16:9/4:3 ratio, WebP or AVIF format
• Implement srcset and lazy loading to preserve LCP
• Complete alt tags, title tags, and structure with schema.org ImageObject
• Test impact on Core Web Vitals with Lighthouse and PageSpeed Insights
• Monitor Discover traffic changes over 4-6 weeks post-optimization