Official statement
Other statements from this video 28 ▾
- 4:42 Does the number of noindex pages really impact SEO rankings?
- 4:42 Can too many noindex pages really hurt your ranking?
- 6:02 Do 404 Pages in Your Structure Really Kill Your Crawl Budget?
- 6:02 Do 404 pages in a site's structure really hinder crawling?
- 7:55 Should you really be worried about having multiple sites with similar content?
- 7:55 Can you target the same queries with multiple websites without risking a penalty?
- 12:27 Should you really check the Webmaster Guidelines before every SEO update?
- 16:16 Does technical compliance really ensure good SEO?
- 19:58 How does redirecting from HTTPS to HTTP potentially derail your indexing?
- 19:58 Should you really remove all URL parameters from your pages?
- 19:58 Should you really declare a canonical tag on all your pages?
- 19:58 Why does redirecting from HTTPS to HTTP paralyze canonicalization?
- 21:07 Should You Really Ditch URL Parameters for 'Meaningful' Structures?
- 21:25 Should you really add a canonical tag on ALL your pages, even the main ones?
- 22:22 Is Google really struggling to differentiate between subdomains and main domains?
- 25:27 Is it really necessary to separate subdomains from the main domain for Google to recognize them distinctly?
- 26:26 Is Local Reputation Enough to Trigger Geolocalized Ranking?
- 29:56 Is it true that having different mobile and desktop content still gets penalized by Google after the Mobile-First Index?
- 29:57 Is it really possible to overlook the desktop version with mobile-first indexing?
- 43:04 Does the indexing API really ensure your pages are indexed immediately?
- 43:06 Does submitting an URL in Search Console really speed up indexing?
- 44:54 Why does Google consistently refuse to detail its ranking algorithms?
- 46:46 Should you really choose between geographical targeting and hreflang for your international SEO?
- 46:46 Geographical Targeting vs Hreflang: Do You Really Need to Choose Between the Two?
- 53:14 Should you really make all structured data images visible on your pages?
- 64:03 Is it really necessary to standardize final slashes in your URLs?
- 66:30 Should You Really Ignore Unresolved Errors in Search Console?
- 66:36 Should you worry about persistent resolved 5xx errors in Search Console?
Google states that marking non-visible images on the page with structured data violates its general guidelines. This practice, often used to artificially optimize display in rich results, is considered deceptive. Specifically, only images that are actually displayed to the user should be marked — marking others exposes you to manual or algorithmic penalties.
What you need to understand
What is an invisible image in structured data? <\/h3>
We refer to a hidden image when a webmaster adds a structured data tag (schema.org ImageObject, for example) for an image that never appears in the user’s viewport. This includes images with display:none<\/strong>, absolutely positioned off-screen, or loaded only for Google.<\/p> This technique has long been used to inject visuals optimized for rich snippets<\/strong> (recipes, products, articles) without affecting the actual layout. The problem? Google sees it as manipulation of search results.<\/p> The logic is simple: structured data must reflect what the user sees<\/strong>. If Google shows an image in its results that the visitor will never see when landing on the page, it’s a form of misrepresentation.<\/p> Google’s general guidelines for structured data require that the marked content is directly accessible and visible<\/strong>. Marking a hidden image violates this fundamental principle — and risks manual action or partial de-indexing of rich results.<\/p> All images marked via schema.org that are not visually rendered for the user<\/strong>. This includes images hidden by CSS, lazy-load images that never display, invisible sprites, or visuals in 1×1 pixel.<\/p> On the other hand, an image that uses lazy-load but ends up displaying<\/strong> on scroll remains compliant. The criterion is actual visual accessibility, not the technical timing of loading.<\/p>Why does Google ban this practice? <\/h3>
Which images are affected by this rule? <\/h3>
SEO Expert opinion
Is this rule really new or just a reminder? <\/h3>
Let’s be honest: this directive has been circulating in the guidelines for years. What’s changed is that Google is publicly reaffirming it<\/strong> — likely a sign of increasing abuse in certain verticals (e-commerce, recipes, articles).<\/p> On the ground, many sites continue to mark hidden images without visible penalties. [To be verified]<\/strong>: Does Google systematically detect this manipulation, or only during manual audits? The consistency between automatic detection and sanction remains unclear.<\/p> The real issue is the definition of “visible”<\/strong>. Is a lazy-load image that only loads when the user scrolls compliant? Yes, as long as it eventually displays. A CSS background image that only appears on mobile? Technically gray — but if it’s rendered somewhere, it’s acceptable.<\/p> The blurry area mainly concerns alternative images<\/strong>: for example, a site offering a desktop version and a mobile version with two different visuals, both marked. If one of the two never displays for a given user, is it a violation? Google does not make this clear.<\/p> Some SEOs inject 1×1 pixel transparent images<\/strong> at the top of the page, technically visible but imperceptible. Others use carousels or tabs with pre-loaded images in the DOM but not displayed by default.<\/p> These gray tactics do not strictly violate the rule — the image is technically rendered — but they betray its spirit. If Google detects a pattern of manipulation (image size vs. actual visibility), there’s no telling it won’t impose manual penalties. The risk exists, even if the probability remains low given the current state of detection.<\/strong><\/p>What nuances should be applied to this prohibition? <\/h3>
In what situations is this rule circumvented in practice? <\/h3>
Practical impact and recommendations
What should you do to remain compliant? <\/h3>
Start with an audit of marked images<\/strong>: collect all image URLs from your JSON-LD, Microdata, or RDFa, then verify that they actually appear in the user’s viewport. A simple script can cross-reference the structured data with the visible DOM.<\/p> Next, eliminate any images with display:none<\/strong>, off-screen CSS, or invisible sprites. If you use different images for desktop/mobile, ensure that the structured data markup corresponds to the version actually served — or adopt a single responsive image.<\/p> Never mark an image that exists only for Google. Some CMS or SEO plugins automatically generate default images<\/strong> (logo, placeholder) even when no image is displayed on the page — disable this logic.<\/p> Avoid marking images in carousels or tabs if only certain ones are displayed. Better to mark only the first visible one, or accept not having a rich snippet rather than risking a penalty.<\/p> Use Google’s rich results testing tool for each type of strategic page. Verify that the images shown in the report actually appear on screen<\/strong> when visiting the page in normal browsing.<\/p> A manual audit remains the most reliable: for each page with structured data, load it in incognito, inspect the marked images, and confirm that they are all visible without manipulating the DOM. If you detect discrepancies, correct them before Google does it for you.<\/p>What errors should be prioritized to avoid? <\/h3>
How can I verify that my site complies with this rule? <\/h3>
❓ Frequently Asked Questions
Une image en lazy-load est-elle considérée comme invisible par Google ?
Puis-je baliser une image qui apparaît uniquement sur mobile ?
Que risque mon site si je baise des images cachées ?
Les images en arrière-plan CSS sont-elles conformes pour les structured data ?
Comment vérifier rapidement si mes images balisées sont visibles ?
🎥 From the same video 28
Other SEO insights extracted from this same Google Search Central video · duration 1h13 · published on 22/04/2021
🎥 Watch the full video on YouTube →Related statements
Get real-time analysis of the latest Google SEO declarations
Be the first to know every time a new official Google statement drops — with full expert analysis.
💬 Comments (0)
Be the first to comment.