// GUIDE · 2026-07-27

Google's review snippet guidelines: fake and incentivized reviews, manual actions, and how to keep your star rich results (2026)

In July 2026 Google added a single 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" — and backed it with a warning that violating sites may face a manual action. The star ratings that appear beneath a result in search are a rich-result feature Google grants, and one it can revoke by hand when the reviews behind them are fabricated or hide the incentive that produced them. This guide explains exactly what the new guideline prohibits and what it still permits (incentivized reviews are fine when the experience is genuine and the incentive is clearly disclosed), how a structured-data manual action actually works — the markup ignored, the star result gone, the reconsideration request required to clear it — and how it fits Google's wider 2026 pattern of tightening authenticity and disclosure across every review surface. Then it draws the strategic conclusion most coverage skips: a rich result is a single, revocable feature on one channel Google controls, so your social proof should never depend on it alone. The durable move is to keep your on-page markup scrupulously honest and put the genuine reviews behind it to work as content across the many surfaces Google's review-snippet enforcement cannot touch.

KompozyTurn one idea into a week of content — across every platform, published for you.
Get Started →
Last verified · 2026-07-27 · by Moe Ameen

One line in the docs, a real penalty behind it

The change was small enough to miss and consequential enough that the SEO industry caught it within days. In July 2026, around the 24th, Google added a guideline to the documentation for its Review Snippet structured data — the markup behind the star ratings that can appear under a page in search results. The new line reads: "Don't include fake or undisclosed incentivized reviews on your page or in your structured data markup." Two sentences of context follow it, and a warning: sites that violate it may face a manual action. The full news brief with the exact wording and reporting is in the companion news entry; this guide is the operator's version — what it prohibits, what it still allows, how the penalty works, and what to actually do about it.

The reason a single documentation line matters is that review snippets are a rich result Google grants, not a right your page holds. The star rating you see in a SERP is Google choosing to render your markup. When the reviews behind that markup are fabricated or hide the incentive that produced them, Google's response is not just to demote the page in some ambient way — it is to revoke the feature by hand and, if warranted, apply a manual action that names the violation. That makes this a rare case where the enforcement is specific, visible, and directly tied to something you control on the page.

What the guideline actually prohibits

Google gave two concrete examples, and the distinction between them is worth reading carefully. The first prohibited case is reviews that aren't based on a genuine experience of a product or service — in plain terms, fabricated reviews, whether invented outright, bought from a review farm, or written by people who never used the thing. The second is reviews written in exchange for a benefit — money, a discount, a voucher, a free product — that don't clearly and prominently disclose that incentive. The operative words in the second case are "undisclosed" and "clearly and prominently." A review someone was paid or comped for is not automatically off-limits; a review someone was paid or comped for and that pretends to be spontaneous is.

That is the part most panic-reads get wrong. This is not a ban on incentivized reviews, and it is not a ban on asking customers for reviews. Incentivized reviews remain permissible in your markup when two conditions hold together: the reviewer had a real experience of the product or service, and the incentive behind the review is disclosed openly on the page. What the guideline targets is deception — ratings that are either invented or quietly paid for and then presented as organic customer sentiment. It brings the review-markup rules in line with the authenticity and disclosure standards Google already applies to reviews on other surfaces, and with the broader regulatory norm that a material connection behind an endorsement has to be disclosed. The through-line across all of Google's 2026 quality moves is the same one covered in the enforcement-layer guide: the target is deceptive or low-value practice, never the mere existence of a review or a tool.

How a structured-data manual action works

A manual action is a penalty applied by a human reviewer at Google, not an automated ranking adjustment, and it behaves differently from the algorithmic demotions that arrive silently through core and spam updates. When a reviewer decides a page's review markup violates the guidelines, the specific consequence for structured data is that Google ignores the markup. The page itself can still rank and appear in results — it does not get de-indexed for this — but the star-rating rich result disappears, because Google no longer trusts the data feeding it. The visible cost is the loss of the stars, the review count, and the click-through lift they provide.

