Can a business mark up reviews it collected itself?
Real first-party testimonials can appear visibly, but self-serving review markup for your own organization is generally ineligible for Google review stars.
Written for businesses and SaaS teams deciding how to publish customer testimonials without creating misleading review structured data.
Key facts
- Google excludes self-serving reviews for LocalBusiness and Organization rich-result stars.
- Embedding ratings from a third-party widget does not remove self-serving control when the reviewed entity controls the page.
- Testimonials can still help readers when consent, context, and verification are clear.
A useful rule: make each important claim understandable and verifiable without requiring the reader to reconstruct your meaning from the rest of the page.
What makes review markup self-serving?
Markup is self-serving when the entity being reviewed controls the page that publishes the rating about itself. Google specifically excludes review snippets for LocalBusiness and Organization when reviews about those entities are placed on their own pages, whether collected directly or embedded through a third-party widget. The reviews may be genuine and useful to customers, but the rich-result eligibility rule remains. Do not change the reviewed type or wrap the business in a Product object simply to bypass the policy. Model the real entity and accept that visible social proof does not automatically qualify for search stars.
- Identify who controls the page and who is being reviewed.
- Do not relabel an organization as a product to chase stars.
- Separate testimonial value from rich-result eligibility.
Can the testimonials remain on the page?
Yes, when they are genuine, relevant, and published with appropriate permission. Show the reviewer's name or approved identifier, the context of their experience, and the date when available. Avoid editing a quote in a way that changes its meaning, combining comments from different people, or presenting incentives as independent praise. Explain how feedback was collected and whether a customer received compensation. This visible evidence can reduce buyer uncertainty even without Review JSON-LD. A small set of specific, verifiable testimonials is stronger than a carousel of anonymous superlatives.
- Obtain consent and preserve the reviewer's intended meaning.
- Disclose incentives and collection method.
- Use specific outcome context instead of anonymous praise.
Sources: 2
What about reviews of products sold by the business?
A merchant page for a distinct product can have review markup when it follows Product and review policies, the reviews concern that product, and all marked ratings are visible. The product must be a real item or service represented accurately, not the business itself disguised as a product. Aggregate values must be calculated from the displayed review corpus and updated consistently. If staff select only favourable submissions, state the moderation method. Eligibility still is not guaranteed, and merchant-specific programs may have additional data requirements beyond on-page JSON-LD.
- Keep the reviewed product distinct from the selling organization.
- Calculate aggregate values from the visible eligible set.
- Document moderation and update procedures.
Should third-party ratings be copied into JSON-LD?
Only when licensing, display, and feature policies permit it and the values are visible on the page. A badge or widget does not automatically grant permission to reproduce rating data in your own structured object. Link to the original profile for verification and read the provider's terms. Do not combine incompatible scales or review populations into one aggregate. For an Organization's own site, third-party sourcing also does not defeat Google's self-serving review restriction. Use the rating as visible external evidence where allowed, not as a loophole for controlled search presentation.
- Check data licensing before copying third-party values.
- Keep scales and populations separate.
- Do not treat a widget as automatic schema permission.
What is the safer trust strategy?
Publish clear product details, pricing, limitations, methodology, customer examples, and attributable testimonials. Link independent reviews without asserting that they are the same as your identity. Use Organization and Product markup only for facts the visible page supports, and omit aggregate ratings when policy or provenance is uncertain. Measure whether visitors understand the offer and complete an appropriate action. This approach earns trust through inspectable evidence and avoids a brittle dependence on star presentation that may never appear or could be removed after a policy review.
- Prioritize verifiable claims and clear offer terms.
- Keep structured data narrower than uncertain evidence.
- Measure qualified actions rather than star visibility alone.
Put it to work
Find the highest-impact fix on your site.
Map the reviewed entity, page controller, visible reviews, and aggregate calculation before emitting schema.
Audit review markupSources
- 1.Google Search Central: Review snippet structured dataChecked 2026-07-26
- 2.Google Search Central: General structured data guidelinesChecked 2026-07-26