Review Schema After Google’s Self-Serve Crackdown
What still qualifies for review schema star ratings on product pages, and the disclosure and one-target rules that keep markup eligible.
Review schema still works for ecommerce products in 2026, but the rules around it have tightened since Google’s 2019 crackdown on “self-serving” review stars, and its structured data documentation keeps getting revised to close gaps businesses were exploiting. The core restriction has stayed constant: pages using LocalBusiness or Organization markup can no longer show star ratings from reviews the business itself collects and controls — that eligibility was removed specifically because it let companies publish their own trust badge. Product review stars on ecommerce pages are still allowed, but only when every review behind the rating is genuine, undisclosed incentives are absent, and the markup points at exactly one clear target rather than being reused across several entities on the same page.
Key takeaway
- Since 2019,
LocalBusinessandOrganizationschema can’t show self-collected review stars — that restriction doesn’t apply to genuineProductreviews. - Google’s structured data guidelines explicitly prohibit fake or undisclosed incentivized reviews in both visible content and markup, not just markup alone.
- A more recent documentation update clarifies that each review or rating should point to exactly one target — reused ratings shared across multiple entities on a page are now flagged.
- Violations don’t get the whole site penalized; Google’s typical response is to ignore the structured data on the affected page while leaving the page itself indexable.
What actually changed in 2019, and what it doesn’t cover
The 2019 update stopped LocalBusiness and Organization structured data from being eligible for the star rating rich result when the business being described controls the reviews about itself — a company publishing its own aggregate rating on its own about page, essentially self-certifying trust. That change was specifically about self-serving business-level ratings, not about product reviews collected through a legitimate, moderated review platform on a product page. A Product entity with a genuine aggregateRating built from real customer reviews is a different case and remains eligible — the distinction Google draws is between a business rating itself and a business hosting reviews customers left about a specific purchase.
The rules that determine whether review markup stays eligible
| Rule | What it means in practice |
|---|---|
| No self-serving business ratings | LocalBusiness/Organization can’t carry star ratings the business itself collects about itself |
| No fake or undisclosed incentivized reviews | Reviews written in exchange for money, discounts, or free products must be clearly disclosed, or excluded from the markup entirely |
| One review target per rating | Don’t attach the same aggregate rating or review to multiple entities on a page — each needs one clear, unambiguous target |
| Reviews must reflect genuine experience | Markup pulled from third-party review syndication should represent real reviews of the actual product, not a generic category average |
The one-target rule and where it usually breaks
Google’s review snippet documentation now explicitly advises against attaching a single review or rating to more than one entity in the structured data graph. In practice this shows up most often in themes and plugins that auto-generate markup: a product’s aggregate rating gets reused as the rating for the business itself, or the same JSON-LD block ends up nested under both an old template and a newer one that was added on top without removing the original, producing two competing targets for one rating. Neither is intentional manipulation in most cases — it’s leftover markup from a platform update — but Google’s validation treats an ambiguous target the same as a technical error. Run a sample of product pages through the Rich Results Test periodically and count how many distinct entities share a review or rating; more than one sharing the same value is the signal to clean up.
One rating, one target
Google updated its review snippet documentation to state explicitly that each review or aggregate rating in structured data should have one clear target, warning against reusing the same rating across multiple different entities on a page — a common byproduct of automatically generated markup from themes and plugins.
Source — Google Search Central, Review snippet structured data technical guidelines
Keeping incentivized reviews compliant
Incentivized reviews aren’t banned outright — plenty of legitimate review platforms send a discount code or loyalty points for leaving any review, positive or negative. What Google’s guidelines prohibit is the incentive being undisclosed, or the review not reflecting a genuine product experience at all. If your review collection flow offers any reward, disclose it clearly on the page next to the reviews, and make sure your review platform doesn’t filter out negative reviews from customers who received the same incentive as everyone else — a lopsided, filtered set of incentivized reviews is exactly the pattern that reads as manipulation rather than genuine feedback, whether or not the disclosure box is checked.
Third-party review platforms and syndicated markup
Most stores don’t hand-build review markup — a third-party platform generates it and injects the JSON-LD automatically. That convenience comes with a specific risk: syndicated reviews written for a manufacturer’s generic listing sometimes get attached to every retailer’s product page selling that item, including yours, even though the review text describes an experience with a different seller’s packaging, shipping, or customer service. Google’s guidance is that reviews should reflect a genuine experience with the specific product on the specific page carrying the markup, so blanket-syndicated review counts that inflate every reseller’s rating identically are a compliance risk worth checking, not just a data-quality nuisance. Ask your review platform vendor directly whether ratings are page-specific or shared across a manufacturer’s full distribution network, and if it’s the latter, weigh whether to keep using it for structured data at all versus only for on-page display.
The same caution applies to first-party review widgets that pull an aggregate score from a different measurement than the one shown to the user — for instance, blending “would recommend” survey data with a five-star review average into a single number. If the number in your aggregateRating markup isn’t the same number a shopper sees when they read the reviews on the page, that’s a mismatch worth fixing before it’s flagged rather than after.
An audit checklist for existing review markup
- Confirm no
LocalBusinessorOrganizationentity on the site carries a self-collectedaggregateRating— move any legitimate product ratings onto the relevantProductentity instead. - Check whether any incentive is offered for reviews, and if so, confirm the disclosure is visible on the page, not just buried in a review platform’s terms.
- Sample product pages in the Rich Results Test and verify each review or rating resolves to exactly one entity, not several.
- Confirm reviews sourced from a third-party platform genuinely relate to the specific product on the page, not a category-wide or brand-wide average mislabeled as product-specific.
- Set a recurring review of Google’s review snippet documentation — this is one of the more frequently revised structured data types, and quiet documentation updates tend to precede stricter automated enforcement.
This audit pairs naturally with a broader look at product schema markup, since review data usually lives inside the same JSON-LD block as price and availability, and with a check of how those ratings are represented if you also run a Merchant Center feed, where review data can independently affect Shopping eligibility.
Frequently asked questions
Can ecommerce product pages still show star ratings in search results?
Yes. The 2019 restriction applies to self-serving LocalBusiness and Organization ratings, not to genuine Product reviews. A product page with real customer reviews and correctly scoped aggregateRating markup remains eligible for the star rating rich result.
What happens if my review markup violates the rules?
Google’s typical response is to ignore the structured data on the affected page rather than penalize the whole site — the page can still rank and appear in search, it simply won’t show the review rich result until the markup is fixed and re-validated.
Are incentivized reviews against Google’s guidelines?
Not automatically. Incentivized reviews are allowed if the incentive is clearly and prominently disclosed and doesn’t bias which reviews get published. Undisclosed incentives, or filtering out negative reviews from incentivized reviewers, are what cross into a violation.
Can I display my Google Business Profile star rating on my website using schema?
You can display it as text, but marking it up as structured data on a LocalBusiness or Organization entity you control won’t make it eligible for a rich result — that’s exactly the self-serving pattern the 2019 update was designed to stop.
Why would the same rating show up on two different entities in my schema?
This is usually a template or plugin issue — an older JSON-LD block left in place after a newer one was added, or an aggregate rating reused between a product and the business entity on the same page. Audit with the Rich Results Test and remove the redundant reference.
The bottom line
Review schema on ecommerce product pages is still a live, useful rich result — it just requires more discipline than it did before the self-serving crackdown. Keep business-level ratings off entities you control, disclose incentives clearly, and make sure every rating in your markup points to exactly one entity. Review structured data is one part of the broader picture in our ecommerce SEO guide, and it works best alongside solid product page SEO fundamentals rather than as a standalone fix.
If your star ratings have stopped showing or you’re setting up review markup for the first time, our SEO services team can audit and correct it.
