Direct answer

Google’s July 24, 2026 review snippet update makes one point painfully explicit: fake reviews and reviews collected for benefits without clear disclosure do not belong in your review markup. The rest of the review-snippet rules are just as important and frequently misunderstood.

What to remember
  • Google’s July 24, 2026 review snippet update makes one point painfully explicit: fake reviews and reviews collected for benefits without clear disclosure do not belong in your review markup. The rest of the review-snippet rules are just as important and frequently misunderstood.
  • reviews not based on a genuine experience;
  • reviews written in exchange for money, discounts, vouchers, free products, or another benefit when the incentive is not clearly and prominently disclosed.
  • On July 24, 2026, Google added an explicit review snippet guideline:

01

Dataset and period

Google’s July 24, 2026 review snippet update makes one point painfully explicit: fake reviews and reviews collected for benefits without clear disclosure do not belong in your review markup. The rest of the review-snippet rules are just as important and frequently misunderstood.

On July 24, 2026, Google added an explicit review snippet guideline:

Do not include fake or undisclosed incentivized reviews on the page or in structured data.[1][2]

Google’s examples include:

  • reviews not based on a genuine experience;
  • reviews written in exchange for money, discounts, vouchers, free products, or another benefit when the incentive is not clearly and prominently disclosed.

If your site uses:

Review
AggregateRating
Product ratings
Course ratings
LocalBusiness review widgets

audit the source of the reviews, not just the JSON-LD syntax.

Why this keyword is hot.

This is one of Google Search Central’s newest documentation changes.

The update landed July 24, less than two weeks before this audit.[2]

Review manipulation is also receiving broader regulatory attention, so search teams and legal teams increasingly care about the same underlying evidence:

Is the review real, independent, and represented accurately?

Structured data does not make a review legitimate.

Valid JSON-LD can describe false information perfectly.

Example:

{
  "@type": "AggregateRating",
  "ratingValue": "4.9",
  "reviewCount": "843"
}

The syntax can validate.

That does not prove:

  • 843 people reviewed the product;
  • the reviewers used it;
  • incentives were disclosed;
  • the average is calculated correctly;
  • the ratings are visible on the page.

Google’s structured data rules require the markup to reflect visible page content.[1]

Sources reviewed.

  1. Review snippet structured data — Google Search Central; accessed 2026-08-06. [1]
  2. Latest Google Search documentation updates — Google Search Central; accessed 2026-08-06. [2]

02

Methodology

Reviews must be visible.

Google says review content being marked up must be readily available to users on the page.[1]

If you mark up an individual review:

  • show the review;
  • show the rating;
  • show the reviewer information supported by the page.

If you mark up an aggregate rating:

  • show the aggregate rating visibly.

Do not hide the evidence in JSON-LD.

Do not aggregate reviews from other websites.

Google’s review snippet guidance says not to aggregate reviews or ratings from other websites.[1]

Common risky pattern:

Google rating + Facebook rating + Yelp rating
→ combined 4.8 average
→ AggregateRating on your own page

That is not supported by Google’s guideline.

Use third-party ratings as attributed information for users when allowed.

Do not manufacture your own search markup from someone else’s rating database.

Self-serving local business reviews.

This remains one of the most misunderstood rules.

If the organization being reviewed controls the reviews about itself, pages using LocalBusiness or another Organization type are ineligible for the star review feature, including when the reviews are embedded through a third-party widget.[1]

Example:

plumber.com
→ embeds Google reviews about plumber.com
→ marks its own LocalBusiness with AggregateRating

The reviews may be real.

The rich-result eligibility issue remains because the reviewed entity controls the page.

Product reviews are different.

A merchant can mark up eligible product review information when the page and markup meet product/review policies.

The reviewed entity and schema type matter.

Do not generalize the local-business self-serving rule into:

Nobody can mark up reviews on their own site.

That is false.

Audit the specific supported type.

03

Result

Incentives require disclosure.

A review can be based on a genuine experience and still be incentivized.

Example:

Leave an honest review and receive a $10 coupon.

The review is not automatically fake.

