Google’s Incentivized Review Rule and Your Snippets

Review markup is one of the few structured data types with a manual action attached to it, which makes a new guideline worth reading the day it appears rather than the quarter it starts mattering. Google added one on 24 July 2026. The documentation changelog records a new guideline in the review snippet documentation about fake and undisclosed incentivized reviews, added to improve user review transparency. The page itself now carries a last-updated date of 8 September 2026.

What the guideline says

The wording in the review snippet guidelines is short. Don’t include fake or undisclosed incentivized reviews on your page or in your structured data markup. Google then gives two examples of what that covers: reviews that aren’t based on a genuine experience of a product or service, and reviews written in exchange for a benefit — money, discounts, vouchers or free products — that don’t clearly and prominently disclose the incentivization.

The guidelines sit under a warning that applies to all of them: if your site violates one or more, Google may take manual action against it, and once the problem is remedied you can submit the site for reconsideration. So this is not advisory phrasing dressed as a rule.

Incentive is allowed; hiding it is not

The pivot in that sentence is “undisclosed”. Google has not banned seeding a product launch, running a sampling programme or offering a voucher for feedback. It has said that if a benefit changed hands, the review has to say so clearly and prominently. Clearly and prominently is doing real work in that phrase: a line in the terms of service is not prominent, and a badge visible only after expanding a truncated review is not clear. The disclosure belongs next to the review, in the place a reader sees before the star rating registers.

The second example is separate and stricter. A review not based on a genuine experience fails regardless of disclosure, because no amount of labelling makes an invented opinion an opinion. That is the clause that catches generated review text, whoever generated it.

The neighbouring rules that catch sites out

The incentivization guideline arrived into a list that already had teeth, and the older rules are still the ones that trip most implementations:

• Don’t aggregate reviews or ratings from other websites. Pulling a third-party rating into your own AggregateRating is a direct violation, not a grey area.
• Self-serving reviews on organisations. If the entity being reviewed controls the reviews about itself, pages using LocalBusiness or any other Organization type are ineligible for the star review feature — including when those reviews arrive through an embedded third-party widget.
• Ratings must come directly from users, and Google says not to rely on human editors to create, curate or compile ratings information for local businesses.
• The content has to be on the page. If you mark up reviews, users must be able to see the review text and rating; if you mark up an aggregate, they must be able to see that aggregate.

Where honest programmes break this

Three patterns account for most of it, and none of them involves anyone deciding to cheat. The first is an imported review set: a store migrates platforms, inherits several thousand historical reviews, and has no record of which came from a sampling campaign years ago. The second is an aggregate that quietly includes seeded reviews — the individual entries may carry a disclosure badge in the widget, but the AggregateRating in the markup is a single number with no provenance attached. The third is review gating, where a flow routes satisfied customers to the public review form and unhappy ones to a support ticket. Gating is not incentivization, but it produces a rating that is not sourced directly from users in the sense the guidelines describe.

The local case is the one to check first, because LocalBusiness markup with self-controlled reviews was already ineligible before this guideline existed. That overlaps with the ground covered in what actually moves local rankings.

An audit over your own review data

Start from the sources rather than the markup. List every channel that can create a review on your site: native form, imported set, third-party widget, syndicated feed from a manufacturer, anything attached to a sampling or affiliate programme. For each, answer whether an incentive was ever available, whether a disclosure is stored as a field rather than inferred, and whether those reviews are inside the aggregate. Then check the rendered page against the markup — the schema.org Review type defines the shape, but the guidelines are about what the shape is allowed to contain. Anything you cannot trace, exclude from the aggregate rather than defend. Losing a rich result you chose to give up is a better position than the one described in when Google removes a rich result, and considerably better than a manual action. The same traceability discipline applies to the product templates in WooCommerce product page SEO.