Why don't your product reviews show up as rich snippets despite perfect markup?

What does "Google does not trust a site" actually mean?

Mueller uses a deliberately vague phrasing. Google's trust is not a documented score or a metric available in Search Console. It refers to a bundle of signals: spam history, backlink quality, user behavior, update frequency, and publisher reputation.

Specifically, a recent site with low authority, artificial traffic spikes, or a toxic link profile risks having its rich snippets rejected, even with impeccable schema.org markup. Google applies a filtering logic here: it's better not to show stars than to display manipulated ratings.

What does Google mean by "reviews replicated from other sites"?

The duplication of reviews primarily affects two practices. First, direct scraping: retrieving reviews from Amazon, Trustpilot, or Verified Reviews to republish them on your product site. Then, aggregators that syndicate the same content across dozens of domains.

Google detects these duplications through text footprint and publication timelines. If your review appears word for word on a third-party domain before yours, you are technically in violation of duplicate content guidelines, even if it is your own product reviewed elsewhere.

Does this rule apply to all types of rich snippets?

No, and this is crucial. Product reviews (Product reviews) and local ratings are the most exposed to this filtering. Other types of structured data, like FAQs, recipes, or events, undergo less trust verification because the potential for commercial manipulation is lower.

However, Organization reviews and aggregated ratings on local SERPs follow exactly the same logic. A business with 50 identical Google Business Profile reviews posted within 48 hours will see its stars disappear temporarily, regardless of the markup quality.

• Correct schema.org markup is necessary but not sufficient for the display of review rich snippets
• Google's trust in a domain is based on publicly undocumented quality signals
• Any duplication of reviews, even partial, exposes you to display rejection without explicit notification
• Review rich snippets are more filtered than other types of structured data due to manipulation risks
• No official Google tool allows diagnosing trust issues regarding reviews

Is this statement consistent with real-world observations?

Absolutely. For years, we have seen sites with technically flawless markup that never generate stars in SERPs. A/B tests show that the same schema.org code deployed on an authoritative domain and a recent site produces radically different results.

What is frustrating is the lack of feedback. Search Console validates the markup, and the rich results testing tool does too, but nothing alerts you to a trust issue. You discover the invisibility of your rich snippets only through manual SERP monitoring or via third-party tools like SEMrush.

What nuances should be added to this official position?

Mueller simplifies to an extreme. "Trust" is not binary: Google applies variable thresholds depending on the vertical. An e-commerce site in health or finance will undergo much stricter filtering than a home decor blog. [To be verified]: some practitioners report that domain age plays a determining role, but Google has never explicitly confirmed this criterion.

Regarding duplication, be careful of false positives. Legitimate customer reviews collected by a third party (SaaS platform like Yotpo) then displayed on your site may be perceived as duplicated if the same review appears on the provider's widget. Technically compliant, practically penalized.

When does this rule not really apply?

E-commerce giants largely escape this filtering. Amazon displays rich snippets even on products with suspicious or mass-generated reviews. The size of the catalog and traffic volume seem to create a de facto exception, never officially documented.

The same is true for established aggregators like TripAdvisor or Yelp: their domain authority compensates for the aggregated nature (thus technically duplicated) of their content. Mueller's rule primarily applies to small and medium players, creating a competitive asymmetry rarely mentioned in official guidelines.

How can you verify that your reviews meet Google's criteria?

First reflex: duplication audit. Take 5-10 extracts of complete reviews and search them in quotes on Google. If the same texts appear on other domains with an earlier indexing date, you are in the red zone. Tools like Copyscape can automate this check across your entire catalog.

Second point: check the declared source of your reviews. If you are using a third-party widget, make sure that the schema.org points to a unique URL on your domain, not to the collection platform. The "author" field should ideally contain differentiated identifiers, not reused generic profiles.

What should you do if your rich snippets disappear overnight?

Let's be honest: Google will not notify you. Set up automated SERP monitoring on your main product queries. Tools like AccuRanker or SEOmonitor can track the presence or absence of stars over time.

If disappearance is confirmed, launch a complete E-A-T audit. Check your backlink profile (recent toxic link spike?), the freshness of your content, and the history of manual penalties in Search Console. Then, clean up any trace of review duplication and wait. The return of rich snippets may take 4 to 8 weeks after correction.

What practices should you adopt to maximize your chances of display?

Prioritize reviews collected directly, with a documented process. A post-purchase email with a link to a proprietary form remains the safest method. If you go through a third party (Trustpilot, Verified Reviews), ensure contractually that the reviews belong to you and that they will not be syndicated elsewhere without your consent.

On the technical side, implement the Review snippet markup only on pages where the review is actually published in full, not on aggregations or excerpts. Google penalizes pages that display stars without the complete associated text content. And above all, vary the publication date of reviews to avoid suspicious patterns.

• Audit for duplication: manual Google search in quotes + Copyscape on a representative sample
• Clean the markup: remove any example, demo, or placeholder review with active schema.org
• Monitor SERPs: automatically track the presence of stars on key queries (at least weekly)
• Document collection: keep proof of real purchases for each review (GDPR compliance + Google anti-spam)
• Avoid third-party widgets displaying the same reviews across multiple domains simultaneously
• Space out publications: posting 20 reviews on the same day triggers spam alerts, spread over 2-3 weeks