Unlike an algorithmic demotion, a manual action tells you it happened. It appears in the Manual Actions report inside Google Search Console, with the violation category named. And it does not clear on its own: recovery is a defined, two-step process. You remedy the problem — remove the fabricated reviews, add clear and prominent disclosure to the incentivized ones, or strip the offending markup — and then you submit a reconsideration request, asking a Google reviewer to re-examine the site and lift the action. That path back is the upside of the manual rail; the downside is that until you complete it, the feature stays gone. For how the manual-action and reconsideration machinery works across the rest of Google's spam policies, the spam-update guide covers the wider enforcement picture.

Where this sits in Google's 2026 tightening

This guideline did not arrive in isolation. Through 2026 Google steadily sharpened enforcement of content authenticity across every surface it controls — faster spam updates, scaled-content-abuse enforcement aimed at mass-produced pages, and a documented change making spam reports a formal input to manual actions. The review-snippet update is the same instinct applied to a narrow, high-value feature: rich results are a trust signal Google lends to your listing, and Google is increasingly unwilling to lend that trust to content it judges deceptive. Read alongside the rest of the year's moves, the message is consistent. Google is not banning reviews, incentives, or AI; it is raising the cost of faking the signals that earn preferential treatment in search.

It is also worth being precise about scope, because the fear tends to over-generalize. Every part of this guideline concerns review structured data on your own indexed web pages. It does not govern how your business is reviewed on third-party platforms, how testimonials perform on social feeds, or how a customer story lands in an email. Those surfaces run their own systems and their own rules. The exposed asset here is narrow and specific: the star rich result attached to pages on the site you own. Knowing exactly what is at risk keeps you from either ignoring the change or overreacting to it.

A compliance checklist for your review markup

The remediation is unglamorous and entirely doable. Mark up only reviews that are real and reflect a genuine experience of the product or service — never invented, never purchased, never written by anyone who did not use it. Where a review was incentivized in any way, disclose the incentive clearly and prominently on the page itself, not buried in a footer or a linked policy. Make sure the review structured data matches the reviews actually visible on the page; markup that claims ratings a visitor cannot see is a classic mismatch that draws scrutiny. Avoid review gating — the practice of routing happy customers to leave public reviews while diverting unhappy ones elsewhere — because it manufactures a rating that is not a genuine reflection of experience. And keep to the technical eligibility rules for the Review Snippet type, since ineligible or self-serving markup is ignored regardless of authenticity.

None of that is exotic. The businesses that get caught by this guideline are overwhelmingly the ones that treated review markup as a growth hack — aggregating ratings they did not earn, or comping reviews and staying quiet about it — rather than as an honest representation of real customer sentiment. If your reviews are genuine and your disclosures are clear, a reviewer who looks at your page finds nothing to act on. That is the whole defense, and it is the same principle that protects every other kind of content under Google's 2026 enforcement: be the real thing, visibly.

The strategic point: a rich result is a single point of failure

Here is the conclusion most coverage of this update skips. A star rich result is one feature, on one channel, granted at Google's discretion and revocable by a single manual action. It is genuinely valuable — stars lift click-through — but a marketing operation whose social proof lives only inside that one rich result is fragile by design. One reviewer's judgment, one policy tightening, one markup mismatch, and the visible proof of your reputation vanishes from the surface you were relying on. The lesson is not "stop using review markup." Keep it, keep it honest, and keep the stars. The lesson is that your credibility should not depend on it alone.

Genuine reviews are far more than markup fodder, and this is where the guideline quietly does you a favor by making authenticity the only safe path. A real customer testimonial — the exact thing Google now rewards over fabricated ratings — is the single most persuasive content asset most businesses own, and almost all of them underuse it, letting it sit as a star count on one page instead of putting it in front of the audience that actually decides. The durable strategy is to keep your on-page markup scrupulously compliant and, in parallel, activate the genuine reviews behind it as social proof across every surface Google's review-snippet enforcement cannot reach.

Where Kompozy fits: social proof that outlives a rich result

