Review Snippets: Google’s Fake-Review Ban Explained

Google’s review snippet structured-data guidelines gained a new prohibition on July 24, 2026: fake reviews and undisclosed incentivized reviews are now explicitly banned from your pages and your markup. The addition is one sentence plus two examples — and it turns a long-standing FTC disclosure principle into a rich-result eligibility rule that any site running review schema can lose stars over.

The change landed quietly. Google updated the documentation on a Friday, logged it in its Search Central changelog, and the SEO industry only noticed when Barry Schwartz reported it at Search Engine Roundtable on Monday, July 27 — a three-day lag between the edit and its discovery. Nothing else on the page changed. That makes this a narrow, surgical addition, which is exactly why it is worth reading closely: Google chose to spell out one specific practice.

This guide lays out the exact before-and-after diff, the pre-existing review-markup rules the new line sits beside, what the FTC already required merchants to disclose, a side-by-side cross-reference of the two rulebooks, and a four-step markup-compliance audit — including how to purge non-compliant review data from structured data without losing legitimate snippets.

The update is a single new entry in the Technical guidelines section of Google’s review snippet structured-data documentation — the page that governs when Review and AggregateRating markup can earn the star rating shown under a result. Google’s Search Central changelog logged it as “Added a new guideline to the review snippet documentation about fake and undisclosed incentivized reviews,” and gave a one-line rationale: the change was made “to improve user review transparency.”

The guideline itself is short. Quoted verbatim from the live documentation: “Don't include fake or undisclosed incentivized reviews on your page or in your structured data markup.” Two bulleted examples define what Google means, and they are worth reading as two distinct prohibitions rather than one.

Placement matters too. The new guideline sits directly beneath the pre-existing rule “Don't aggregate reviews or ratings from other websites” in the Technical guidelines list. Google filed it as a peer to its existing anti-manipulation rules — not as a standalone disclaimer or a blog-post announcement. For sites that already treat the review-snippet guidelines as a compliance checklist, this is one more line item on the same list, with the same consequence for violations.

Most coverage states that the change happened. The evidence trail is worth laying out, because it establishes both that the guideline is genuinely new and how narrow the edit was.

• July 22, 2026 — before. A Wayback Machine snapshot of the review snippet documentation captured two days before the update shows the Technical guidelines section with no mention of “fake,” “incentivized,” or “disclosure” anywhere on the page.
• July 24, 2026 — the change. The live page’s own footer timestamp reads “Last updated 2026-07-24 UTC,” and Google’s Search Central changelog carries a matching entry logging the new review-snippet guideline.
• July 27, 2026 — discovery. Search Engine Roundtable published the first report, three days after the doc changed. The report is the discovery vehicle, not the change itself — keep the two dates distinct.

Schwartz’s own read confirms the surgical scope: “Nothing else on the page was changed as far as I can tell, outside of Google adding that new guideline with those two examples.” If your review markup was compliant on July 23, exactly one new question applies to it now — do any of your marked-up reviews fail the fake or undisclosed-incentive test? Everything else in the doc, including the broader rich-results eligibility rules, carries over unchanged.

“Pretty obvious” is doing real work in that sentence. Nobody believed fake reviews were fine before July 24. What changed is that the prohibition now lives in the specific document Google points to when it explains why a page lost its stars — which converts an implicit norm into an explicit, checkable eligibility rule.

The new guideline joins a set of review-markup integrity rules that were already in force and were untouched by this update. Any compliance audit has to check all of them, because a site can pass the new fake-review test and still be ineligible under a rule that predates it.

One adjacent surface to keep separate: Google Business Profile has its own review-manipulation policies, which already prohibited fake, incentivized, and off-topic reviews on the profile side. Search Engine Roundtable frames the July 24 change as bringing the structured-data guidelines more in line with those Business Profile policies. If your review problems live on your profile rather than your markup, that is a different playbook — see our Google Business Profile review triage guide for that surface.

Google’s new guideline names the obvious benefits — money, discounts, vouchers, free products — but doesn’t define how small a benefit can be and still count. For that, the operative framework is the FTC’s Endorsement Guides (codified at 16 CFR Part 255 and revised in 2023), which require disclosure of any connection between a reviewer and a marketer “that a significant minority of consumers wouldn't expect and it would affect how they evaluate the endorsement” — disclosed “clearly and conspicuously.” Three FTC positions set the practical bar.

