Google Discover's Visual Policy: Minimum Pixel Requirements Explained

Google Discover's visual policy indicates that to showcase your content in Discover's feed with large, eye-catching visual cards, images need to be at least 1200 pixels wide, and the page must have max-image-preview:large permission. In short, to have your content prominently featured in Discover with a large image, you must use a high-quality, original, and relevant main image that is at least 1200 px wide, and you should not restrict search engines from providing a large image preview.

This issue is not just about image size. Unlike traditional search results, Google Discover suggests content based on user interests. Therefore, factors like title, topic authority, page experience, mobile compatibility, E-E-A-T signals, and image quality are all evaluated together. However, one of the strongest factors determining click-through rates in Discover is still the image. A small, blurry, irrelevant, or restricted image can limit even well-written content's performance in Discover.

In this guide prepared for the Hostragons blog, we will systematically cover Google Discover's visual policy, minimum pixel requirements, technical tags, WordPress and custom software applications, performance impacts, and common mistakes in alignment with 2026 SEO expectations. Additionally, you will find natural linking suggestions to relevant resources such as Hostragons Web Hosting Solutions, SSL Certificate Products, and Domain Registration to strengthen your website’s visual SEO, speed, and security infrastructure.

What is Google Discover and Why Are Images So Important?

Google Discover is a personalized content feed that users encounter without searching, appearing in the Google app, on the Android home screen, or in mobile browser experiences. User search history, interests, location, followed topics, and interaction behaviors all play a role in shaping this feed.

Since users do not enter a query in Discover, a simple keyword match, as in traditional SEO, is not enough. The relevance, timeliness, authority, and presentation of your content matter. The image is the first point of contact here. Often, users look at the image before reading the title. Therefore, a large, clear, and contextually appropriate image can increase the click-through rate, time spent on the page, and brand recall.

Particularly in competitive fields such as news, technology, finance, health, travel, software, e-commerce, and digital marketing, visibility in Discover can lead to significant traffic. However, this traffic is not guaranteed. Google does not provide a manual submission system for inclusion in Discover. Content must be technically sound, trustworthy, and valuable to users.

What Does Google Discover's Visual Policy Require?

There are two critical conditions at the core of Google's large image recommendations: the image must be of sufficient width and permission must be granted to Google for large previews. The most overlooked point is this: simply uploading an image that is 1200 px wide is not enough. If your page restricts large image previews through a robots meta tag or HTTP header, Google may use a small image in the Discover card or may evaluate the content less favorably.

Minimum Pixel Requirement: At Least 1200 Pixels Wide

Images recommended for Discover must be at least 1200 pixels wide. The critical term here is width. Therefore, a vertical image with dimensions of 800x1200, even though it technically has a height of 1200 px, is not ideal for larger horizontal previews because its width is only 800 px.

In practice, the safest usage scenarios are:

• 1200x675 px: Ideal for news, blog, and technology content in a 16:9 ratio.
• 1280x720 px: Suitable for video cover images or guide content.
• 1600x900 px: A safe option for sites requiring higher quality.
• 1200x800 px: Can be used for more editorial or product-focused content.
• 1920x1080 px: Though good in quality, the file size must be optimized.

The minimum 1200 px requirement is a baseline for the image to be used as a large card in Discover. However, not only size but also clarity, compression quality, topic alignment, and the image's position on the page are important.

What is max-image-preview:large?

max-image-preview:large is a robots meta directive that informs Google it can use large previews of the images on the page. It can be used in the head section of the page as follows:

<meta name='robots' content='max-image-preview:large'>

Alternatively, it can also be implemented server-side through the X-Robots-Tag HTTP header:

X-Robots-Tag: max-image-preview:large

The purpose of this directive is to allow Google to use larger images in content previews. If your site has max-image-preview:none or a more restrictive setting, Google may not use the image in large card format. Therefore, SEO plugins, custom theme files, CDN settings, and security headers should all be checked together.

Minimum Image Size Comparison Table

You can think of this table as a practical checklist. If you want to provide editors with a single standard during your content production process, setting 1200x675 px or 1600x900 px as the default cover image format is generally sufficient.

How to Choose the Ideal Image for Google Discover?

While the pixel dimensions of the image meet the technical requirement, editorial quality is also necessary for success in Discover. Google clearly states that misleading, sensational, or non-representative images weaken the user experience. Therefore, the following principles should be applied in image selection:

• The image should directly represent the main topic of the page.
• If using stock images, avoid overly generic images seen on every site.
• The image should not contain unnecessary text, heavy logos, or clickbait elements.
• Images of human faces, product details, interface screenshots, or real-life usage scenes can perform better contextually.
• The cover image should not be blurry, pixelated, dark, or overly compressed.

For instance, instead of using just an abstract rocket image in an article about “WordPress speed optimization,” a unique cover that combines PageSpeed Insights screens, server performance graphs, and an optimized WordPress dashboard would be more meaningful. Similarly, contextual images like server infrastructure, data centers, speed tests, or control panels can create more reliable signals in Discover for content related to hosting. At this point, linking to supportive content, such as What is WordPress Hosting and Website Acceleration Guide, can enhance the topic cluster.

