Official statement
Other statements from this video 12 ▾
- 1:19 Faut-il vraiment garder vos pages d'événements en ligne après la date ?
- 4:37 Diviser ou fusionner un site : pourquoi Google ne transfère-t-il pas la valeur SEO comme pour un simple move ?
- 5:23 Faut-il vraiment éviter les doubles bylines pour ne pas perturber Google ?
- 13:08 Comment enlever efficacement les pages hackées des résultats de recherche Google ?
- 16:56 Les bannières GDPR bloquent-elles vraiment l'indexation de vos contenus par Googlebot ?
- 21:42 Faut-il héberger ses images sur un sous-domaine CDN pour optimiser leur indexation ?
- 24:14 Faut-il encore utiliser le nofollow pour filtrer le crawl de navigation à facettes ?
- 31:39 Le JavaScript nuit-il encore au crawl Google en l'absence de rendu côté serveur ?
- 37:55 Le mobile-first indexing s'applique-t-il vraiment à tous les sites sans exception ?
- 38:23 Les sous-types de schéma affectent-ils réellement l'affichage des extraits enrichis ?
- 43:00 Pourquoi robots.txt et noindex ne suffisent-ils pas pour protéger vos serveurs de staging ?
- 46:20 Comment Google calcule-t-il vraiment la position affichée dans la Search Console ?
Google is now limiting the display of review rich snippets to specific types of content and strictly excluding reviews hosted on the website of the entity being reviewed. In practical terms, an e-commerce site can no longer display its own product reviews as rich snippets. This restriction aims to favor third-party and independent sources, reshaping strategies for schema.org markup.
What you need to understand
What are the concrete changes in the display of reviews?
The update restricts the display of review rich snippets to well-defined types of content. Google does not always specify an exhaustive list, but we know that reviews of movies, books, and third-party products remain eligible.
The game-changing point: reviews hosted on the site of the reviewed entity no longer generate rich snippets. If you sell a product and publish customer reviews directly on your product page, those reviews will not appear as stars in the SERP—even if the schema.org markup is technically correct.
Why this restriction now?
Google seeks to promote third-party and independent sources. A site that rates its own products or services creates an obvious conflict of interest: nothing prevents it from only publishing 5-star reviews and burying negative ones.
This logic aligns with Google's goal to enhance the trustworthiness of SERPs. Review rich snippets offer a considerable visual advantage (gold stars, boosted click rates). Google does not want this boost to be captured by sites that self-rate.
What types of content remain eligible?
Third-party review sites retain their eligibility: review aggregators, product testing blogs, independent rating platforms. If your business model relies on reviewing external products or services, you can continue to utilize the Review markup.
Local reviews via Google Business Profile are not impacted by this update—they follow their own display logic. This strictly concerns the organic rich snippets in standard search results.
- Self-hosted reviews (on the site of the reviewed entity) no longer generate rich snippets, even with correct schema.org markup.
- Third-party review sites retain their eligibility to display stars in the SERP.
- This restriction aims to limit conflicts of interest and favor independent sources.
- The Review markup remains technically valid, but Google chooses not to display it for certain types of content.
- Local Google Business Profile reviews are not affected by this update.
SEO Expert opinion
Was this restriction predictable on the ground?
Absolutely. For years, there has been an inflation of abuses on the Review markup: e-commerce sites displaying questionable 4.8/5 ratings, B2B services self-rating, pages publishing cherry-picked 3 reviews to snag stars. Google long tolerated this and then started devaluing certain signals—this update simply formalizes a practice that had already started on the algorithm side.
What's interesting: Google is not removing the Review markup from its guidelines. It remains technically valid, but its display is now conditional on the type of site. This is a subtle but crucial distinction: your markup may be perfect and never generate a rich snippet.
What gray areas remain in this announcement?
Mueller's statement remains vague on several points. [To be checked]: what is the exhaustive list of eligible content types? Google talks about "certain specific types" without providing a precise taxonomy. We know that reviews of third-party products are acceptable, but what about self-published book reviews, online courses, SaaS?
Another blind spot: how does Google determine that a review is hosted "on the site of the reviewed entity"? If an e-commerce integrates a Trustpilot or Verified Reviews widget via iframe, is it considered self-hosted or third-party? The technical boundary is not clear, and Google provides no clarification on this.
Should you remove the Review markup from your site?
No. The schema.org Review markup remains relevant for other search engines, voice assistants, third-party crawlers. It also contributes to the semantic understanding of your content by algorithms, even though visual display in SERPs is blocked.
However, if your sole goal was to snag stars in the SERP and you are a self-rating site, this strategy is dead. Redirect your efforts towards third-party platforms (Trustpilot, Capterra, G2) and optimize your presence on these channels to indirectly capture traffic through their rich snippets.
Practical impact and recommendations
What to do if your site hosted product reviews with Review markup?
First step: audit your current markup. Identify all pages with schema.org Review or AggregateRating. If these reviews concern your own products/services and are hosted on your domain, the rich snippets will no longer display—but the markup remains valid for other uses (crawlers, semantic understanding).
Second step: pivot to third-party platforms. Actively collect reviews on Trustpilot, Google Business Profile (for local), Capterra (B2B SaaS), Amazon (if relevant). These platforms have their own rich snippets and generate qualified traffic via their authority.
How to recover the lost visual advantage in SERPs?
The other types of rich snippets remain fully exploitable: FAQ, HowTo, Product (without Review), BreadcrumbList, VideoObject. If you lose the stars, compensate by optimizing these other formats to gain vertical space in SERPs.
On the content side, focus on third-party comparison pages and tests. If you are a media outlet or a blog, publish reviews of external products: this type of content remains eligible for review rich snippets. Some e-commerce sites even launch separate blogs (on a different domain) to publish third-party reviews and recover rich snippets—a tricky but feasible strategy.
What mistakes to avoid during the transition?
Do not abruptly remove all the Review markup from your site. As mentioned above, it retains semantic utility and can be read by other tools than Google Search. However, do not waste time optimizing it in hopes of snagging stars if your site is self-rating.
Avoid also trying dubious technical workarounds (masked iframes, parked domains, etc.) to circumvent the rule. Google will sooner or later detect the link between your site and the fictitious "third-party platform," and you risk a manual penalty that is much costlier than just losing rich snippets.
- Audit all pages with Review or AggregateRating markup to identify those that are now ineligible.
- Redirect your review collection strategy to recognized third-party platforms (Trustpilot, Capterra, G2, Google Business Profile).
- Compensate for the loss of review rich snippets by leveraging other formats: FAQ, HowTo, Product, VideoObject.
- If you are a media outlet or blog, publish reviews of external products/services to remain eligible for rich snippets.
- Keep the existing Review markup for its semantic utility, but no longer invest resources to optimize it if your site is self-rating.
- Do not attempt to circumvent the rule with dubious technical workarounds: the risk of a manual penalty is real.
❓ Frequently Asked Questions
Mon site e-commerce peut-il encore afficher des étoiles en SERP avec des avis clients ?
Le balisage schema.org Review est-il devenu inutile ?
Un blog de critiques de produits tiers est-il encore éligible aux extraits enrichis d'avis ?
Si j'intègre un widget Trustpilot sur mes fiches produits, est-ce considéré comme tiers ou auto-hébergé ?
Dois-je supprimer tout le balisage Review de mon site e-commerce ?
🎥 From the same video 12
Other SEO insights extracted from this same Google Search Central video · duration 57 min · published on 20/09/2019
🎥 Watch the full video on YouTube →
💬 Comments (0)
Be the first to comment.