There is also a dedicated FTC rule specifically targeting fake reviews and testimonials, in force since 2024, with civil-penalty exposure for violations. The practical takeaway for merchants: the legal side of this obligation predates Google’s guideline by years, and it applies whether or not your reviews ever appear in a rich result. If you are building review volume through post-purchase asks, coupons, or sampling programs, design the disclosure in from the start — our compliant review-collection program framework covers what that looks like operationally.

Google’s markup guideline and the FTC’s endorsement framework are structurally the same disclosure principle, enforced by two different bodies with two different consequences. The cross-reference below maps each underlying practice against both rulebooks — the artifact a marketing and legal team can actually work from. Google-side consequences come from the review snippet doc’s own eligibility framing; FTC-side consequences flow from deceptive-advertising enforcement under the FTC Act.

The pattern in the table is the story: for every practice, Google polices visibility while the FTC polices legality. Before July 24, the top two rows only had an FTC-side entry. Now both rulebooks cover the full column — which means a single review-sourcing decision made by a marketing team can simultaneously cost the site its stars and create a legal question for counsel.

If your site emits Review or AggregateRating markup — directly, through your ecommerce platform, or via a review-platform integration — run these four checks. Each maps to a specific rule in the sections above, and together they cover both the new guideline and the pre-existing ones.

Purging non-compliant data without losing legitimate snippets is mostly a filtering exercise, not a deletion exercise. Work in this order:

• Segment the review corpus. Split reviews into verified-organic, incentivized-with-disclosure, incentivized-without-disclosure, and unverifiable-origin. Most review platforms record incentive flags at collection time; if yours doesn’t, that is the first vendor conversation.
• Fix what disclosure can fix. Incentivized-but-undisclosed reviews become compliant when the incentivization is clearly and prominently disclosed with the review. Where the platform supports appending a disclosure badge or label, that preserves both the review and its markup eligibility.
• Exclude what disclosure can’t fix. Reviews that fail the genuine-experience test, and reviews whose origin you cannot establish, come out of the structured-data feed — and out of any AggregateRating math derived from it. Keep the exclusion at the markup layer so legitimate reviews keep generating snippets.
• Keep review content visible. Google recommends that accepted ratings be accompanied by a review comment and the author’s name, and requires review content to be readily available on the marked-up page. Don’t strip visible reviews while cleaning the markup — visibility is itself an eligibility condition.
• Re-test. Run cleaned pages through the Rich Results Test and monitor Search Console for review-snippet status. Responding to the legitimate reviews you keep is its own discipline — our guide to responding to reviews at scale picks up where the compliance work ends.

If review schema is one surface of a larger organic program, fold this audit into your regular technical-SEO cadence rather than treating it as a one-off — this is exactly the kind of documentation-level change our agentic SEO engagements monitor continuously, because Google ships guideline edits like this without announcement posts.

Most compliance write-ups collapse this story into one risk. It is two, on separate axes. Google-side risk is a visibility loss: per the doc’s own troubleshooting framing, non-compliant markup makes the page ineligible for the review-snippet rich result — the stars stop showing, with the click-through consequences that implies. It is an eligibility issue, not a listing in Google’s separate Manual Actions program. FTC-side risk is legal and financial: exposure under deceptive-advertising enforcement, which exists whether or not your pages ever earned a rich result. Same underlying bad practice, two independent enforcement tracks, two different remediation owners — the SEO team fixes one, counsel worries about the other.

What the trend looks like from here. The direction of travel is documentation convergence: Google’s structured-data guidelines are being brought in line with its Business Profile review policies and, in substance, with the FTC’s long-standing disclosure framework. Guideline text tends to precede enforcement attention — Google rarely documents a prohibition it never intends to check. A defensible reading: the July 24 line gives Google a citable basis for pulling review snippets from sites with tainted review corpora, and gives compliant sites a modest relative advantage as non-compliant markup loses eligibility. Sites investing in genuinely-collected, properly-disclosed reviews are accumulating an asset that both rulebooks now protect — consistent with what consumer trust data on reviews has shown about how heavily buyers weight review authenticity.

Projecting forward, the prudent posture is to treat review markup as a regulated surface: inventory it, gate what enters it, and log why each review qualifies. If enforcement tightens — algorithmically or manually — sites with a documented review-sourcing trail can respond in days, while sites that never segmented their corpus face an all-or-nothing choice between pulling review schema entirely and gambling on eligibility. That asymmetry, not the guideline text itself, is the real cost of ignoring this update. For the wider discipline around review acquisition, monitoring, and response, see our reputation-management playbook.