Official statement
Other statements from this video 8 ▾
- 1:00 Search Console Insights : Google unifie-t-il enfin Analytics et Search Console pour les SEO ?
- 2:08 Comment exploiter le nouveau filtre actualités de Search Console pour optimiser vos performances ?
- 2:08 Faut-il vraiment implémenter tous les nouveaux types de données structurées supportés par Google ?
- 2:39 Faut-il vraiment migrer vers les propriétés de domaine dans Search Console ?
- 2:59 Comment Google Images exploite-t-il le balisage des images sous licence ?
- 4:41 Faut-il maîtriser Python pour être un bon SEO ?
- 5:43 Pourquoi Google a-t-il repoussé le passage définitif au mobile-first et que risquez-vous vraiment ?
- 5:43 Les sitemaps par défaut dans WordPress Core changent-ils vraiment la donne pour le SEO ?
Google confirms that large image previews in Discover can be activated either through AMP or simply by using the max-image-preview:large attribute in the robots meta tag. This second option avoids the need for AMP migration while maximizing visual visibility. In practical terms, adding a single line of code is enough to make your content stand out in the Discover feed.
What you need to understand
Why does Google provide two methods to activate these large previews?
Google has long pushed AMP as the preferred solution for optimizing display in Discover. The AMP technology ensures ultra-fast loading and standardized rendering, but its implementation remains heavy and constraining for many sites.
The robots meta tag with max-image-preview:large offers a much lighter alternative. It allows Google to display large image previews without requiring a technical overhaul. This is a victory for teams that refused AMP on principle or due to a lack of resources.
What is the real difference between a standard preview and a large preview?
In the Discover feed, the standard preview displays a small square or rectangular thumbnail, often cropped. The large preview, on the other hand, occupies the full width of the mobile screen and showcases the image spectacularly.
This increased visual area significantly boosts the click-through rate (CTR) — some publishers report increases of 20 to 40% on their highlighted articles. The differential relies entirely on visual impact: a stunning full-width photo captures attention, while a small thumbnail goes unnoticed.
How to implement max-image-preview:large without disrupting existing setups?
The addition of this directive is done in the meta name="robots" tag within the <head> of your pages. If you already have a robots meta tag (index, follow, etc.), you just need to add max-image-preview:large separated by a comma.
However, be cautious: this directive allows Google to display large previews, but it does not guarantee they will always be used. Google retains the final decision based on image quality, content relevance, and estimated engagement.
- AMP is no longer mandatory for enjoying large previews in Discover
- The max-image-preview:large directive must be placed in the robots meta tag of the
<head> - Site-side activation does not guarantee the large display — Google decides on a case-by-case basis
- Images must be high quality and at least 1200px wide to maximize chances
- This optimization only applies to Discover, not to traditional search results
SEO Expert opinion
Is this statement consistent with the practices observed in the field?
Yes, and it’s quite a pleasant surprise. For a long time, Google maintained ambiguity about alternatives to AMP for Discover. Many SEO professionals still thought AMP remained a mandatory prerequisite for accessing large previews.
In reality, field tests show that max-image-preview:large has been working effectively for several months. Some non-AMP sites regularly appear with full-width images in Discover. This statement therefore formalizes a practice that was already operational but poorly documented.
What are the unspoken limitations of this optimization?
Google does not specify the exact eligibility criteria for Discover, nor the actual weight of the large preview in the feed ranking. Adding the directive alone is not enough to make your content appear — you must first be selected by the algorithm. [To be verified]
Additionally, the impact of the image format remains unclear. Google recommends a minimum width of 1200px, but some publishers report better results with 16:9 aspect ratio images rather than 4:3 or square. No official guidelines settle this debate, leaving the door open for experimentation.
In what cases is this recommendation pointless?
If your site has no chance of being eligible for Discover — for example, a transactional e-commerce site, a directory, or an ultra-niche blog with zero engagement signals — implementing max-image-preview:large will change nothing.
Discover prioritizes editorial content, news, visual tutorials, and topics with high viral potential. If your Discover traffic is non-existent and you lack a mobile-oriented editorial strategy, focus your efforts elsewhere. Specifically: first check in Google Search Console if you are receiving Discover impressions before diving in.
Practical impact and recommendations
What steps should you take to enable this feature?
The first step is to add or modify the robots meta tag in the <head> of your eligible pages. If you are using WordPress, an SEO plugin like Yoast or Rank Math can do this globally or on a page-by-page basis.
Then, ensure that each targeted content has a high-quality featured image at least 1200px wide. Prioritize eye-catching visuals, well-framed and relevant to the topic — Google values engagement, not just size.
What mistakes should be avoided during implementation?
Do not block the indexing or crawling of your images in the robots.txt. If Googlebot can’t access the images, the max-image-preview:large directive will have no effect. Also check that your images are not overly lazy-loaded, which can prevent their detection.
Another classic pitfall: duplicating robots meta tags or using contradictory directives (such as noindex + max-image-preview:large). Google ignores the preview directive if the page is not indexable. Audit your tags before deploying.
How to measure the impact of this optimization?
Google Search Console offers a dedicated report for Discover in the Performance section. Check it regularly to track your impressions, clicks, and CTR. Compare the performances before/after activating the directive.
If you notice an increase in CTR without an increase in impressions, that’s a good sign — the large preview is doing its job. If nothing changes, dig into editorial quality or engagement: Discover does not reward purely technical optimizations; it first values content that captivates.
- Add max-image-preview:large to the robots meta tag in the
<head> - Ensure your images are at least 1200px wide and well optimized (WebP, compression)
- Confirm that images are not blocked in robots.txt or overly lazy-loaded
- Check for the absence of contradictory directives (noindex, nofollow mistakenly applied)
- Monitor performance in Google Search Console > Discover to measure real impact
- Test different image formats and ratios to identify which perform best
❓ Frequently Asked Questions
Faut-il obligatoirement avoir une version AMP pour profiter des aperçus larges dans Discover ?
Quelle taille d'image minimale est recommandée pour les aperçus larges ?
L'activation de max-image-preview:large garantit-elle l'affichage large dans Discover ?
Cette optimisation s'applique-t-elle aussi aux résultats de recherche classiques ?
Peut-on activer cette directive uniquement sur certaines pages du site ?
🎥 From the same video 8
Other SEO insights extracted from this same Google Search Central video · duration 7 min · published on 29/09/2020
🎥 Watch the full video on YouTube →
💬 Comments (0)
Be the first to comment.