Google's 24 July 2026 review rule: a 6-step audit before your stars disappear
Summary. On 24 July 2026 Google added one sentence to its review snippet structured data guidelines: "Don't include fake or undisclosed incentivized reviews on your page or in your structured data markup." The page itself now carries a last-updated stamp of 2026-07-24 UTC. That sentence sits inside the Guidelines section, which opens with a warning that a site violating one or more of these guidelines may receive a manual action. Google gave two examples of what it means: reviews not based on a genuine experience of a product or service, and reviews written in exchange for a benefit such as money, discounts, vouchers or free products where the incentivization is not clearly and prominently disclosed. This is not new law. The US Federal Trade Commission's Rule on the Use of Consumer Reviews and Testimonials has been in effect since 21 October 2024, and its own example of a non-compliant offer is a business saying "Tell us how much you loved your visit to John's Steakhouse and get a $5 coupon". In India the Bureau of Indian Standards published IS 19000:2022 for online consumer reviews and it remains voluntary, while the Central Consumer Protection Authority can fine a manufacturer or endorser up to Rs 10 lakh for a misleading advertisement, rising to Rs 50 lakh for a repeat offence. What changed on 24 July is that a review programme most brands considered a marketing question is now an eligibility question for star ratings in Google Search. This is the audit.
What Google actually wrote, and where it sits
The wording matters, so here it is exactly as published in the technical guidelines for review snippets:
"Don't include fake or undisclosed incentivized reviews on your page or in your structured data markup. Examples include:
- Reviews that aren't based on a genuine experience of a product or service
- Reviews written in exchange for a benefit (such as money, discounts, vouchers, or free products) that don't clearly and prominently disclose the incentivization"
Two words in that text do the work. The first is "undisclosed", which means an incentivized review is not automatically disqualifying; an incentivized review without a clear disclosure is. The second is "or", in "on your page or in your structured data markup", which closes the obvious workaround of leaving an undisclosed incentivized review visible on the page while quietly excluding it from the JSON-LD, or the reverse.
Barry Schwartz, Contributing Editor at Search Engine Land, read the timing the way most practitioners did: "Google added a new guideline to the documentation for a reason; Google probably sees people using these techniques to get fake reviews."
Placement is the part teams miss. This is not in the spam policies and it is not in a blog post. It is in the Guidelines block of the review snippet reference, directly under a warning that reads: "If your site violates one or more of these guidelines, then Google may take manual action against it. Once you have remedied the problem, you can submit your site for reconsideration." Guidelines in that block govern eligibility for the rich result. The practical exposure is losing stars in search results, and a manual action that has to be cleared through reconsideration.
Google published no separate announcement alongside the change, which is why plenty of teams running review campaigns still have not seen it.
Why this lands harder in 2026 than it would have in 2023
Two things happened before this guideline that change its weight.
Google removed the FAQ rich result. A deprecation notice went on the documentation on 8 May 2026, the feature stopped appearing in search from 7 May 2026, and the documentation itself was removed on 15 June 2026. Star ratings are now one of the few remaining visual differentiators an ordinary commercial page can earn in a results layout increasingly dominated by AI Overviews.
Review data is also flowing into AI answers. Search Engine Land reported on 24 July 2026 that ChatGPT gained access to Yelp reviews, ratings and photos. Rating data is no longer only a snippet decoration; it is an input to systems that summarise a purchase decision on your behalf.
So the asset getting more valuable is the same asset now governed by a stricter eligibility test. That is the whole reason to spend a day on this audit rather than a quarter.
Step 1: Inventory every system that feeds a rating into your markup
Most brands cannot answer this in one sitting, which is the first finding.
Write down every source that contributes a rating or a review to any page carrying Review or AggregateRating markup. In a typical D2C stack that list runs longer than expected: the on-site review widget, post-purchase email review requests, an SMS review flow, a loyalty programme that awards points for reviews, a sampling or seeding programme, an affiliate or creator programme, imported reviews from a marketplace listing, and reviews syndicated from a parent brand or a group site.
For each source, record four things: does it offer anything in return for the review, does the offer depend in any way on the review being positive, is any disclosure attached to the resulting review, and does the review flow into the structured data.
Two of Google's older guidelines usually claim their first victims here. "Don't aggregate reviews or ratings from other websites" rules out pulling in marketplace ratings, and "Provide review information about a specific item, not about a category or a list of items" rules out a category page carrying a rating rolled up from its children.
| Review source | Typical Google guideline risk | What to do first |
|---|---|---|
| Post-purchase email with no incentive | Low | Confirm reviewer names are valid and under 100 characters |
| Points, coupon or discount for any review | Undisclosed incentivization if no visible label | Add an unavoidable disclosure to each affected review |
| Free product seeding or sampling | Undisclosed incentivization; often no disclosure at all | Disclose, and check the offer wording for implied sentiment |
| Ratings imported from a marketplace listing | "Don't aggregate reviews or ratings from other websites" | Remove from markup; keep on page only if clearly attributed |
| Embedded third-party widget on your own Organization page | Self-serving reviews; ineligible for the star feature | Remove the Organization-level markup |
| Category or collection page rating | Rating must describe a specific item | Move markup to the individual product pages |
Step 2: Classify every review, then count what you lose
Sort each review into one of five buckets: organic, incentivized with an adequate disclosure, incentivized without an adequate disclosure, insider, or fake.
The fifth bucket is the one to be honest about. Google's first example is "Reviews that aren't based on a genuine experience of a product or service". If a review came from a purchased pack, a review-exchange group, or an agency that could not name the reviewer, it belongs there and it comes out of both the page and the markup.
Then do the arithmetic before you do the remediation. Take your current ratingValue and ratingCount, remove the fake bucket entirely, and recompute. Do the same again excluding the undisclosed incentivized bucket, so you can see the gap between the rating you display today and the rating your genuinely organic reviews support. If those two numbers are far apart, the star rating was never the asset you thought it was, and the drop you are worried about has already been priced into your conversion data as returns and complaints.
One judgement, stated plainly: a 4.9 built on a seeding programme is a liability with a countdown on it, and the cheapest day to fix it is the day before Google notices.
Step 3: Make the disclosure unavoidable, not merely present
Google's wording is "clearly and prominently disclose". The FTC has published a workable operational definition of a very similar standard, and it is the most useful thing in this whole area.
Under the FTC rule, a disclosure has to be "clear and conspicuous", and its definition of that term requires the disclosure to be "unavoidable". The FTC explains that a disclosure is avoidable when "a consumer must take any action, such as clicking on a hyperlink or hovering over an icon, to see" it. Asked directly whether a disclosure in the first line of a consumer review is unavoidable, the FTC's answer is that the Commission would consider such a disclosure to be unavoidable.
That gives you a concrete implementation target. The disclosure belongs in the visible review body, at the start, on the page, in the same text that goes into your markup. Not in a footer. Not in a tooltip. Not in the terms of the loyalty programme.
Here is what that looks like in the markup, using only properties Google lists as required or recommended for Review:
{
"@context": "https://schema.org/",
"@type": "Product",
"name": "Example product name",
"review": [{
"@type": "Review",
"reviewRating": {
"@type": "Rating",
"ratingValue": 4,
"bestRating": 5,
"worstRating": 1
},
"author": {
"@type": "Person",
"name": "Priya S."
},
"datePublished": "2026-07-28",
"reviewBody": "Received a free sample in exchange for this review. Fit is true to size and the fabric held up after four washes."
}]
}
The disclosure is the first sentence of reviewBody, so it survives both the on-page render and the markup, and a reader meets it before the opinion. Note also that bestRating and worstRating are only recommended: Google assumes 5 and 1 respectively when they are omitted, so include them only when your scale actually differs.
Watch the author field. Google requires author for a Review, states that the reviewer's name must be a valid name, gives "50% off until Saturday" as an example of an invalid one, and specifies that the field must be shorter than 100 characters or the page is not eligible for an author-based review snippet.
Step 4: Recompute the aggregate honestly
A disclosure fixes the individual review. It does not fix the number in the star widget.
The FTC makes this point about insider reviews and the logic transfers directly to incentivized ones: insider reviews are permitted when the relationship is clearly and conspicuously disclosed, but "if these reviews materially increase the average star rating of a product, the business could be violating the FTC Act even with such disclosures, because consumers might see only the star rating and not look at the individual reviews."
That is the trap. A page can be fully compliant review by review and still misrepresent itself through the single number most people actually read.
Practical position: if disclosed incentivized reviews move your average by a material margin, either exclude them from the aggregate you mark up, or show both numbers on the page. Google requires ratingValue plus at least one of ratingCount or reviewCount on AggregateRating, and it defines reviewCount as the number of people who provided a review with or without an accompanying rating, so the vocabulary to be precise already exists.
| Failure mode | What the reader sees | Google exposure | FTC exposure |
|---|---|---|---|
| Fake reviews in markup | Inflated stars | Guideline breach; manual action risk | Rule violation; civil penalties for knowing violations |
| Incentivized, no disclosure | Inflated stars | Guideline breach; manual action risk | FTC Act exposure for failure to disclose |
| Incentivized for positive sentiment only | Inflated stars | Guideline breach | Section 465.4 violation even with a disclosure |
| Disclosed incentives, aggregate not adjusted | Inflated average | Compliant on the letter of the guideline | Possible FTC Act exposure via the star rating |
| Marketplace ratings imported into markup | Borrowed credibility | "Don't aggregate reviews or ratings from other websites" | Depends on presentation |
| Organization reviews you control | Stars on your own brand page | Ineligible for the star review feature | Depends on presentation |
Step 5: Clear the self-serving and aggregation traps while you are in there
Two older guidelines cause more lost stars than the new one will, and this audit is the moment to close them.
The self-serving rule is specific and it is stricter than most teams assume. Google's guideline states that if the entity being reviewed controls the reviews about itself, its pages using LocalBusiness or any other type of Organization structured data are ineligible for the star review feature. Google spells out that this covers an embedded third-party widget, naming a Google Business reviews or Facebook reviews widget as examples. A "what our customers say" section on your homepage, marked up at the Organization level, is the single most common instance of this.
Read the scope carefully before you strip anything. That ineligibility clause is written against LocalBusiness and Organization types. Reviews of your own products, marked up on the product page as Product with nested Review or AggregateRating, are a different case and are not covered by that clause. The rule about not aggregating ratings from other websites and the new rule about fake or undisclosed incentivized reviews do apply everywhere.
For local business ratings Google adds two further requirements: ratings must be sourced directly from users, and you should not rely on human editors to create, curate or compile ratings information for local businesses.
Also check the visibility requirement, which is easy to fail after a redesign. Google requires that marked-up review content be readily available to users from the marked-up page, and that it be immediately obvious that the page has review content. If your reviews load behind a tab, an accordion or a lazy-loaded widget that never fires for a crawler, the markup is describing content the page does not clearly show.
Step 6: Validate, then watch the right report
Run the Rich Results Test and the Search Console rich result reports for review snippets. Both catch syntax problems and missing required properties. Neither can tell you whether a review was written in exchange for a free sample, which is why steps 1 to 4 have to be done by a human with access to the marketing calendar.
Set two monitoring habits. First, watch the review snippet report in Search Console for a drop in valid items, which is what a markup regression looks like. Second, watch the Manual Actions report, which is where a guideline breach surfaces. If a manual action appears, the remedy path is the one named in the documentation: fix the problem, then submit the site for reconsideration.
Give it time before you conclude anything. Google's own note on the page is that it may take several days after publishing for Google to find and crawl a page, and re-crawling and re-indexing take longer still.
The same structured-data discipline pays off beyond stars, which is why we treat structured data and JSON-LD for AI search citations as part of the same workstream rather than a separate one, and why the wider SEO guide for 2026 puts markup accuracy alongside content quality rather than after it.
What the FTC rule adds that Google's guideline does not
If you sell into the United States, Google's guideline is the smaller of your two problems.
The FTC's Rule on the Use of Consumer Reviews and Testimonials took effect on 21 October 2024. On incentives, Section 465.4 draws a line that Google's one-sentence guideline does not: "The rule does not prohibit giving incentives for reviews, as long as there isn't an express or implied requirement that the reviews have to express a particular sentiment. But remember that failing to disclose incentives could be a violation of the FTC Act."
The sentiment condition is where marketing copy quietly breaks the rule. The FTC's worked example is that you would be implying reviews have to be positive if you wrote "Tell us how much you loved your visit to John's Steakhouse and get a $5 coupon" or "Tell your friends about all the fun you had at Jane's Arcade for a chance to win prizes." Neither sentence contains an explicit condition. Both imply one.
And a disclosure does not rescue a sentiment-conditioned incentive. Asked whether a business can pay incentives for 5-star reviews on third-party platforms so long as reviewers add a disclosure, the FTC's answer is: "No. That conduct would violate Section 465.4. Note also that this section applies whether the reviews appear on your website or third-party review platforms."
Three further points are worth knowing before anyone on your team improvises.
The rule authorises courts to impose civil penalties for knowing violations. The FTC's guidance page states the standard in those terms and does not publish a per-violation figure, so treat any specific number you see quoted as something to verify against the current civil penalty adjustment rather than as settled fact.
There is no private right of action under the rule, so the enforcement risk is regulatory rather than a class action under this rule specifically.
Sorting is mostly safe, suppression is not. The FTC says organizing reviews is not suppressing reviews under the rule, and that ordering reviews by rating with five-star reviews on top is not covered by the rule, but adds that organizing reviews in a way that makes it difficult for consumers to find negative reviews could be an unfair or deceptive act under Section 5 of the FTC Act.
Finally, note that the FTC's guidance is staff guidance and says so directly: it "isn't definitive or comprehensive, and it doesn't provide a safe harbor from potential liability."
India-specific considerations
Indian D2C brands and marketplaces sit under a different mix: a voluntary technical standard plus a live enforcement power aimed at advertising.
The Bureau of Indian Standards published IS 19000:2022, "Online Consumer Reviews: Principles and Requirements for their Collection, Moderation and Publication", covering how review administrators collect, moderate and publish online consumer reviews. It applies to anyone publishing consumer reviews online, including sellers collecting reviews from their own customers, a third party contracted by the seller, and independent third parties. Compliance is voluntary.
The enforcement teeth are elsewhere. Under the Consumer Protection Act 2019, the Central Consumer Protection Authority can impose a penalty of up to Rs 10 lakh on a manufacturer or endorser for a false or misleading advertisement, with imprisonment of up to two years; for a subsequent offence the fine may extend to Rs 50 lakh and imprisonment to five years. The CCPA can also bar an endorser from endorsing that product or service for up to one year, extending to three years for repeat offences.
Three practical consequences for an Indian brand.
A seeding or sampling programme run through creators is advertising as well as review generation, and the endorser-side penalty means your creators carry exposure alongside you. Disclosure protects the creator as well as the brand.
Marketplace ratings and own-site ratings need to stay separate in your markup. Google's prohibition on aggregating ratings from other websites means your product page cannot borrow the marketplace's star average, however tempting the volume difference.
If your review programme touches personal data across borders, the review vendor is a processor in your data map like any other. Teams working through that mapping will find the relevant obligations in our DPDP Act engineering playbook for Indian startups, and brands selling through open network channels should read it alongside the ONDC playbook for D2C brands and sellers.
The audit in one page
| Check | Pass condition | Where it is defined |
|---|---|---|
| Fake reviews removed | No review in page or markup lacking a genuine experience | Google review snippet guidelines, 24 July 2026 |
| Incentives disclosed | Disclosure visible in the review body, not behind a click | Google guideline; FTC "unavoidable" standard |
| No sentiment condition | Offer wording never implies the review must be positive | FTC Section 465.4 |
| Aggregate not inflated | Disclosed incentivized reviews do not materially move the average | FTC Act risk on star ratings |
| No imported ratings | No marketplace or third-party ratings inside your markup | Google: don't aggregate ratings from other websites |
| No self-serving Organization stars | No Review or AggregateRating on LocalBusiness or Organization you control | Google self-serving reviews guideline |
| Reviews visible on page | Review text and rating immediately obvious to a user | Google technical guidelines |
| Required properties present | author, itemReviewed or nesting, reviewRating, ratingValue | Google review snippet reference |
If a row fails, fix the page and the markup together. Fixing only one is how sites end up with markup that no longer matches the page, which is a separate guideline breach.
FAQ
What exactly did Google change on 24 July 2026?
Google added one guideline to its review snippet structured data documentation: do not include fake or undisclosed incentivized reviews on your page or in your structured data markup. It gave two examples, covering reviews not based on genuine experience and reviews written in exchange for a benefit without clear and prominent disclosure of the incentivization.
Are incentivized reviews now banned outright?
No. The guideline targets fake reviews and undisclosed incentivized reviews. An incentivized review with a clear and prominent disclosure is not prohibited by this guideline. Separately, the US FTC rule prohibits conditioning an incentive on the review expressing a particular sentiment, and a disclosure does not cure that specific problem.
What happens if my site breaks this guideline?
The guidelines section of Google's review snippet documentation warns that Google may take manual action against a site violating one or more of these guidelines. The practical outcome is losing eligibility for review rich results. After remedying the problem, you can submit the site for reconsideration through Search Console.
Where should the disclosure appear?
In the visible review text and in the markup, at the start of the review body. The FTC treats a disclosure as avoidable when a consumer must click a hyperlink or hover over an icon to see it, and considers a disclosure in the first line of a consumer review to be unavoidable. Footers and programme terms do not qualify.
Can I still show star ratings on my own homepage?
Usually not at the Organization level. Google says that if the reviewed entity controls the reviews about itself, its pages using LocalBusiness or any other Organization structured data are ineligible for the star review feature, including reviews delivered through an embedded third-party widget. Product-level reviews on product pages are a separate case.
Can I import my marketplace ratings into my product pages?
No. Google's long-standing technical guideline says not to aggregate reviews or ratings from other websites. Your product page markup should describe reviews collected on that page for that specific item. You may still reference a marketplace rating as visible content, provided it is clearly attributed and not marked up as your own.
How do I decide whether to exclude incentivized reviews from my average?
Recompute your rating value and count with and without the incentivized set. If the difference is material, either exclude them from the aggregate you mark up or publish both numbers. The FTC's reasoning is that consumers may see only the star rating and never read the individual reviews or their disclosures.
What applies to Indian brands specifically?
The Bureau of Indian Standards published IS 19000:2022 on collecting, moderating and publishing online consumer reviews, and compliance is voluntary. Enforcement risk comes from the Consumer Protection Act 2019, under which the Central Consumer Protection Authority can penalise a manufacturer or endorser up to Rs 10 lakh, rising to Rs 50 lakh for repeat offences.
How eCorpIT can help
eCorpIT is a Gurugram-based technology consultancy, ISO 27001:2022 certified and assessed at CMMI Level 5, with senior engineering teams working across commerce platforms, structured data and search visibility. We audit review pipelines end to end, from the incentive wording in a post-purchase email through to the JSON-LD a crawler actually receives, and we design implementations aligned with Consumer Protection Act and Digital Personal Data Protection Act requirements. If your stars matter to your conversion rate and you are not certain what is feeding them, talk to us at /contact-us/.
References
- Review snippet (Review, AggregateRating) structured data - Google Search Central, last updated 24 July 2026
- Latest documentation updates - Google Search Central changelog, July 2026
- Google says don't include fake or undisclosed incentivized reviews in review snippet structured data - Barry Schwartz, Search Engine Land, 24 July 2026
- The Consumer Reviews and Testimonials Rule: Questions and Answers - US Federal Trade Commission
- Trade Regulation Rule on the Use of Consumer Reviews and Testimonials - Federal Register, 22 August 2024
- Federal Trade Commission Announces Final Rule Banning Fake Reviews and Testimonials - US Federal Trade Commission, August 2024
- FTC Endorsement Guides, 16 CFR Part 255 - Electronic Code of Federal Regulations
- Making review rich results more helpful - Google Search Central Blog, September 2019
- BIS issues standards for organizations publishing consumer reviews - Press Information Bureau, Government of India
- Summary: India's new guidelines for reviews on online platforms - MediaNama, December 2022
- IS 19000:2022 Online Consumer Reviews: Principles and Requirements for their Collection, Moderation and Publication - Bureau of Indian Standards
- The Consumer Protection Bill, 2019 - PRS Legislative Research
- ChatGPT gains access to Yelp reviews, ratings, and photos - Search Engine Land, 24 July 2026
Last updated: 5 August 2026.
Top comments (0)