Kompozy is a content generation and multi-platform publishing engine, and its relevance to this specific news is a matter of channel diversification, not markup management. It does not write your structured data or manage your review rich results — be clear about that, because a tool that claimed to would be selling you the same single point of failure this guide warns against. What Kompozy does is take the honest asset the guideline rewards — a genuine customer review, result, or testimonial — and turn it into social proof that lives everywhere Google's review-snippet manual actions do not govern. Across its eighteen output formats, one real testimonial becomes a set: a Quote Graphic that frames the customer's words in your brand style, a Carousel that walks through their before-and-after, a Persona Short where your avatar delivers the story, a photo post, a Persona Tweet, and an email newsletter feature — then it schedules and publishes them across the eight social platforms plus blog and email.

The honesty discipline that keeps your review markup safe is the same discipline Kompozy builds into how content ships. Every output is generated from a written Persona Brief that fixes a real voice and point of view, filtered for the generic AI-tell phrasing that reads as inauthentic, and — critically — routed through a per-post review gate where a human approves each piece before it publishes. That checkpoint is where you make sure a testimonial is represented faithfully, that any material connection is disclosed the way it should be, and that nothing goes out overstated. Autopilot can hold the cadence, but the review gate is what keeps the operation on the honest side of the line, the same way keeping only genuine reviews in your markup keeps a Google reviewer with nothing to act on.

So the practical playbook after this update is two moves, not one. First, audit and fix your on-page review markup — real reviews only, incentives disclosed, markup matching what a visitor sees — so your star rich result stays eligible and no manual action has grounds to land. Second, stop letting your best proof live only there. Take the genuine reviews you legitimately collect and run them, through Kompozy, as recurring social-proof content across the many surfaces Google's review-snippet enforcement never touches. That is a reputation strategy with no single point of failure: honest where Google can penalize you, and distributed everywhere it cannot.

Frequently asked questions

What did Google change about review snippet guidelines?

In July 2026 Google added a guideline to its Review Snippet (Review and AggregateRating) structured data documentation, spotted around July 24: "Don't include fake or undisclosed incentivized reviews on your page or in your structured data markup." It cites two examples — reviews not based on a genuine experience of a product or service, and reviews written in exchange for a benefit (money, discounts, vouchers, free products) that don't clearly and prominently disclose the incentive.

Does Google now ban incentivized reviews?

No. The guideline does not prohibit incentives. An incentivized review is still allowed in your review markup as long as the reviewer had a genuine experience of the product or service and the incentive is disclosed clearly and prominently. What is banned is fabricated reviews and incentivized reviews that hide the incentive — pay-for-praise presented as if it were organic. Disclosure and genuine experience are the dividing line, not the incentive itself.

What is a structured-data manual action and how do I fix it?

It is a penalty a human reviewer at Google applies when a page's structured data violates the guidelines. For review markup, the effect is that Google ignores the markup — the page can still appear in results but loses its star-rating rich result. It surfaces in the Manual Actions report in Google Search Console with the violation named. It does not clear on its own: you remove the offending reviews or markup, then submit a reconsideration request for a Google reviewer to re-examine the site and lift the action.

Does this affect testimonials I post on social media or email?

No. The guideline concerns review structured data on your own indexed web pages. Testimonials and social-proof content you publish to TikTok, Instagram, YouTube, LinkedIn, X, Pinterest, Threads, or an email list are governed by those platforms' own rules, not by Google's review-snippet manual actions. Genuine customer reviews are, in fact, ideal source material for that off-site social-proof content.

How do I keep my star rich results safe?

Only mark up reviews that are real and reflect a genuine experience, disclose any incentive clearly and prominently on the page, follow the technical eligibility rules for the Review Snippet type, and audit your markup so it matches the visible reviews on the page. Do not aggregate purchased or fabricated ratings, and do not gate reviews to filter out negative ones. Honest, on-page, disclosed reviews are what keeps the rich result and keeps a reviewer with nothing to act on.

The direct answer

In July 2026 Google added a guideline to its review snippet structured data docs — "Don't include fake or undisclosed incentivized reviews on your page or in your structured data markup" — and warned that violating sites may face a manual action. It bans fabricated reviews and incentivized reviews that hide the incentive, but still permits incentivized reviews when the experience is genuine and the incentive is clearly disclosed. A structured-data manual action makes Google ignore the markup, removing the star rich result until the site fixes the issue and files a reconsideration request.

Get started → · ← All guides · Compare Kompozy vs other tools