Technical Implementation: Is Your Page Ready for Discover?

For a page to be displayed with a large image in Google Discover, simply uploading the right image is not enough. The theme, robots tag, image URL, indexability, mobile experience, and page speed must all be checked together.

1. Check the Robots Meta Tag

The page's source code must contain a robots meta tag that does not prevent large image previews. The simplest safe structure is:

<meta name='robots' content='index, follow, max-image-preview:large'>

If the page has a noindex, you should not expect visibility in Discover. Additionally, if multiple robots tags are used, conflicts may arise. For example, if the theme generates one tag and the SEO plugin generates another, Google may consider the more restrictive signal. Therefore, the source code should be manually reviewed.

2. Place the Main Image at the Top of the Page

The main image intended for Discover should be visible in a relevant way when the user opens the page. It may not be sufficient for the image to only be present in social media meta tags. The cover image should consistently appear on the page with the title and introductory paragraph.

For WordPress sites, check whether the featured image is actually rendered on the page by the theme. Some themes display the featured image on the listing page but not on the post detail page. In this case, Google may not evaluate the image strongly enough in context.

3. Complete Open Graph and Twitter Card Tags

Open Graph tags are not directly decisive for Discover; however, they are important for social sharing, preview consistency, and content signals. Especially using an image at least 1200 px wide in the og:image field is a good practice.

The recommended essential fields are:

• og:title
• og:description
• og:image
• og:url
• twitter:card

These fields help ensure that the content appears correctly with the right image across different platforms. It is also important for brand consistency that your domain name is reliable, short, and memorable. If you are setting up a new project, Domain Query and Domain Registration Guide can be useful at this stage.

4. Keep the Image URL Crawlable

Image files should not be blocked by robots.txt. If your /wp-content/uploads/ or custom media directory is closed to crawling, Google cannot process the image. Similarly, if you are using hotlink protection or signed URLs on your CDN, Googlebot access should be tested.

You can follow these steps to check:

• Open the image URL in an incognito tab.
• Ensure the HTTP status code is 200.
• Check that the media directory is not blocked in the robots.txt file.
• Verify that the CDN firewall is not blocking Googlebot.
• Test the page's crawlability with the Search Console URL Inspection tool.

Balancing Visual SEO and Performance

Using large images for Discover does not mean uncontrollably increasing the image file size. A 1920x1080 px PNG image that is 3 MB can lead to slow loading for mobile users and disrupt the LCP metric. Since Google Discover traffic largely comes from mobile devices, performance is critically important.

File Format: Prioritize WebP and AVIF

As of 2026, WebP and AVIF formats are widely used in modern web projects. JPEG is still supported, but WebP often provides smaller file sizes at the same quality level. AVIF can offer better compression, but your production line must be correctly configured for browser compatibility and fallback support.

Practical recommendations:

• Use WebP or AVIF for photo-heavy images.
• If transparency is needed, prefer WebP or optimized PNG.
• Ensure text readability in screenshots.
• Aim for a file size between 150-300 KB for cover images; up to 400 KB may be acceptable for complex images.

These values are not absolute rules; however, they serve as a good starting point for mobile performance. Sites using more intensive media require strong server, caching, and CDN configurations. Linking to content like High-performance hosting and CDN Usage provides additional value to the user.

Be Cautious When Using Lazy Load

Lazy loading improves page performance; however, if misapplied to the main image at the top, it can worsen LCP times. The cover image that appears above the fold should often not be lazy-loaded, or it should be loaded with high priority.

Applicable checklist:

• Do not apply unnecessary lazy loading to the cover image.
• Consider using fetchpriority='high' for the above-the-fold image.
• Specify the width and height values for the image.
• Pre-allocate space for the image to avoid CLS issues.
• Use responsive srcset appropriate for the actual displayed size on mobile.

These settings should be made by the technical team within theme or frontend components. Especially for sites using custom software, the developer, SEO expert, and content team should share the same visual standard.

Google Discover Large Image Settings for WordPress Sites

On WordPress sites, Discover images are typically managed through the combination of featured images, SEO plugins, and theme settings. The first step is to define a featured image at least 1200 px wide for each post. The second step is to verify that your SEO plugin generates the max-image-preview:large value in the robots meta field.

Implementation steps:

• Set the default cover image size to 1200x675 px or 1600x900 px.
• Check the search engine visibility settings in your SEO plugin.
• Verify the max-image-preview:large directive in the post source code.
• Ensure the featured image is visible on the post detail page.
• Name the image file descriptively: google-discover-large-image-policy.webp, for example.
• Create alt text that is natural and accessibility-focused.

Alt text should not be used for keyword stuffing. For example, a descriptive phrase like “Example of a cover image 1200 pixels wide for Google Discover” is healthier in terms of both accessibility and visual context.

If images are loading slowly on your WordPress site, if the media library becomes sluggish as it grows, or if you experience interruptions during traffic spikes, the infrastructure side should also be reviewed. In this context, links to WordPress hosting packages and WordPress Security Guide can guide the user correctly.

Implementation Standards for Custom Software and Corporate Sites

