Digital MarketingSEO & AI Search
Google Adds Manual Action Triggers for Fake Reviews
Google quietly expanded its review snippet documentation with three new prohibitions on fake and undisclosed incentivized reviews, and it's spelling out manual action as the penalty.

Key takeaways
- Google updated its review snippet guidelines on July 27, 2026, adding three new bans on fake or undisclosed incentivized reviews.
- Violating the guidelines can trigger a manual action; sites must fix the issue and submit for reconsideration to recover.
- The changes target reviews not based on genuine product or service experience, and paid reviews that don't clearly disclose the incentive.
- Google's changelog frames the update as an effort to improve user review transparency, tying it to its broader Reviews System.
- E-commerce and review-heavy sites should audit incentivized review programs now, before a manual action shows up in Search Console.
What Google Changed
Google updated its review snippet documentation on July 27, 2026, adding three new guidelines that can now trigger a manual action against a site, according to Search Engine Journal, which reviewed the changelog. The core addition bans fake or undisclosed incentivized reviews, both in on-page content and in structured data markup.
Two of the new prohibitions get specific: reviews that aren't based on a genuine experience of a product or service, and reviews written in exchange for money, discounts, vouchers, or free products that don't clearly and prominently disclose the incentive. Google's own changelog states the reason plainly: to improve user review transparency.
Why It Matters, What To Do This Week
This lands squarely on e-commerce, SaaS review pages, and any brand running incentivized review programs through vendors or affiliates. These guidelines sit under the same section covering Google's algorithmic Reviews System, which the company has already built to evaluate first-party review content for authenticity and expertise.
The move fits a pattern: Google keeps writing enforcement mechanics into public docs rather than leaving them as internal signals, similar to how it has handled other search enforcement disputes, including the recent court ruling that blocked Google's DMCA claims against SerpApi over search data scraping.
- Audit every incentivized review campaign this week: is the discount, voucher, or free product disclosed clearly and prominently on the review itself, not buried in a footer?
- Check structured data markup for review snippets against actual on-page disclosure language; mismatches are now an explicit violation.
- If you've run review campaigns without disclosure, fix the copy and markup before Google flags it, since the only path back after a manual action is reconsideration.
The timing also lands as Google's core search business faces its own scrutiny, with search revenue growth slowing to 17% in Q2, giving the company more reason to protect the trust signals that keep users on its results pages.
Visit the Digital Marketing hub for more SEO compliance updates.
Advertiser disclosure: some links in our articles are affiliate links, and CMO Mag may earn a commission or referral fee if you sign up or buy through them, at no cost to you. It never affects our editorial coverage. See our advertising & affiliate policy.
More in Digital Marketing
View allGoogle's AI Opt-Out Setting May Cost Publishers Top Stories
Google has started running the Top Stories carousel inside AI Overviews instead of below them, and the new AI opt-out setting in Search Console may determine who gets left out.
Creators Now Co-Develop Products, Not Just Post About Them
A new survey of 125 brand and agency professionals shows creator marketing has moved past awareness plays into seasonal campaigns, product launches and, in some cases, actual product co-development.
Claude Share Pages Leaked Into Google Despite a Robots Block
Anthropic's shared Claude chats turned up in Google search results this weekend, exposing a textbook conflict between robots.txt and noindex that any marketing team could replicate by accident.




Discussion
No comments yet. Be the first to say something worth reading.