Review and rating markup

A large share of review markup on the web is doing nothing, and the reason is a single documented rule that almost nobody reads before implementing.

The rule, stated plainly

Review and aggregate-rating markup exists so a site that reviews things can expose those ratings. It is not a mechanism for a business to publish its own score.

So the common implementation — a testimonials page, an AggregateRating of 4.9 built from reviews the business gathered, applied to the business's own Organization or LocalBusiness — is not eligible. It will not produce stars. In its more aggressive forms, where the rating is marked up but not shown to visitors, it is a structured data violation.

The second half of that matters as much as the first. Marked-up content must be visible on the page. Google's wording is that the review content marked up must be readily available to users from the marked-up page, and that it must be immediately obvious the page has review content — for an aggregate rating, the user should be able to see the rating. Markup describing a rating a reader cannot see is misrepresentation, and it is the category of error that attracts a manual action rather than simple ineligibility.

The widget loophole that is not one

This is the detail that catches careful teams, and it is documented explicitly.

Embedding a third-party review widget on your own site does not create eligibility. Google's guidance names this case directly: a review about entity A placed on entity A's website is self-serving, including when the reviews arrive through an embedded third-party widget. Routing the same reviews through a vendor's JavaScript does not change whose site they are on or who controls them.

Teams reach for the widget specifically to escape the restriction, usually on a vendor's advice. It does not work, and the vendor is rarely the one who finds out.

What to do instead

For Google reviews: nothing. They live on your business profile. There is no markup step, and copying them onto your site with markup attached does not create eligibility.

For testimonials: publish them as content. Real quotes, attributed as specifically as your profession allows, on a page a person would want to read. They work on the reader, which is the job. Skip the markup.

For genuine review content: mark it up properly. If you review products, books or services editorially, Review and AggregateRating apply exactly as documented — because you are reviewing something other than yourself.

For the entity itself: use Organization or LocalBusiness markup with the facts that are legitimate — name, address, phone, identifiers, sameAs profiles — and let the review content sit where it belongs. That is the connected-graph approach in the structured data spoke, and it is more valuable than a star rating you are not entitled to.

Why the restriction exists

Because the alternative is worthless. If every business could publish its own aggregate rating in markup, every business would publish a high one, and the signal would carry no information within a week.

Review signals are useful precisely because they are collected and displayed by somebody with no stake in the number. That is the same principle running through this entire pillar: the evidence you did not write is the evidence that counts.

The audit

If your site already has review markup, check three things:

1. Is the review about your own business? If yes, it is not eligible, and removing it is cleaner than leaving markup that does nothing.
2. Is every marked-up value visible on the page? If a rating appears only in the JSON-LD, fix that first — it is the part that carries real risk.
3. Does the marked-up rating match what the page actually shows? A mismatch between markup and visible content is the clearest version of the same violation.