Official statement
Other statements from this video 14 ▾
- 1:04 Pourquoi Google pioche-t-il parfois l'image d'un autre site pour illustrer votre featured snippet ?
- 3:02 Les réponses courtes sur sites Q&A nuisent-elles au référencement ?
- 7:24 Les Featured Snippets et Rich Results utilisent-ils vraiment des critères de qualité différents ?
- 12:42 Les certificats HTTPS premium offrent-ils un avantage SEO ?
- 20:09 Les pages en No Index nuisent-elles à la qualité globale de votre site ?
- 20:15 Le contenu médiocre d'un site peut-il vraiment pénaliser l'ensemble de vos pages dans Google ?
- 20:44 Canonical ou No Index : quelle balise privilégier pour gérer le contenu dupliqué ?
- 21:49 Les tests A/B peuvent-ils vraiment pénaliser votre SEO ?
- 23:12 Comment Google gère-t-il vraiment les URL paramétrées de navigation facettée ?
- 23:58 Les pages de redirection nuisent-elles vraiment au classement de votre site ?
- 37:50 Faut-il vraiment créer une version mobile si Google indexe le desktop ?
- 39:13 Pourquoi votre version desktop peut-elle disparaître du classement si votre mobile est incomplet ?
- 43:58 Le contenu CSS masqué sur mobile compte-t-il vraiment pour l'indexation Google ?
- 57:48 La vitesse du site est-elle vraiment un critère de classement Google ?
Google now requires that schema-marked reviews come directly from end users and not from internal forms. Testimonials collected through your own site should no longer be structured with the Review schema. This clarification reshapes the display of Rich Results: only external third-party sources (Trustpilot, Google Reviews, Verified Reviews) are eligible.
What you need to understand
What distinction does Google make between reviews and testimonials?
The distinction is based on the source of collection. A user review, according to Google, is gathered by an independent third-party platform: review aggregator, marketplace, industry rating site.
A testimonial collected via an internal form (your own site, post-purchase email, customer survey) falls under a process controlled by the seller. Google regards this channel as potentially biased, lacking external verification of authenticity or representativeness.
Why is Google tightening its stance on this issue?
Reviews in Rich Results generate a high click-through rate: golden stars, enriched snippets, advantageous visual positioning. This visibility has naturally created an incentive to artificially inflate ratings through selected testimonials.
By imposing external collection, Google aims to restore user trust in enriched snippets. The logic is: a third party verifies, authenticates, and represents all feedback, not just the best.
Does this rule apply to all types of schema?
No, only to schemas that trigger an enriched display visible in the SERPs: Review, AggregateRating, Product with reviews. Testimonials can still exist on your site, but without structured markup eligible for Rich Results.
Other schemas (Organization, LocalBusiness, FAQ) are not impacted by this directive. Your NAP, hours, or Q&A can still be marked up normally.
- Only external third-party platforms are now eligible for the Review schema for Rich Results
- Internal forms (own site, email, CRM) should no longer be marked up as reviews
- Testimonials can remain on the site, but without schema markup if collected internally
- This rule targets enriched snippets, not all types of structured data
- Google prioritizes verifiable sources to maintain user trust in the SERPs
SEO Expert opinion
Is this statement consistent with observed practices on the ground?
Yes, and it finally formalizes what Google has already been applying inconsistently for two years. Many sites with marked internal reviews have seen their stars disappear without official explanation between 2022 and 2023.
What is concerning is the lack of precise criteria to define what constitutes an "acceptable third-party platform." Google does not provide any whitelist. Trustpilot does, but what about lesser-known industry aggregators? [To be verified] on what criteria Google judges the legitimacy of a review source.
What nuances should be added to this rule?
The line between internal and third-party collection is sometimes blurry. If you use a third-party widget (Verified Reviews, Avis Vérifiés) integrated into your checkout, technically the collection goes through a certified intermediary.
In that case, you can mark up the reviews if the third party manages authentication and also publishes the feedback on its own platform. The key criterion: does the review exist outside your direct control? If yes, the markup remains defensible.
In what cases does this rule not apply?
Purely editorial sites (professional reviews, product tests) are not affected: a review article signed by a journalist can still be marked up as CriticReview, as it consists of editorial content, not aggregated user feedback.
B2B markets pose an unresolved issue. Long sales cycles and small customer bases make it difficult to collect through third-party platforms. Google offers no alternative, and the rule penalizes sectors where consumer aggregators do not exist. [To be verified] if Google plans to adapt this doctrine to B2B contexts or vertical niches.
Practical impact and recommendations
What steps should you take right now?
Audit your current schema markup. Identify all pages with Review or AggregateRating. For each, check the source: internal collection or third-party platform?
If the source is internal, remove the schema. Keep the testimonials in visible HTML, but without structured markup. Your content remains useful for the user; it just does not generate Rich Results anymore.
What mistakes should you absolutely avoid?
Do not attempt to disguise internal testimonials as third-party reviews by tinkering with the author or publisher properties. Google cross-checks its data: if your domain collects and displays the review, it considers the source as internal.
Also, avoid deleting all your visible testimonials. Their presence reassures visitors and boosts conversions, even without stars in the SERP. The goal is to remove the schema, not the content.
How can I check that my site is now compliant?
Use Google’s Rich Results Test on your critical URLs. If a warning appears on the reviews, it means Google detects an internal collection. Correct it immediately.
Set up a third-party collection process: choose a platform (Trustpilot, Avis Vérifiés, Verified Reviews), integrate it into your customer journey, actively collect for 2-3 months, then mark up these new reviews. Patience is key; building a stock of third-party reviews takes time.
- Audit all pages with schema Review or AggregateRating
- Remove schema markup for reviews collected internally (forms, emails, CRM)
- Keep testimonials in visible HTML for conversion, without markup
- Choose and integrate a certified third-party review platform
- Test critical URLs with Google’s Rich Results Test
- Document the source of each review for future auditing
❓ Frequently Asked Questions
Puis-je baliser des avis collectés via un widget tiers intégré à mon site ?
Les témoignages clients doivent-ils être supprimés de mon site ?
Quelle plateforme tierce Google considère-t-il comme acceptable ?
Un article de test produit rédigé par mon équipe peut-il être balisé Review ?
Que se passe-t-il si je garde mes schemas Review internes ?
🎥 From the same video 14
Other SEO insights extracted from this same Google Search Central video · duration 59 min · published on 03/04/2018
🎥 Watch the full video on YouTube →
💬 Comments (0)
Be the first to comment.