Skip to content
search-engine-optimizedby Netsolution

The engine has spelled out what a forbidden incentivised review is

Current recordDocument dated , published by Google Search Central, read on

The review snippet documentation forbids fake reviews and undisclosed incentivised reviews. It gives two examples and announces a possible manual action. The line therefore does not separate the paid review from the spontaneous one, but the declared inducement from the concealed one.

What the document says

The documentation page devoted to review snippets received, on 24 July 2026, an additional instruction. It names two practices and forbids them.

The documentation forbids including fake or undisclosed incentivised reviews, on the page as in the markup, and gives two examples: a review not based on a genuine experience of the product or service, and a review written in exchange for a benefit without that inducement being clearly and prominently disclosed.

officialSource : Google Search Central, “Review snippet (Review, AggregateRating) structured data”

The text is short and unambiguous:

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

Two examples follow, and it is they that carry the useful detail:

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

The second deserves rereading slowly, because it does not say what most summaries will make it say.

The line is not where people think

The boundary this document draws does not separate the paid review from the spontaneous one: it separates the disclosed inducement from the concealed one, which is the same line applied to commercial links.

hypothesis

A review obtained in exchange for a discount, a voucher or a free product is not forbidden as such. What is named is the absence of a clear and prominent disclosure of that inducement. The fault identified is the concealment.

That distinction is not a legal detail: it completely changes what a site has to fix. A shopkeeper offering a sample in exchange for a review does not have to stop the practice — they have to write it down, next to the review, in a form a reader sees without looking for it.

It is exactly the line applied to commercial links, and this site has described it that way since its first guides: the real boundary does not run between paid and free, but between declared and hidden. Seeing it appear identically on another subject, in another document, is the kind of convergence worth recording.

The rule almost nobody applies

Where the entity being reviewed controls the reviews about itself, its pages using business or organisation structured data are ineligible for the star display.

officialSource : Google Search Central, “Review snippet (Review, AggregateRating) structured data”

Here is the sentence:

If the entity that’s being reviewed controls the reviews about itself, their pages that use LocalBusiness or any other type of Organization structured data are ineligible for star review feature.

Its reach is considerable and widely ignored. A site that collects reviews about itself, stores them itself and displays them itself is not eligible for stars in the results, however clean its markup. The customer testimonial published on a home page, conscientiously marked up, will not produce the hoped-for display — not through a technical fault, but by rule.

Many services sold on the promise “we add the stars in Google” run into that sentence. The markup is done, it is valid, the testing tool confirms it, and the display never arrives. Validating markup says it is well formed; it says nothing about eligibility.

What the document does not say

It sets no form for the disclosure. “Clearly and prominently” is not a specification: no size, no placement, no wording is imposed. A site looking for minimal compliance therefore has no threshold to aim at, and that is probably deliberate — a numbered threshold would be worked around the day it was published.

Nor does it say how detection happens, or at what scale. Nothing indicates that an automatic system spots incentivised reviews; what is announced, on the other hand, is a penalty of another nature.

Failing to follow these guidelines may lead to a manual action against the site, and the site can request a review once the problem is fixed.

officialSource : Google Search Central, “Review snippet (Review, AggregateRating) structured data”

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.

Manual action: the decision has a human author, a named reason, a notification in the engine’s console, and a way out. It is not a silent ranking adjustment, and that difference matters for anyone who has to explain a drop to their management — in one case you read the reason; in the other you speculate.

What this changes about what you were doing

Three checks, in this order.

Are your reviews genuine? A review written by the business, copied from elsewhere, or obtained without the person having used the product falls under the first prohibition. No markup repairs that, and removing it repairs it no better: the document targets reviews on the page as much as in the markup.

Are your inducements written down? If a review was obtained in exchange for a benefit, the notice has to be there, legible, next to the review. Not in the terms and conditions, not in a footer.

Are you expecting stars you are not entitled to? If you collect and control your own reviews, the answer is no, and no technical fix will change it. The useful work is then to have the reviews collected elsewhere, or to stop expecting the display.

What does not work

Add review markup to your customer testimonials and your stars will appear in Google within days.

The documentation explicitly rules out the star display for pages where the entity being reviewed controls the reviews about itself. Testimonials collected and published by the business itself fall under that case: the markup will be valid, the testing tool will confirm it, and the display will not arrive. The promise confuses markup validity with display eligibility, which are two distinct things documented separately.

What would have to be measured to settle the rest

The document closes the question of what is forbidden. It leaves entirely open the question of what is actually detected, and how often a manual action is really issued on those grounds.

An honest record would mean tracking comparable sites, some of which display plainly incentivised reviews with no notice, and observing over several months which ones lose their star display. This site has run no observation of that kind and will publish none without a replayable protocol. In the meantime, the only thing established is the rule — which is amply enough to decide what to fix.

Sources

  1. Review snippet (Review, AggregateRating) structured data — Google Search Centralaccessed on
  2. Latest Google Search Documentation Updates — Google Search Centralaccessed on

Block revalidated on

Check it yourself

Observe whether your page meets the conditions for a star display, or whether it is ruled out by the rule on reviews controlled by the entity being reviewed.

  1. Open a page on your site that displays reviews and look, in its markup, for the structured data type carrying the rating.
  2. Ask yourself who collected those reviews: you, or a platform independent of you?
  3. If a review was obtained in exchange for any benefit, look on the page for the notice saying so, and judge whether it is visible without effort.
  4. Finally, compare your page with what the engine actually displays for it in its results, several days after any fix.

What you should observe: A page whose reviews are collected and controlled by the entity being reviewed is not eligible for stars, whatever the quality of its markup. An inducement with no visible notice falls under the prohibition quoted above, whether the markup is present or not.

Frequently asked questions

Is a review obtained in exchange for a discount forbidden?
Not in itself. What the document forbids is a review obtained in exchange for a benefit without that inducement being clearly and prominently disclosed. The fault named is the concealment, not the inducement, and the nuance completely changes what has to be fixed.
Can I display stars from my own reviews?
No, for the rich display. The document rules out star eligibility where the entity being reviewed controls the reviews about itself. You can display them for your visitors, which stays useful; you cannot expect stars in the engine's results from them.
What does a site risk by not following these guidelines?
The document announces a possible manual action, issued by a human reviewer, and provides for a review request once the problem is fixed. It is not an automatic ranking adjustment: it is a reasoned decision, notified in the engine's console.
Should the markup be removed to become compliant?
Removing the markup does not fix a fake review: the document forbids those reviews on the page as much as in the markup. Removing the markup only removes the rich display, and therefore the benefit, without removing the fault. The fix bears on the reviews themselves.
Does this rule apply to reviews from a third-party platform?
The document targets what you publish on your pages and in your markup. Reviews collected by an independent platform do not fall under the same control, but reproducing them on your site makes you responsible for what you display, their sincerity included.