On July 24, 2026, Google quietly revised its Review Snippet schema — the guidelines that control whether your star ratings and review counts show up as rich results in Google Search. No announcement, no blog post from Google itself. Just an updated page and a new line in the guidelines that every site owner collecting reviews should read before their markup gets flagged.
This isn’t a redesign of how review snippets work. It’s a tightening of what’s allowed inside them — and it lands right on top of an issue a lot of local and ecommerce sites have been quietly getting away with: reviews that aren’t quite real, or aren’t quite disclosed.
What Google Actually Changed
According to Barry Schwartz’s report on Search Engine Land, Google added new guidelines and examples to the review snippet documentation. The core addition is a direct instruction not to include fake or paid reviews without disclosure in your markup — Google’s documentation now states site owners should “not include fake or undisclosed incentivized reviews” on-page or in structured data.
This builds on a pattern. It isn’t the first time Google has tightened this particular document in the last year:
| Date | What Changed | Why It Matters |
| Nov 2025 | Clarified that sites should avoid multiple ways of indicating what’s being reviewed (nesting rules) | Prevents ambiguity so Google can correctly parse which entity a rating belongs to |
| Jul 24, 2026 | Added explicit guidance against fake or undisclosed incentivized reviews in markup | Closes a loophole where paid or fabricated reviews were being marked up as genuine |
The direction is consistent: Google is narrowing the gap between what your markup claims and what’s actually true on the page. That’s worth taking seriously — review snippets are a rich-result eligibility feature, and eligibility can be revoked.
Why This Matters Beyond Compliance
Fake or incentivized reviews without disclosure were already against Google’s product structured data policies. What’s new here is that Google made the review snippet type guidance explicit about it, rather than leaving it implied. In practice, that usually precedes stricter automated enforcement — Google tends to document a rule clearly before it starts penalizing at scale.
This sits alongside a broader trust push across Google’s ranking systems this year. We covered a related thread in Google Search Rankings Shake Again, where volatility tracked closely with sites relying on thin or manipulated trust signals rather than genuine ones.
| Insight
If your review markup is pulling from a review platform that allows incentivized reviews (free products, discounts, gift cards in exchange for a review) and you aren’t labeling those clearly, this update is aimed squarely at you — even if you didn’t write the reviews yourself. |
How to Audit Your Review Snippet Markup
Run through this before your next crawl. None of it requires a developer if your reviews are coming through a standard plugin or platform (Judge.me, Yotpo, Trustpilot, Google’s own review widgets).
- Pull every page with Review or AggregateRating schema using Search Console’s Rich Results report or a manual site: crawl.
- Check your review collection process — are any reviews solicited with a discount, free product, or payment? If yes, they need clear disclosure, on-page and ideally in the review text itself.
- Validate every page with Google’s Rich Results Test to confirm the markup still parses correctly after any edits.
- Check for duplicate signals — the Nov 2025 update flagged sites using more than one method (e.g. both itemReviewed and a separate name field) to indicate what’s being reviewed. Pick one and remove the rest.
- Re-check ratingCount and reviewCount fields match what’s actually visible on the page. Mismatches are one of the most common reasons rich results get suppressed.
- Document your review sourcing policy somewhere your client (or your future self) can find it — this is the kind of thing that becomes an argument during an audit if it isn’t written down.
A Practical Checklist Table
| Check | Priority | Where to Look |
| Incentivized reviews disclosed | High | Review platform settings + on-page review text |
| itemReviewed used once, consistently | High | JSON-LD markup / Rich Results Test |
| ratingCount matches visible review count | Medium | Page front-end vs. schema |
| No fabricated or placeholder reviews | High | Manual spot-check of review source |
| Schema validates with no warnings | Medium | Google Rich Results Test |
What This Means If You’re Also Chasing AI Search Visibility
Review snippets aren’t just a Google Search feature. Structured, disclosed, trustworthy review data is exactly the kind of signal AI systems lean on when deciding whether to cite a business at all. We went deeper on this in How to Rank in AI Search Results — the pattern holds here too: markup that Google trusts enough to show as a rich result is markup that AI Overviews and chat-based assistants are more likely to trust as a citation source.
If your site is also dealing with deeper crawlability issues, it’s worth pairing this audit with the JavaScript rendering checks covered in Your Site Can Rank #1 on Google and Still Be Invisible to ChatGPT, Claude and Perplexity — clean schema doesn’t help if AI crawlers can’t reach the page it’s sitting on.
FAQ
Will this update cause an existing rich result to disappear immediately?
Not automatically. Google’s structured data guideline updates typically get enforced at the next meaningful crawl and re-evaluation of the page, not instantly. But there’s no fixed grace period, so treat this as a “fix now” item rather than a “fix eventually” one.
Does this affect product review snippets and business review snippets equally?
Yes. The guidance sits inside the general Review, AggregateRating structured data documentation, which covers both product reviews and broader review/rating markup across schema.org types.
Where can I check the official, current guidance directly?
Google’s own Search Central changelog logs every documentation update chronologically, including this one, and is the fastest way to confirm you’re looking at the current version rather than a cached summary.
The Takeaway
This is a small documentation change with a clear signal behind it: Google is done treating incentivized-but-undisclosed reviews as a grey area inside structured data. If your review markup has never been audited against the current guidelines, do it this week rather than after something drops.
Sanjeev Kumar is a digital marketing expert with over 14 years of experience in SEO, PPC, content marketing, and online growth strategies. He specializes in search engine optimization, AI-driven marketing, and digital strategy for businesses and agencies worldwide.