Official statement
Other statements from this video 6 ▾
- 10:35 Le nofollow est-il vraiment devenu un simple indice pour Google ?
- 15:37 Pourquoi mon site perd-il des positions sans avoir été pénalisé ?
- 24:35 Le contenu de qualité suffit-il vraiment à ranker sur Google ?
- 42:01 Le duplicate content déclenche-t-il vraiment une pénalité Google ?
- 46:50 Faut-il abandonner les URLs mobiles séparées pour votre stratégie SEO ?
- 85:42 Google gère-t-il vraiment les demandes de suppression d'informations personnelles sur les sites tiers ?
Google claims that the max-image-preview attribute set to large can enhance the display of large images on Discover. This often overlooked meta tag controls the size of visual previews in rich results. Without it, your visuals might appear as tiny thumbnails — which can significantly harm the CTR on such a visual platform as Discover.
What you need to understand
Why does Google condition the size of Discover images on a meta attribute?
Discover works like a personalized news feed where visuals take precedence. Google displays content it deems relevant to the user, without an explicit query. The display area heavily relies on the impact of images: a large photo attracts attention, while a thumbnail goes unnoticed.
The max-image-preview attribute is a meta robots tag that tells Google which preview size you allow for your images in search results, rich snippets, and feeds like Discover. There are three possible values: none (no preview), standard (classic thumbnail), large (large image). By default, if you don’t specify anything, Google applies standard — and you limit your visibility on Discover.
How does this tag interact with other robots directives?
The max-image-preview attribute is part of the meta robots tags family, alongside noindex, nofollow, or max-snippet. It should be placed in the <head> of the page or can be returned through the HTTP header X-Robots-Tag. Unlike noindex, which blocks indexing, max-image-preview does not affect crawling or ranking — it only concerns the visual presentation in the results.
Google adheres strictly to this directive. If you set max-image-preview:standard, even if your image is technically usable in high resolution, Discover will only display it in a small format. This is an editorial choice of the webmaster — some sites prefer to limit the size of previews to protect their visual content or force clicks.
Which types of sites are affected by this attribute?
All sites eligible for Discover — mainly media, blogs, online magazines, and news sites. If your content is indexable, you publish regularly, and your pages meet the E-E-A-T quality criteria, you can appear in Discover. However, without max-image-preview:large, your content risks losing attractiveness against competitors displaying full-width visuals.
E-commerce, SaaS, or institutional sites are less affected — Discover favors fresh and engaging editorial content. However, if you operate a corporate blog with in-depth articles, activating this directive remains relevant to maximize the exposure of your content in this feed.
- max-image-preview:large allows the display of large images on Discover and in rich results.
- By default, without an explicit directive, Google applies max-image-preview:standard (reduced thumbnails).
- This meta tag is placed in the
<head>or via the HTTP header X-Robots-Tag. - It does not affect crawling, indexing, or ranking — only the visual presentation.
- Editorial and media sites are the primary beneficiaries of this optimization.
SEO Expert opinion
Is this statement consistent with field observations?
Yes, absolutely. Tests on news sites show a direct link between enabling max-image-preview:large and the appearance of large images on Discover. Sites that migrated from standard to large noted a marked improvement in their CTR on this feed — logical, since a large-format visual grabs more attention than a thumbnail.
That said, enabling this tag does not guarantee that all your images will display in large format. Google applies quality criteria: minimum resolution (recommended 1200px wide), visual relevance, and absence of intrusive watermarks. If your image is blurry, too small, or unrelated to the content, it will not benefit from the large format even if you have the directive.
What nuances should be added to this statement?
Google says "can allow," not "guarantees." It's a necessary but not sufficient prerequisite. Other factors come into play: the editorial quality of the content, its timeliness, the engagement it generates (dwell time, shares), and the site's reputation. Discover remains an opaque algorithm where the visual lever is important, but not isolated.
Another nuance: some publishers intentionally choose not to activate max-image-preview:large to protect their exclusive visuals. They prefer to display a thumbnail and force a click to the full site. It's a trade-off between immediate visibility and content control — there is no one-size-fits-all answer, it depends on your strategy.
In what cases can this directive pose a problem?
If you deal with paid visual content (photojournalism, stock photo sites, premium galleries), displaying large images in Discover amounts to giving away what you sell for free. Some photography or art sites have disabled this option for this specific reason — they want users to visit the site before seeing the full photo.
Be cautious of poorly optimized images. If you enable max-image-preview:large with uncompressed heavy files, you risk slowing down your page load times — and Discover penalizes slow content. Activating this directive must be accompanied by rigorous technical optimization: WebP, lazy loading, CDN, adaptive compression.
Practical impact and recommendations
What practical steps should you take to enable this feature?
Add the following meta robots tag in the <head> of your pages eligible for Discover: <meta name="robots" content="max-image-preview:large">. If you already use other robots directives (max-snippet, max-video-preview), group them in a single tag separated by commas: <meta name="robots" content="max-image-preview:large, max-snippet:-1">.
Alternatively, you can deploy this directive via the HTTP X-Robots-Tag header if your server configuration allows — useful for sites with non-HTML content or PDF files. Example: X-Robots-Tag: max-image-preview:large. This method is less common but more flexible on certain technical architectures.
What mistakes should be avoided during implementation?
Do not mix contradictory directives. If you already have a tag meta name="robots" content="noindex", adding max-image-preview:large will have no effect as the page is not indexed. Check the consistency of your robots directives before deploying.
Another common trap: enabling the directive without optimizing the images. If your visuals are 600px wide, Google won’t display them in large format even with max-image-preview:large. Aim for a minimum of 1200px in width for Discover to fully utilize the directive. Also consider the aspect ratio — images that are too narrow or too square perform poorly in the Discover feed which favors 16:9 or 4:3 formats.
How can you verify that the directive is being properly recognized?
Use the Search Console and the Discover tab (if your site generates traffic on this channel). Observe the evolution of CTR and impressions after activation — a significant gain indicates that your images are now displayed in large format. You can also inspect your pages with the URL Inspection tool to check that the meta tag is correctly detected.
Test as well with third-party tools like Screaming Frog or a custom crawler to validate that all your eligible pages carry the directive. A regular technical audit prevents regressions during template updates or migrations. Finally, monitor your Core Web Vitals — if displaying large images degrades the LCP, adjust compression and lazy loading.
- Add
<meta name="robots" content="max-image-preview:large">in the<head>of your pages eligible for Discover. - Ensure your images are at least 1200px wide and optimized in weight (WebP, adaptive compression).
- Avoid contradictory robots directives (noindex, none) that would nullify the effect of max-image-preview.
- Monitor the evolution of CTR and Discover impressions in the Search Console after deployment.
- Test the detection of the tag with URL Inspection or Screaming Frog.
- Keep an eye on Core Web Vitals to ensure that large images do not impact the LCP.
❓ Frequently Asked Questions
L'attribut max-image-preview:large affecte-t-il le classement dans les résultats de recherche classiques ?
Puis-je activer max-image-preview:large uniquement sur certaines pages ?
Quelle est la taille d'image recommandée pour bénéficier pleinement de cette directive ?
Cette balise fonctionne-t-elle avec les images en lazy loading ?
Dois-je aussi ajouter max-snippet et max-video-preview pour optimiser Discover ?
🎥 From the same video 6
Other SEO insights extracted from this same Google Search Central video · duration 1h02 · published on 02/10/2019
🎥 Watch the full video on YouTube →
💬 Comments (0)
Be the first to comment.