Google has added a line to its review snippet structured data documentation telling site owners not to include fake or undisclosed incentivized reviews, either on the page or in the markup. The change was made on 24 July 2026 and applies to Review and AggregateRating markup, which is the data behind the star ratings that show in search results. Search Engine Land reported the documentation change the same day.

The guidance names two things as prohibited: reviews that are not based on a genuine experience of a product or service, and reviews written in exchange for a benefit such as money, discounts, vouchers or free products that do not clearly and prominently disclose the incentivization.

What changed, and what did not

This is a documentation update. Google did not announce an algorithm update, a manual action campaign, or a date on which star ratings stop appearing for anyone. What changed is the written guidance on the review snippet page in Google Search Central, which is the rulebook for whether review markup qualifies for a rich result in the first place.

That is still worth acting on. Structured data guidelines are the terms of the feature. Markup that ignores them has no claim on the star rating, and there is nothing to appeal when the rule was published in advance.

Read the scope twice, because it is broader than the markup alone. The guidance covers the reviews shown on the page and the structured data. Feeding an average into AggregateRating while the underlying reviews were bought is the exact case the new line describes.

Incentivized reviews are not banned. Undisclosed ones are.

This is the distinction to get right before anyone panics in a client meeting. Asking a customer for a review and thanking them with a discount code is still permitted. What the documentation asks for is that the incentive is disclosed clearly and prominently. The problem is the silence, not the voucher.

"Clearly and prominently" is doing the work in that sentence. A clause buried in a terms page is neither clear nor prominent. A disclosure sitting with the review itself, where someone reading the star rating will see it, is much closer to what the wording describes. Google does not prescribe a format, so placement is a judgement call, and the safe direction is more visible rather than less.

Who this affects most

Stores running review-for-voucher or review-for-free-sample campaigns after purchase.
Service businesses offering a discount on the next booking in exchange for a rating.
Sites publishing product reviews written by staff or supplied by a vendor rather than by someone who used the product.
Anyone using a third-party review widget whose collection method has never been checked.

What this means for Thai marketers

Review-for-reward is ordinary practice in Thai retail. A coupon after a review, a free sample for a rating, bonus loyalty points for a photo review: none of this is unusual on a Thai store, and the same tactic carries over into the review widgets bolted onto Shopify and WooCommerce builds. Under the updated guidance the campaign itself is fine. Running it with no visible disclosure beside the review is what puts the stars at risk.

Two jobs follow from that. The first is finding out how the reviews were actually collected, which usually means asking the marketing team rather than reading code. The second is checking what the review platform does about disclosure, because plenty of them record an incentivized review internally and show the reader nothing.

Star ratings are one of the few visual differences left on a Thai results page full of near-identical listings, and they appear on product and service queries where a click has real value. Losing eligibility over an undisclosed coupon is a poor trade. If review collection sits inside a wider ecommerce marketing programme, the disclosure question belongs in the same conversation as the campaign that generates the reviews, not in a separate technical backlog.

How to check a site this week

List every source of reviews shown on the site: on-site form, review platform, marketplace import, supplier feed.
For each source, ask whether anything was given in return for the review.
Where the answer is yes, put a disclosure the reader can see next to the review, not only in the terms.
Look at the JSON-LD. An AggregateRating that averages incentivized reviews carries the same problem as the reviews themselves.
Remove ratings that were never based on someone using the product.

Questions people are asking

Will Google remove my star ratings?

Google did not announce removals, a date, or an enforcement action. The documentation sets the conditions for review rich result eligibility, and markup that does not meet them has no claim on the feature.

Can I still give a discount in exchange for a review?

Yes, provided the review reflects real use of the product or service and the incentive is disclosed clearly and prominently.

Where should the disclosure go?

The documentation asks for clear and prominent without naming a format. Next to the review is a safer reading than a footer or a policy page.

Does this apply to aggregate ratings as well?

The guidance covers the reviews on the page and the structured data markup, and review snippet markup includes both Review and AggregateRating.

The short version

Fake reviews were never allowed. What is new is the explicit line about incentivized reviews and the requirement to disclose the incentive where readers can see it. Sites that already say "this reviewer received a free sample" have nothing to fix. Sites that pay for reviews quietly now have a written rule pointing at them.

If nobody has checked how your reviews are collected against what your markup claims, that is a short piece of work worth doing before it costs you the stars, and it fits naturally into an ongoing SEO programme.