A manual action against review-snippet structured data doesn’t touch rankings. Google ignores the markup and leaves the page in Search results, so the visible symptom isn’t a ranking drop: it’s the star rating vanishing from the search result. On July 24, Google named the trigger in a new guideline covering fake and undisclosed incentivized reviews.
What Google’s documentation actually added
The change sits inside Google’s review-snippet structured data guidelines, not in a blog post. The new line reads: “Don’t include fake or undisclosed incentivized reviews on your page or in your structured data markup.” Two examples follow, quoted directly from that documentation: “Reviews that aren’t 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) that don’t clearly and prominently disclose the incentivization.”
Google’s own changelog, dated July 24, describes the motive in one line: “To improve user review transparency.” The documentation restates the existing consequence for any guideline violation: Google “may take manual action against it,” and once the problem is fixed, the site owner “can submit your site for reconsideration.”
Incentivized reviews are not banned; undisclosed ones are
This guideline doesn’t prohibit the incentive itself: money, discounts, vouchers, or free products. It prohibits leaving that incentive undisclosed. Google names no format for the disclosure. It gives no placement rule, no required wording, no proximity requirement between the disclosure and the review itself. That absence is the whole story: an incentivized-review program can comply, and Google has defined no threshold for what clearing the bar looks like. Search Engine Journal’s headline leads with the manual-action warning, which is one half of the story: the other half is what still qualifies as compliant.
What does Google’s new review-snippet guideline change?
What changed: a July 24 update to Google’s review-snippet documentation bans fake reviews and undisclosed incentivized reviews from your page and your structured data markup, and who’s affected is any site marking up ratings for products, software, courses, recipes, events, movies, or books. On violation, Google may take a structured-data manual action: the troubleshooting section says the page’s structured data “will be ignored (although the page can still appear in Google Search results).” How to comply: disclose any review incentive clearly and prominently, since Google sets no rule for how.
The blind spot: third-party review widgets
This reading is ours, not Google’s. Review markup on a commercial site often isn’t hand-typed by the merchant: a review-collection widget generates it, sometimes from a post-purchase incentive flow the merchant installed once and never re-read line by line. If that generated markup fails to disclose the incentive clearly and prominently, the manual action would still land on the merchant’s domain. Google’s guideline draws no line between code a site owner wrote and code a vendor’s script wrote on their behalf. You are liable for JSON-LD you did not write, and you are the one who has to file the reconsideration request to get it back.
The scope reaches well past e-commerce
Star ratings aren’t an e-commerce feature bolted onto product pages. Google’s structured-data documentation lets sites supply ratings for:
- Book
- Course list
- Event
- Local business (only for sites that capture reviews about other local businesses)
- Movie
- Product
- Recipe
- Software App
Google also supports reviews for CreativeWorkSeason, CreativeWorkSeries, Episode, Game, MediaObject, MusicPlaylist, MusicRecording, and Organization (only for sites that capture reviews about other organizations) schema.org types and their subtypes. A SaaS review directory running Software App markup, a course platform running Course list markup, and a local-service listing site running Local business markup sit under the identical rule as a Shopify storefront. The documentation never said retail-only.
Read your own markup before the trade headline forces you to
The page-keeps-ranking, markup-gets-ignored mechanism isn’t new to this guideline. The July 24 change follows Google’s spam-policy expansion covering AI answers, and arrives a month after June’s spam update. Nothing here reports an actual manual action issued yet, and nothing sets a deadline. What exists is a documentation change that quietly rewrites who owns disclosure, and a failure mode that will read, on a rankings dashboard, like nothing happened at all.