Google’s new guideline focuses on undisclosed incentivization.

Make the relationship clear and prominent.

Do not hide it:

  • in terms;
  • in a tooltip;
  • behind a link;
  • at the bottom of the page.

The reader should understand the incentive when reading the review.

Affiliate review content.

A publisher reviewing software through an affiliate relationship should disclose that commercial relationship.

That disclosure is separate from whether the writer actually tested the software.

A strong review can explain:

  • access method;
  • test period;
  • affiliate compensation;
  • scoring method;
  • evidence;
  • version.

Transparency does not weaken a useful review.

It makes the commercial context legible.

Review collection audit.

Create a review ledger.

Fields:

REVIEW_ID
ITEM
REVIEWER
DATE
EXPERIENCE_VERIFIED
INCENTIVE
DISCLOSURE
RATING
VISIBLE_URL
MARKED_UP
SOURCE

Sample reviews monthly.

Verify:

  • person exists;
  • transaction or experience evidence;
  • incentive disclosure;
  • rating in page HTML;
  • aggregate math;
  • review count.

Aggregate math.

Do not hard-code:

4.9

for six months.

Calculate from the same eligible reviews displayed or represented under your policy.

If reviews are removed:

  • update count;
  • update average;
  • update visible text;
  • update markup.

A stale rating is still inaccurate.

Rich results are not guaranteed.

Valid markup creates eligibility.

It does not guarantee Google will show stars.

Google can choose whether to display a rich result.

Do not sell:

We added schema, so your star rating will appear.

Sell:

We implemented valid eligible markup and verified the page against current guidelines.

2026 audit checklist.

  • Reviews are based on genuine experience.
  • Incentives are disclosed prominently.
  • Marked-up reviews are visible.
  • Aggregate rating is visible.
  • Review count is accurate.
  • Rating calculation is reproducible.
  • Third-party ratings are not improperly aggregated.
  • LocalBusiness self-serving stars are not expected.
  • Schema type is supported.
  • Rich Results Test passes.
  • Review source is preserved.
  • Changes are logged.

04

Limitations

FAQ.

Did Google ban incentivized reviews?

Google’s new guideline says not to include fake or undisclosed incentivized reviews. A disclosed incentive still needs to comply with other applicable policies and laws.

Can I mark up Google Business Profile reviews on my own local business site?

Google says a local business or organization controlling reviews about itself is ineligible for the star review feature, including embedded third-party review widgets.

Can I combine Google and Facebook star ratings?

Google’s review snippet guidance says not to aggregate reviews or ratings from other websites.

Does valid schema guarantee stars?

No. Structured data makes a page eligible; display is not guaranteed.

Should the review be visible?

Yes. Google says marked-up review content should be readily available to users.

Verdict.

The July 2026 update did not create review integrity.

It made the expectation harder to pretend you missed.

If your structured data says users love a product, preserve the evidence that actual users produced the rating.

This data note reflects the cited documentation and sample periods available through 2026-08-06. Product interfaces, eligibility, sampling, aggregation, ad delivery, and Search behavior can change. Observed percentages from a commercial-query sample do not describe all Google searches, and valid structured data never guarantees a rich result.

Verification record.

  • July 24, 2026 documentation update was checked on 2026-08-06.
  • Visibility, third-party aggregation, and self-serving local-business rules were checked against current review snippet documentation.
  • No rich-result guarantee is claimed.

Duplication and search-intent record.

No prior package targets the exact July 2026 review snippet update with incentive disclosure, aggregate math, self-serving review rules, and an implementation ledger.

References

Sources behind this record

  1. Review snippet structured data — Google Search Central (accessed August 6, 2026)
  2. Latest Google Search documentation updates — Google Search Central (accessed August 6, 2026)

Corrections

Correction history

No corrections recorded.

To report an error, use the public corrections path.

Claim limit

Reviewed against cited sources available through 2026-08-06.

Search features, documentation, policies, interfaces, sampling, and enforcement can change after publication.

Eligibility, compliance, or correct implementation does not guarantee rankings, traffic, citations, or rich results.