Official statement
Other statements from this video 17 ▾
- □ Faut-il vraiment créer du contenu géolocalisé pour toutes vos pages ?
- □ Le hreflang booste-t-il vraiment le classement ou est-ce un mythe SEO ?
- □ Peut-on vraiment combiner noindex et canonical sans risque SEO ?
- □ Faut-il vraiment indexer toutes vos pages de pagination ?
- □ Le budget de crawl : faut-il vraiment s'en préoccuper pour votre site ?
- □ Faut-il vraiment inclure vos pages m-dot dans vos annotations hreflang ?
- □ Exclure Googlebot de la détection d'adblock est-il du cloaking ?
- □ Faut-il vraiment optimiser tout le site pour ranker une seule page ?
- □ Les redirections de domaines expirés sont-elles vraiment ignorées par Google ?
- □ Faut-il créer un site intermédiaire bloqué par robots.txt pour gérer des milliers de redirections ?
- □ Les breadcrumbs sont-ils vraiment utiles pour le SEO ou juste un gadget UI ?
- □ Changer de CMS détruit-il vraiment votre référencement naturel ?
- □ L'UX est-elle vraiment un facteur de classement Google ou un simple effet de bord ?
- □ Faut-il vraiment optimiser des passages individuels ou toute la page reste-t-elle prioritaire ?
- □ Pourquoi l'authentification HTTP protège-t-elle mieux votre staging que robots.txt ou noindex ?
- □ Les Core Web Vitals desktop ne comptent-ils vraiment pour rien dans le classement Google ?
- □ Peut-on vraiment contrôler l'apparition des sitelinks dans Google ?
Google firmly prohibits the use of review structured data for reviews imported from third-party platforms, even with permission. Only reviews collected directly on your own platform can use this markup. Third-party reviews can still be displayed as standard testimonials, but without schema.org review markup — effectively excluding them from star-rich snippets in the SERPs.
What you need to understand
What distinguishes a genuine review from a copied review according to Google? <\/h3>
Google draws a clear line in the sand: a review is only considered 'genuine' if you collect it yourself, via your own system (on-site form, dedicated tool, proprietary platform). As soon as you import a review from Trustpilot, Google My Business, Yelp, or any external source — even with contractual permission — that review becomes third-party content.<\/p>
In practical terms? You can display these reviews on your site, highlight them, quote them. But you cannot mark them up with schema.org/Review or AggregateRating. Google explicitly rejects this markup for imported content, regardless of the context.<\/p>
This distinction is significant. It relies on the verification chain: Google wants to ensure that you control the source, that you can verify authenticity, and that you take editorial responsibility for the rated content.<\/p>
Why does Google reject review structured data for imported content? <\/h3>
The official reason boils down to one word: manipulation. If review markup is allowed on copied reviews, any site can siphon off 5-star ratings from a third-party platform, display them on their own site, and gain rich snippets without generating any real reviews.<\/p>
Google wants to prevent a 'worthless aggregator' effect. A site that copies 1,000 Trustpilot reviews and displays them with stars in the SERPs circumvents the system: it benefits from the reputation built elsewhere without having collected a single direct customer feedback.<\/p>
Mueller's stance is unequivocal: if you want stars in organic search, collect your own reviews. The rest is just testimonial — legitimate, displayable, but not eligible for schema markup.<\/p>
What should you do with third-party reviews if you can't mark them up as reviews? <\/h3>
First option: treat them as standard testimonials. You display them in plain HTML, with a citation, customer name, potentially a logo of the source platform. No schema markup, so no rich snippet, but text content that reassures visitors and can enrich the page.<\/p>
Second option: redirect to the source. Instead of copying reviews, you integrate a widget or a link to your Trustpilot/Google profile. You maintain the credibility of the third party, but you forgo organic markup. This is a cautious approach, especially if you're concerned about a manual disavow.<\/p>
Third option: collect your own reviews in parallel. You launch an internal system (WooCommerce plugin, custom tool, platform like Yotpo in proprietary mode), ask your customers after purchase, and only mark up those responses. Third-party reviews remain unmarked testimonials.<\/p>
- Imported reviews can never have schema.org/Review markup, even with legal permission from the source platform.<\/li>
- Unstructured testimonials can be displayed without risk, but will never appear as stars in the SERPs.<\/li>
- Only direct collection grants the right to review markup — and even then, provided that the guidelines are followed (no fake reviews, reasonable moderation, transparency).<\/li>
- Google does not recognize 'contractual permission' as a qualifying criterion: even a signed agreement with Trustpilot changes nothing about the rule.<\/li><\/ul>
SEO Expert opinion
Is this statement consistent with observed practices on the ground? <\/h3>
Yes, and it’s one of the rare cases where Google has maintained a perfectly stable line for years. Manual disavows for misuse of review markup on imported content are regularly observed. Sites that display aggregated stars from Trustpilot or Yelp with schema.org/AggregateRating often end up losing their rich snippets — or worse, facing a manual action for structured spam.<\/p>
What complicates things is that many WordPress or Shopify plugins automatically apply review markup to third-party reviews. The webmaster may not even realize they are violating the guidelines. The result: a clean site, legitimate reviews, but non-compliant markup exposing them to a disavow.<\/p>
Field observation: e-commerce sites that collect their own reviews (even 20-30 responses) consistently earn stable stars in the SERPs. Those that copy 500 Trustpilot reviews with markup lose their stars after a few weeks, without warning.<\/p>
In what cases does this rule pose a legitimate problem? <\/h3>
First case: multi-brand distributors. A reseller selling third-party products often has no own reviews — customers rate on Amazon or the manufacturer’s site. If they copy these reviews to reassure their visitors, they cannot mark them up. Result: zero stars in the SERPs, even though the product has 500 five-star ratings elsewhere.<\/p>
Second case: legitimate aggregators. A price comparison site or a sector review site that centralizes feedback from multiple sources loses all SEO value if no reviews can be marked up. Google makes no distinction: even a high-value aggregator is treated like a copier.<\/p>
Third case: franchises or networks. A national brand collecting reviews on Google My Business for each point of sale cannot consolidate them on the corporate site with markup. Each establishment has its own local stars, but the national site remains without product rich snippets.<\/p>
Should you completely abandon third-party reviews to optimize your SEO? <\/h3>
No, but you must segment their usage. Third-party reviews still have enormous conversion value: a visible Trustpilot widget reassures, a displayed Google score inspires confidence. But this value is purely on-site — it doesn’t translate into the SERPs.<\/p>
The optimal strategy is to double up your systems: keep your Trustpilot widget in the sidebar for reassurance, while launching a direct collection (post-purchase, automated email, dedicated form) to obtain mappable reviews. Both can coexist without conflict.<\/p>
What doesn’t work is trying to 'map everything' hoping that Google won't detect anything. Crawlers easily identify a copied Trustpilot review, even if reformulated. As soon as the source is third-party, the markup is a mistake — and Google always ends up spotting it.<\/p>
Practical impact and recommendations
How can I check if my site is using review structured data on third-party reviews? <\/h3>
First step: audit your existing markup. Use the Google rich results testing tool (or the schema.org validator) on your product or service pages. Identify all Review or AggregateRating objects present in the source code.<\/p>
Second step: trace the source of each review. For each marked review, check where the content comes from. If it’s a plugin importing from Trustpilot, Google, Yelp — even via official API — it's third-party, hence non-compliant. If it’s an on-site form, proprietary tool, or post-purchase system, you're clean.<\/p>
Third step: analyze the active plugins. Some modules (especially WordPress, Shopify, PrestaShop) automatically apply review markup to imported content. Temporarily disable each review plugin, reload the page, and check if the markup disappears. If yes, it’s the culprit.<\/p>
What concrete actions can be taken to quickly comply? <\/h3>
If you’re currently marking up third-party reviews with schema.org/Review: remove the markup immediately. Keep only the raw HTML content, without any structured data. You can display the reviews, visually highlight them, but no schema markup.<\/p>
If you want to preserve star-rich snippets: launch your own collection. Set up a post-purchase customer feedback system (automated email J+7, dedicated form, tool like Judge.me in proprietary mode). Wait until you have at least 10-15 reviews before marking up — an AggregateRating on 2 reviews looks suspicious.<\/p>
If you manage a complex product catalog: prioritize best-sellers. There’s no need to collect reviews on 500 references at once. Focus on the 20-30 products generating the most organic traffic, solicit targeted feedback, and only mark those pages up.<\/p>
- Audit all pages marked with Review or AggregateRating using Google’s rich results testing tool
- Identify the source of each review: own (on-site form) or third-party (Trustpilot, Google, Yelp, etc.)
- Remove the schema.org markup from all imported reviews, even if the import is legal and permitted
- Leave third-party reviews displayed in plain HTML, without structured markup — they retain their conversion value
- Implement a clean collection system (post-purchase, dedicated tool) to obtain markable reviews
- Ensure that active e-commerce plugins do not automatically re-inject review markup on third-party content <\/ul>
❓ Frequently Asked Questions
Puis-je baliser des avis Google My Business importés sur mon site e-commerce avec schema.org/Review ?
Si j'ai l'autorisation écrite de Trustpilot pour afficher leurs avis, puis-je utiliser le markup review ?
Quelle est la différence entre un témoignage et un avis au sens de Google ?
Combien d'avis propres faut-il collecter avant de baliser avec AggregateRating ?
Peut-on perdre ses rich snippets étoilés si on balisait des avis tiers par erreur ?
🎥 From the same video 17
Other SEO insights extracted from this same Google Search Central video · published on 16/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.