Google Cracks Down on Fake and Incentivized Reviews in Review Snippets
On July 24, 2026, Google quietly added a new 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." It is a single sentence, but it closes a loophole that thousands of sites have leaned on for years — and it puts every star rating you display in search results on notice.
If your product pages, local listings or service pages show those familiar gold stars in Google's results, this update is a direct instruction to audit how you collect and mark up reviews. Ignore it and you risk a manual action that strips the rich result — and, in the worst case, dents your visibility. Here is exactly what changed, why it matters, and what to do before Google starts enforcing at scale.
What Google actually changed
Google did not launch a new algorithm or ranking system. It amended the review snippet structured data guidelines — the rules that decide whether your Review and AggregateRating markup is eligible to render as a star rating in search. The new guideline names two specific practices as off-limits:
- Fake reviews — ratings that are not based on a genuine experience with the product or service being reviewed.
- Undisclosed incentivized reviews — reviews written in exchange for a benefit (money, discounts, vouchers, free products, gift cards) where that compensation is not clearly disclosed.
The key word is undisclosed. Incentivized reviews are not banned outright — asking a customer for feedback after sending a sample is still allowed. What is banned is hiding the incentive. If a rating was earned in exchange for something of value, that fact must be visible to the reader; otherwise it cannot be counted in the reviews you mark up for a snippet.
This aligns Google's structured data rules with the review policies it already enforces on Google Business Profiles and, more broadly, with consumer-protection expectations set by regulators such as the U.S. Federal Trade Commission, which has fined companies for undisclosed paid reviews. In other words, Google is closing the gap between what it forbids in profiles and what it has tolerated in markup.
Why this matters more than a one-line edit suggests
Review snippets are one of the highest-leverage rich results available. A row of gold stars under your listing raises click-through rates, signals trust before a user even lands, and — for local and e-commerce sites — can be the deciding factor in a crowded results page. That is precisely why the format has been abused: self-authored testimonials, star ratings scraped from unrelated sources, and "leave a 5-star review for 10% off" campaigns marked up as if they were organic.
Google's documentation is explicit that breaking review snippet guidelines can trigger a manual action, which removes the rich result and can be applied site-wide for structured data spam. Unlike an algorithmic suppression that quietly fades, a manual action shows up in Search Console and requires a reconsideration request to lift. For a business that depends on those stars for click-through, losing them overnight is a measurable revenue hit.
There is also a second-order effect worth noting. As search shifts toward AI-generated answers, the trust signals a page carries increasingly feed how AI systems describe a brand. Clean, verifiable review data supports that; fabricated ratings become a liability the moment a model — or a competitor filing a spam report — surfaces the discrepancy. If you are already rethinking how you earn trust for AI search and AI Overviews, review integrity belongs on the same checklist.
Allowed vs. not allowed: a quick reference
The line between a compliant review program and a risky one is narrower than most teams assume. Use the table below as a first-pass filter.
| Practice | Status | What to do |
|---|---|---|
| Organic customer reviews from real buyers | Allowed | Keep collecting; this is the gold standard. |
| Review left in exchange for a discount, clearly disclosed | Allowed | Show the disclosure next to the review; you may mark it up. |
| Review for a free product, no disclosure | Not allowed | Add a visible disclosure, or exclude it from markup. |
| Self-written or staff-written "testimonials" | Not allowed | Remove from review markup entirely. |
| Ratings copied from an unrelated product or site | Not allowed | Delete; only mark up reviews about the specific item. |
| Purchased or bot-generated reviews | Not allowed | Remove and stop the vendor relationship. |
A four-step compliance checklist
You do not need to wait for a warning in Search Console. Treat the next few weeks as a grace window and work through these steps.
1. Inventory every page with review markup
Pull a list of URLs that emit Review or AggregateRating schema. Google's Rich Results Test and Search Console's "Review snippets" enhancement report will surface them, and a site crawler or one of the website SEO audit tools that parse structured data can flag them at scale. You cannot fix what you have not mapped.
2. Trace where each rating came from
For every marked-up review, answer one question: did a real customer leave this after a genuine experience? Reviews you cannot trace to a verifiable purchaser — imported testimonials, legacy widgets, ratings of a parent brand shown on a product page — are the highest-risk items. When in doubt, exclude them from markup rather than gamble the whole snippet.
3. Add disclosures to incentivized reviews
If part of your program offers a perk for feedback, keep it — but make the incentive visible on the page next to the review (for example, "Reviewer received a free sample"). The disclosure has to be human-readable, not buried in a footer or terms page. Reviews with a clear disclosure remain eligible; the same reviews without one do not.
4. Fix the markup and monitor Search Console
Update your schema so AggregateRating reflects only compliant reviews, then re-validate with the Rich Results Test. Watch the Manual Actions and Review snippet reports for the next several weeks. If you run reviews through a plugin, confirm it lets you exclude specific sources — many of the best WordPress SEO plugins generate review schema automatically, and you will want control over exactly what they publish.
Who is most exposed
Three types of site should treat this as urgent rather than routine:
- E-commerce and product pages that aggregate ratings, especially stores syndicating reviews across variants or copying a brand-level score onto individual SKUs.
- Local and service businesses that display self-collected testimonials as star ratings. Because this update mirrors Google Business Profile policy, local sites face the tightest scrutiny — see our note on how Business Profiles now feed local SEO.
- Affiliate and review sites running incentivized-review programs at scale without per-review disclosure.
Sites built on organic, verifiable reviews have little to worry about — for them this is a formality. The exposure sits with anyone who has been treating star markup as a growth hack rather than a reflection of real customer sentiment.
The takeaway
Google's July 24 update is small in wording and large in intent: star ratings in search are meant to represent honest, disclosed feedback, and the structured data behind them is no longer a place to cut corners. The safe path is also the durable one — collect real reviews, disclose any incentives plainly, and mark up only what you can stand behind. Do that audit now, while enforcement is still ramping, and you keep your stars instead of scrambling to earn them back after a manual action.