Corporate websites, news portals, or SaaS blogs typically use custom CMS solutions. In these structures, visual validation rules should be defined in the content management panel for Discover compliance. The system should alert the editor or not allow the upload when an image of 900 px width is uploaded.

Recommended technical standards:

• Cover image minimum width check: 1200 px.
• Recommended ratio: 16:9.
• Automatic WebP or AVIF conversion.
• Creation of compressed variations of the original image.
• Providing mobile, tablet, and desktop variants with srcset.
• The robots meta field should contain max-image-preview:large at the template level.
• Image URLs should be accessible with a 200 status code via CDN.

These standards benefit not only Discover but also overall visual SEO, Core Web Vitals, and the quality of social media sharing. Testing in a staging environment during the development process reduces surprise issues on pages that will go live. For corporate projects, Corporate Hosting Solutions and SSL Certificate Installation can be recommended for a secure publishing environment.

E-E-A-T Signals Affecting Discover Visibility

While image quality is important in Google Discover, it is not sufficient on its own. Especially in topics that could be considered YMYL, such as health, finance, law, and security, expertise and trust signals are more significant. The 2026 SEO approach considers E-E-A-T as a combination of experience, expertise, authority, and trust.

To make content more suitable for Discover, the following elements should be strengthened:

• Author name, area of expertise, and a short biography should be present.
• The content's update date should be clearly shown.
• Concrete examples, screenshots, and measurements should be used.
• Avoid exaggerated or misleading headlines.
• Maintain source citation and technical accuracy.
• Ensure HTTPS, fast loading, and secure browsing across the site.

For example, in a claim-based content piece like “The best hosting company,” instead of using only marketing phrases, providing measurable criteria such as uptime rates, support duration, NVMe disk usage, backup frequency, SSL support, and real performance tests creates a more trustworthy approach. This also contributes to organic search performance outside of Discover.

Common Mistakes and Solutions

Errors made in Google Discover's large image policy often stem from small technical details. The following issues reduce Discover potential for many sites:

• Image width falling below 1200 px: As a solution, establish an editorial upload standard.
• Missing max-image-preview value: Check the robots meta tag in the source code.
• The cover image not appearing on the page: Adjust the theme template.
• Image being blocked by robots.txt: Allow crawling permissions for media directories.
• Excessively large file size: Use WebP, AVIF, CDN, and compression.
• Using irrelevant stock images: Create topic-specific, original, and descriptive images.
• Misleading title-image mismatch: Avoid clickbait that undermines user trust.

To prevent these mistakes, a pre-publication SEO quality control checklist should be created. If the editor, SEO expert, and developer use the same control form, both Discover and overall organic performance will become more stable.

Pre-Publication Google Discover Image Checklist

You can apply the following list to every new piece of content:

• Is the main image at least 1200 px wide?
• Is the image preferably in a 16:9 ratio?
• Is the file size at a level that will not hinder mobile performance?
• Is max-image-preview:large present in the page source code?
• Is the page in index, follow status?
• Is the image URL accessible by Googlebot?
• Is the featured image visible in the post?
• Is the alt text descriptive and natural?
• Is the Open Graph image the same high-quality image?
• Does the page load quickly on mobile without layout shifts?

Although this list may seem short, it is highly valuable for Discover visibility. Especially for blogs producing intensive content, applying the same standard with each publication will strengthen quality signals over time.

Conclusion: Large Images, Technical Permissions, and Quality Must Be Considered Together

Using large images for Google Discover is not just about enlarging the cover image. A minimum width of 1200 px, max-image-preview:large permission, quickly loading optimized files, mobile compatibility, reliable content, and contextually relevant image selection all work together. If any of these elements are missing, Discover performance may be limited.

If you want to improve your website's Discover and overall SEO performance, first clarify your content and image standards, then strengthen technical foundations such as hosting, SSL, CDN, and caching. Hostragons’ hosting, domain, and SSL solutions can help you manage this infrastructure securely and sustainably. For better performance, regularly measure your site, optimize your images, and continue producing content that truly offers value to users.

Frequently Asked Questions

What is the minimum image width for Google Discover?

Images recommended for Google Discover must be at least 1200 pixels wide. The most practical sizes are 1200x675 px, 1280x720 px, and 1600x900 px formats.

Is the max-image-preview:large tag mandatory?

Using max-image-preview:large is crucial for allowing large image previews. Without this tag or if there is a more restrictive robots setting, Google may not use your image as a large card in Discover.

Is a 1200 px image sufficient to appear in Google Discover?

No. While 1200 px width is a technical requirement, it is not sufficient on its own. The quality of the content, E-E-A-T signals, mobile performance, indexability, and user interest also affect Discover visibility.

Does using WebP or AVIF create issues for Discover?

When configured correctly, using WebP and AVIF does not create issues. On the contrary, they can enhance mobile performance due to smaller file sizes. However, you must ensure that the images are accessible by Googlebot.

How to set up large images for Discover in WordPress?

In WordPress, you must use a featured image at least 1200 px wide for each post, verify that your SEO plugin generates max-image-preview:large, and ensure that your theme displays this image on the post detail page.