Should you really ban external reviews from your Schema.org structured data?

What does Google mean by "non-original reviews"?

Google distinguishes two categories of reviews: those that you collect directly from your customers through your own system (post-purchase form, proprietary platform, internal survey), and those that you retrieve from a third-party source (Trustpilot, Verified Reviews, Google Reviews, Amazon, etc.).

Mueller's position is clear: if the review does not come from your own collection mechanism, it should not appear in your Schema.org markup of type Review or AggregateRating. It doesn't matter if you have an official API with the third-party platform or if you display those reviews on your site — if you're not the source of the collection, you're out of the game.

Why does Google impose this restriction?

The official reason relates to the quality and authenticity of the data displayed in the SERPs. Google wants to prevent sites from manipulating rich snippets by massively importing positive reviews from third-party platforms without real control over their origin.

In practice, it also limits cases where the same review appears twice: once on the Google Business Profile of the business, another time in organic results via Schema.org. Google aims to avoid redundancy and maintain a clear hierarchy between its own review systems (GBP, Shopping) and the open web.

Does this rule apply to all types of Schema?

No. The directive specifically concerns Review and AggregateRating tags in Schema.org. If you use other types of structured data (Product, Organization, LocalBusiness without reviews), you are not affected.

However, as soon as you add an aggregateRating property or a review object in your JSON-LD or microdata, you fall under the scope of this rule. Even one single external review is enough to expose you to a manual action if Google detects that the source is not your own collection system.

• Only reviews collected directly by you (internal form, proprietary platform) are allowed in Schema.org.
• Reviews imported from Trustpilot, Google Reviews, Verified Reviews, Amazon, etc. must NOT be marked up.
• The rule aims to prevent the manipulation of rich snippets and redundancy in the SERPs.
• It only applies to Review and AggregateRating tags, not to other types of Schema.
• Even with an official API, if you are not the source of the collection, you are out of the directive.

Is this statement consistent with observed practices in the field?

Yes and no. Google has always had a strict stance on reviews in its quality guidelines, but the actual enforcement is uneven. We still see thousands of e-commerce sites using Trustpilot or Verified Reviews in their Schema.org without visible manual action.

Let’s be honest: Google doesn’t have the human resources to track every site manually. Most penalties arise either after a competitor report or when a site abuses too openly (fake reviews, manipulated ratings, mass spam). If your site displays 4.9 aggregated stars from a third-party source but everything else is clean, you might fly under the radar for years. [To be verified]: no public data documents the actual rate of manual actions for this specific infringement.

What nuances should be considered regarding this rule?

Mueller does not specify what constitutes "your own collection." If you use a third-party widget hosted on your domain (such as Reviews.io, Yotpo, Judge.me), technically you are collecting through an intermediary — but you control the interface, the form, and you own the data.

In this case, the gray area persists. Some experts believe that as long as you master the entire cycle (triggering the email, displaying on your site, moderation), you respect the spirit of the directive. Others prefer complete safety and only use 100% internal systems. My opinion? If you go through a third-party platform but contractually own the reviews (not just a display license), you’re probably in the clear — but Google has never confirmed this in black and white.

In what cases does this rule not apply?

If you are a review aggregator (like Trustpilot, Yelp, TripAdvisor), you can obviously mark your own reviews — since it is you who collects them. Likewise, if you are a marketplace (Amazon, eBay, Airbnb) and reviews are submitted directly on your platform, there’s no problem.

Another borderline case: media and comparison sites. If you publish a product test with an editorial score (like Les Numériques, 60 Millions de Consommateurs), it’s an original review — you can mark it up. However, if you aggregate ratings from several external editorial sources, we fall back into the gray area. Google has never clarified this point, and market practices vary widely.

What should you do if you use external reviews?

First step: audit your current Schema markup. Inspect your JSON-LD or microdata and identify all occurrences of "@type": "Review" or "aggregateRating". For each instance, identify the source of the reviews: do they come from your own collection system, or from a third-party platform?

If the answer is "third-party", you have two options. Either you completely remove the markup (the safest solution), or you migrate to a proprietary collection system (Reviews.io, Yotpo, or internal development) and only mark up the new reviews collected through this channel. Avoid the temptation to keep the old markup "in the meantime" — it’s the best way to trigger a manual action the day Google scans your site.

What mistakes should you absolutely avoid?

Do not attempt to disguise the source by modifying the author or publisher attribute in the Schema to make it seem like the review comes from you. Google cross-checks this data with the visible content on the page — if you display a Trustpilot logo next to the review but your JSON-LD claims it comes from your own system, it’s a huge red flag.

Another classic pitfall: marking up Google Business Profile reviews retrieved via the Places API. Even if technically they are "your" reviews (linked to your profile), Google considers them external for Schema markup on your website. They must remain confined to your GBP — end of story. And this is where it gets tricky: many WordPress or Shopify plugins automatically import these reviews and mark them up without your knowledge.

How can you check if your site complies?

Use the Rich Results Test from Google (search.google.com/test/rich-results) to validate your markup. The tool does not detect the source of the reviews, but it spots structural errors. Then, check in Search Console under the