What happened
Google quietly added a line to its review-snippet structured-data documentation: don't include fake or undisclosed incentivized reviews on your page or in your structured-data markup. Two examples are spelled out. Reviews written without genuine experience of the product or service. And reviews exchanged for money, discounts, vouchers, or free product where the incentive isn't clearly disclosed.
Nothing about this is a surprise as policy — Google has never wanted fake reviews, and the FTC already requires incentive disclosure on the consumer-protection side. What changed is location. The rule now lives in the guidelines that govern review-snippet eligibility, the same docs that decide whether star ratings appear under your products in search results. Search Engine Land's Barry Schwartz flagged the addition on July 24.
Why this matters
Incentivized reviews are the default in ecommerce, not the exception. Points programs, post-purchase coupons, free product for early reviewers — most review apps ship these flows out of the box. None of that is banned. The undisclosed part is the violation, which means the difference between a clean program and an ineligible one is a disclosure label your review platform may or may not be rendering.
The enforcement lever is obvious even though Google doesn't spell it out: review snippets are a rich result, and rich results get withheld when markup breaks guidelines. For a store whose products show stars in search listings, losing them is a click-through-rate haircut on every ranking you own. Will Google proactively police this at scale? Probably not — but the doc gives them a clean citation for manual actions, and it gives competitors a clean citation for spam reports. Assume the audit arrives with a complaint, not a crawler.
There's an AI angle too. Review content increasingly feeds shopping answers across AI surfaces, and structured review data is the cleanest input those systems have. A rule formalizing what belongs in review markup is Google tightening the supply chain of a signal it plans to keep using.
What to do about it
Audit your review program for disclosure
List every incentive you offer for reviews — discount codes, loyalty points, free product, giveaway entries. For each one, confirm the resulting review carries a visible disclosure where it's displayed. If your review app supports an incentivized-review badge, turn it on; if it doesn't, that's now a reason to reconsider the app.
Inspect the markup, not just the page
Pull a product page's source and read the Review and AggregateRating structured data your app injects, then run it through the Rich Results Test. The guideline covers the markup itself — a disclosure that shows on-page while undisclosed reviews flow into the schema doesn't get you there.
Purge anything that fails the genuine-experience test
Seeded reviews from staff, imported reviews for products the reviewer never bought, testimonials pasted in as reviews — cut them from the page and the markup. They were always a risk. Now they're a documented eligibility problem sitting next to your stars.
Bake disclosure into the request flow
Put the incentive language in the review-request email itself and require the disclosure flag at submission where your platform allows it. Disclosure built into collection never needs retrofitting, and it survives an app migration far better than display-layer badges do.