Google Tightened Review Schema Rules. Your Trust Signals Need to Be Clean.

Review schema has always been treated as a formatting exercise. Get the properties right, pass the Rich Results Test, collect the stars. The July 2026 update reframes it. Google is now asserting a claim about the reviews themselves, not just the way they are encoded, and it is doing so in the same document that governs whether your rich result appears at all.

The practical version: review markup is not a place to launder trust. Your reviews, your testimonials, your structured data, and the copy a visitor actually reads all have to describe the same reality.

What Google actually added

The review snippet structured data documentation gained a new guideline on July 24, 2026. The wording is direct:

Don’t include fake or undisclosed incentivized reviews on your page or in your structured data markup.

Google gives two examples of what falls inside that prohibition. The first is reviews that are not based on a genuine experience of a product or service. The second is reviews written in exchange for a benefit, such as money, discounts, vouchers, or free products, that do not clearly and prominently disclose the incentivization. Google’s changelog states the reason for the change in six words: to improve user review transparency.

Two details matter more than the headline. First, the guideline covers the page and the markup. This is not a structured data validation rule. A review that fails the test is a problem even if you never wrapped it in JSON-LD. Second, this guideline sits inside the section of the documentation that carries Google’s manual action language: if a site violates one or more of these guidelines, Google may take manual action against it, and the site can request reconsideration after fixing the problem. Search Engine Journal and Search Engine Land both covered the change when it landed.

Notice what Google did not say. It did not ban incentivized reviews. Offering a gift card for a review is still allowed under this guideline, as long as the incentive is disclosed clearly and prominently, and as long as the review reflects a real experience. The prohibited thing is the concealment, not the incentive.

Why this lands harder in 2026 than it would have in 2019

Reviews stopped being decoration a while ago. They are now conversion proof, local ranking input, and increasingly, the raw material that AI systems summarize on your behalf. BrightLocal’s most recent Local Consumer Review Survey puts numbers on how far that has gone.

The same survey found that 97 percent of consumers believe businesses should face some consequence for fake reviews, and 46 percent think offenders should be removed from Google search results entirely. Google enforcing a transparency rule here is not Google being unusually strict. It is Google catching up to what its users already expect.

The AI summary number is the one worth sitting with. When 82 percent of people are reading a generated summary of your reviews, the thing being summarized is your whole review corpus, including the four-star review that mentions a scheduling problem. Padding that corpus with reviews that were bought, staged, or written internally does not just risk a manual action. It teaches the summarizer something about your business that is not true, which is a fragile place to build a pipeline on.

The eligibility rule most sites already break

Before the new guideline, there was an older one that catches more sites than anything Google published this month. In September 2019, Google stopped showing self-serving review stars for LocalBusiness and Organization schema. The current documentation still carries it: if the entity being reviewed controls the reviews about itself, pages using LocalBusiness or any other Organization type are ineligible for the star review feature.

Self-serving means a review about entity A placed on entity A’s own website. Adding it directly to your markup counts. So does pulling it in through an embedded third-party review widget. The widget being third-party does not change who the review is about or whose site it is on.

This is why so many businesses have valid, error-free review markup that has never produced a single star in a search result. The markup is not broken. The page is not eligible. Those are different problems with different fixes, and it is worth knowing which one you have before you start editing JSON-LD.

What clear and prominent disclosure looks like

Google did not publish a disclosure template, which means the standard is going to be read the way regulators read it: would a reasonable person see it, and would they understand it, at the moment they are forming an opinion. A line in your terms page does not meet that bar. Neither does a footnote below the fold.

The aggregate mismatch is the one we find most often, and it is rarely deliberate. A plugin caches an average, someone prunes old reviews, and the number in the markup drifts away from the number on the page. Under the old reading that was a data hygiene issue. Under the new reading it is a page making a review claim it cannot support, which is closer to the thing Google just prohibited.

This is not only a Google problem

Google's guideline arrived roughly two years after the Federal Trade Commission's Trade Regulation Rule on the Use of Consumer Reviews and Testimonials, which took effect on October 21, 2024. The two overlap heavily, and the FTC version has sharper teeth.

The rule prohibits creating, buying, or selling fake consumer reviews and testimonials, including ones generated by AI. It prohibits paying for either positive or negative reviews. It requires insiders, meaning officers, managers, employees, and their immediate relatives, to clearly disclose their relationship when writing a review. It prohibits company-controlled review sites that present themselves as independent, certain review suppression practices, and buying fake indicators of social media influence. For knowing violations the FTC can seek civil penalties, set at 51,744 dollars per violation when the rule took effect and adjusted annually for inflation.

So the compliance picture is layered. Google can take your stars. The FTC can take considerably more. If you have been treating incentivized review disclosure as an SEO nicety, the honest framing is that it has been a legal requirement in the United States since late 2024, and Google has now made it a search requirement too. One cleanup covers both.

Audit your review trust signals

The checklist below is the one we work through on client sites. Check what is actually true today, not what the policy document says should be true.

A 30-day cleanup

Most of the work here is inventory, not engineering. The order matters, because remediating before you have a complete list produces a page that looks clean and an underlying dataset that is still wrong.

What we check first

When a review integrity question comes to us, we do not open the JSON-LD first. We open the page and count. If the visible reviews do not reconcile with the aggregate in the markup, everything downstream of that is noise, and it is the fastest signal that the review system has been running unattended.

After that, three things in order. Whether the page was ever eligible for stars in the first place, because a surprising number of review implementations are technically flawless and structurally disqualified. Whether any review in the set came from an incentive, which usually requires talking to whoever runs the email flow rather than reading the site. And whether the review plugin is generating markup the team has never actually seen, which is common enough that we treat plugin-generated structured data as unverified until proven otherwise.

None of this is exotic work. It is the same discipline that keeps the rest of a technical SEO program honest: make the data on the page and the data in the markup describe the same thing, then keep them that way. The businesses that feel this update hardest are the ones where reviews were outsourced to a plugin and a vendor and then never looked at again. For regulated and high-trust verticals, where a review is often the last thing a person reads before making an expensive decision, that gap is worth closing regardless of what Google publishes next. We see it most often on med spa and law firm sites, where the incentive program and the website are usually managed by two different people who have never compared notes.

If you want a second set of eyes on how your review markup, disclosure, and page content line up, send a message or a Loom and we will take a look.

Frequently Asked Questions

Sources

• Review Snippet (Review, AggregateRating) Structured Data - Google Search Central
• Making Review Rich Results more helpful - Google Search Central Blog, September 2019
• Google says don't include fake or undisclosed incentivized reviews in review snippet structured data - Search Engine Land, July 24, 2026
• Google Expands Review Guidelines And Warns Of Manual Actions - Search Engine Journal
• Local Consumer Review Survey - BrightLocal
• Trade Regulation Rule on the Use of Consumer Reviews and Testimonials - Federal Register, August 22, 2024
• FTC Announces Final Rule Banning Fake Reviews and Testimonials - Federal Trade Commission

Search documentation and regulatory guidance both change. This article was reviewed on July 27, 2026 against the sources listed above. Confirm the current wording of Google's review snippet guidelines and the FTC rule before making a compliance decision. See our editorial review policy for how we source and update this material.