Google Changed Its Review Rules on 24 July: Undisclosed Incentives Now Cost You the Stars

Google updated its review snippet documentation on 24 July 2026 with a line that reads simply and bites hard: "Don't include fake or undisclosed incentivized reviews on your page or in your structured data markup." Read the middle word carefully. Incentivized reviews are still allowed. What is prohibited is a review "written in exchange for a benefit (such as money, discounts, vouchers, or free products)" that does not "clearly and prominently disclose the incentivization." If you have ever sent a discount code in exchange for a review, or shipped a free unit to someone who then wrote about it, the fix is a disclosure, not a deletion.

What actually changed, and what did not

The change lives on Google's review snippet structured data page, stamped "Last updated 2026-07-24 UTC". The prohibited examples now cover both reviews that "aren't based on a genuine experience of a product or service" and undisclosed incentivized ones.

Two scoping points that decide whether this is your problem:

It applies to your page and your markup, not to third-party platforms. This is about reviews you publish and mark up on your own site. Reviews on Google Business Profile run under a separate policy surface that this page does not change, so nothing here should be read as guidance on that; if local search is your channel, the setup work is in the free lead channel local businesses leave empty.
It reaches further than product pages. Review snippets can appear for Book, Course list, Event, Local business, Movie, Product, Recipe and Software App, plus schema types including Game, MediaObject, MusicRecording and Organization. A software company with an AggregateRating on its Organization markup is inside the rule, not outside it.

The enforcement route, and why it stings differently

Trade coverage of the update, from PPC Land on 24 July 2026, describes the enforcement as a manual action notified in Search Console that causes the structured data to be ignored while the pages stay in the index. We attribute that specific outcome to that source rather than to Google, because Google's own manual actions documentation describes the general consequence more broadly: a manual action is issued when "a human reviewer at Google has determined that pages on the site are not compliant with Google's spam policies," and "some or all of that site will not be shown in Google search results." Structured data issues are listed among the manual action types, alongside thin affiliate content and user-generated spam.

Either way, the practical loss is the same and it is worse than it looks. Star ratings in a result listing are a click-through multiplier, not a ranking factor. Losing them does not move your position; it quietly reduces the share of impressions that become visits, on exactly the commercial pages where that share is worth the most. You can hold rank and lose a third of the traffic.

Where undisclosed incentives hide in a normal small business

Very few sites set out to buy reviews. Most of the exposure is accidental and sits in one of these five patterns:

The post-purchase discount email. "Leave a review, get 10% off your next order." That is a voucher for a review. The reviews it produces need disclosure wherever they are displayed.
Seeded product. Free units to creators, testers or a customer panel, whose write-ups then appear on your site as reviews or testimonials.
Affiliate roundups. A "best of" page rating products you earn commission on. The commission is a benefit tied to the outcome, and this pattern also sits close to the thin-affiliate manual action type; the disclosure standards that actually hold up are the ones we set out in the affiliate programme piece.
Employee and insider testimonials. Staff, contractors or founders' relations reviewing the product without saying so.
Prize draws. "Review us and be entered to win." A chance at a benefit is still a benefit.

What a compliant disclosure looks like

The requirement is that the incentivization is disclosed "clearly and prominently." Three placement rules follow from that phrasing, and the first is the one sites get wrong:

In the review, not in a policy page. A sentence in your terms saying "some reviewers receive free products" is not prominent relative to the individual review a reader is looking at. The disclosure belongs adjacent to the review text itself.
In the rendered page, not only in the markup. The rule names both "your page" and "your structured data markup." A hidden disclosure that only exists in JSON-LD fails the visible-content half, and hidden content is separately listed among structured data manual action triggers.
Specific about the benefit. "Sponsored" is vague. "This reviewer received the product free of charge" and "This review was submitted in exchange for a 10% discount code" name the thing.

Wording you can paste, placed directly under the reviewer name or above the review body: "Incentive disclosure: this customer received a 10% discount code in exchange for submitting a review. The review text was not edited or approved by us." The second sentence is not required by Google, but it answers the next question a sceptical reader has, and it is the difference between a disclosure that damages trust and one that builds it.

US sellers have a second, older obligation

Google's rule is a search policy. Separately, the FTC's Rule on the Use of Consumer Reviews and Testimonials, 16 CFR Part 465, published at 89 FR 68077 on 22 August 2024, addresses this conduct as a matter of law. Its sections cover fake or false consumer reviews and testimonials (465.2), buying positive or negative reviews (465.4), insider consumer reviews and testimonials (465.5), company-controlled review websites (465.6), review suppression (465.7) and fake indicators of social media influence (465.8). We are not quoting the operative text or any penalty figure here, because the FTC and Federal Register pages did not open for us this run and we do not restate regulatory language we have not read. Treat the section list as a map of where to have your own lawyer look, particularly 465.5 if employees or founders' relations have ever left a review, and 465.7 if you filter which reviews get published.

The overlap is convenient: a disclosure practice built to satisfy the search policy is broadly the same practice that a fair-trading regulator is looking for. Doing it once covers both.

If you already have a manual action

Open Search Console and go to the Manual Actions report. A green check means nothing is pending. If something is listed, expand it to see the affected page patterns, then work in this order: fix every affected page, not a sample; remove or correct the structured data on each; add visible disclosures where the incentive was real; and only then submit the reconsideration request. Google's documentation asks that the request explain the quality issue, what you did to fix it, and the outcome, and warns that reviews take "several days or weeks." A request submitted before the fixes are complete restarts that clock.

One temptation to resist: stripping the Review and AggregateRating markup from every page to make the problem disappear. That removes the symptom and the asset. Genuine reviews with correct required properties, author, itemReviewed, reviewRating with a ratingValue, and a name, are still fully eligible for snippets. The rule is not asking you to stop showing reviews. It is asking you to stop showing paid-for ones as though they were spontaneous, which is roughly what Google has spent the past two years doing to every other form of content that looks organic and is not. The audit takes an afternoon. The stars take months to get back.