Google Review Snippets: Free Products and Paid Reviews Need Prominent Disclosure
Audit real reviewer experience, benefits, prominent disclosures, visible-page parity, and aggregate-rating math before marking reviews up for Google.
Updated August 16, 2026: Google’s review-snippet guideline says not to mark up fake reviews or undisclosed incentivized reviews. A genuine reviewer who received money, a discount, a voucher, a free product or another benefit needs a clear and prominent disclosure. Burying the relationship in a general policy page does not give the reader the same context as a disclosure beside the review.
The rule is about eligibility and truthful presentation. It does not mean every disclosed review earns stars, and it does not turn an incentivized endorsement into an independent review.
Classify the review before markup
| Case | Page treatment | Markup decision |
|---|---|---|
| No genuine experience | Reject or clearly present as non-review material | Do not include as Review |
| Genuine, no material benefit | Show author, item, rating and review | May be eligible if all rules are met |
| Genuine, benefit prominently disclosed | Place plain-language disclosure beside the review | May be eligible; display is not guaranteed |
| Genuine, benefit hidden or vague | Repair disclosure before release | Exclude until repaired |
“Gifted,” “partner” or a symbol can be too ambiguous if readers cannot understand what the reviewer received. Prefer plain language such as “The reviewer received this product for free” or “The reviewer was paid for this review.”
Build a review-provenance ledger
Keep one record per review with the submission ID, reviewer, reviewed item or variant, evidence of experience, date, rating scale, benefit type and value where known, exact disclosure text, disclosure location, moderation decision and aggregate inclusion state.
Recalculate AggregateRating from the same visible, eligible set. Removing one undisclosed review without updating the count and average creates a new mismatch. Do not aggregate reviews copied from other websites, and do not assume a third-party widget makes self-serving LocalBusiness or Organization reviews eligible.
Run the visible-page parity test
- Open the rendered page as a reader and locate the reviewed item, review text, author, date, rating and incentive disclosure.
- Inspect the JSON-LD or microdata and compare those values exactly.
- Reproduce the aggregate count and rating from the eligible visible set.
- Test a normal review, a disclosed incentive, a rejected review and a changed aggregate.
- Validate syntax, then inspect the page again after caching, localization and consent layers load.
The schema decision guide explains the difference between valid vocabulary, feature eligibility and ranking. The commercial disclosure policy records Search Engine Answer’s own separation rule.
Release checklist
- Every marked review traces to a real submission and specific reviewed item.
- Every benefit is recorded and disclosed in plain language beside the affected review.
- Visible content and structured data agree.
- Aggregate math excludes rejected or undisclosed reviews.
- Imported third-party ratings and self-serving business reviews are not treated as automatically eligible.
- An owner and re-audit trigger are assigned.
Limit: Google’s documentation defines Search feature eligibility. Consumer-protection laws vary by jurisdiction and may impose additional duties. This article is editorial guidance, not legal advice.
Ask a question or join the discussion