Review Schema Best Practices and Mistakes to Avoid

The golden rules of Review schema are: mark up only genuine reviews, never rate your own product to give yourself stars, and always declare your rating scale — breaking any of these can cost you rich results or trigger a manual action. Valid markup is necessary but not sufficient; Google also checks that the reviews are real and shown on the page.

Here are the practices that keep review snippets safe, the mistakes that quietly disqualify pages, and how to troubleshoot when stars do not appear.

Best practices that keep snippets eligible

• Mark up only real, visible reviews. The review in your JSON-LD should exist on the page for users to read. Invisible or fabricated reviews are a policy violation.
• Always set bestRating and worstRating. Declaring your scale stops a 7-out-of-10 from being misread against the default 5-point assumption.
• Type itemReviewed specifically. Choose the most precise type — Product, Book, Movie, LocalBusiness and so on — so search engines model exactly what was reviewed.
• Match markup to visible content. The author, rating and text in the schema should mirror what visitors see, not a more flattering version.
• Validate before shipping. Run every page through the Rich Results Test to catch errors early.

Mistakes that cost you rich results

Mistake	Consequence	Fix
Reviewing your own product/service	Self-serving reviews violate guidelines; risk of manual action	Only mark up reviews written by others about the item
Omitting the rating scale	ratingValue misread, wrong stars	Set bestRating and worstRating explicitly
Marking up hidden reviews	Ineligible; looks manipulative	Ensure reviews are visible on the page
Confusing Review with AggregateRating	Wrong data model	Use Review for one critique, AggregateRating for averages
Vague itemReviewed type	Weaker eligibility	Pick the most specific matching type

The self-review trap

The single most common and most damaging error is adding Review markup to your own product or service to award yourself star ratings. Google's guidelines explicitly prohibit self-serving reviews on the entity that provides the item, and these violations commonly trigger manual actions that remove rich results site-wide. You can legitimately mark up reviews that customers or critics wrote about the item, but you cannot be both the reviewer and the reviewed. When in doubt, ask: did an independent person write this review? If not, do not mark it up.

Review versus AggregateRating

These two schemas answer different questions. A single Review represents one person's critique with one rating and an author. AggregateRating summarises many reviews into an average score and a count. Using the wrong one misrepresents your data — do not wrap ten reviews in a single Review, and do not report an average as if it were one person's opinion. This generator focuses on the single-review case; use aggregate markup separately when you are reporting a combined score.

Troubleshooting: stars are not showing

If your markup validates but stars never appear, remember Google decides when to display them — eligibility is not a guarantee. Confirm the reviews are genuine and visible, the type is eligible, and the scale is declared. Give it time to recrawl, and check Search Console for manual actions. Because the tool omits empty fields and runs entirely in your browser, the markup it produces is clean and private, but display always remains Google's call.

Try the Review Schema Generator — free and 100% in your browser.

FAQ

Can I add review stars to my own homepage?

No. Reviewing your own product or service to give yourself stars is a self-serving review that violates Google's guidelines and often triggers a manual action. Only mark up genuine reviews written by others.

Why did my valid markup not produce star ratings?

Valid markup only makes a page eligible; Google chooses when to show stars. Ensure the reviews are real and visible, the type qualifies, and wait for a recrawl.

What happens if I skip bestRating and worstRating?

The scale defaults to 5, so any rating out of a different scale can be misinterpreted. Always declare both bounds to keep your score unambiguous.

Should I use Review or AggregateRating for a list of customer reviews?

Use individual Review items for each critique, and AggregateRating to express the overall average and count. Do not collapse many reviews into one Review.

Related free tools

• Product Schema Generator — pair reviews with product data correctly.
• JSON-LD Generator — build and validate other schema types.
• Local Business Schema Generator — mark up a reviewed business.
• Organization Schema Generator — supply publisher information.

Built by ByteVancer

ByteTools is a free product of ByteVancer, a software and web development studio building web apps, SaaS and custom software. If you need SEO tools or a custom product, explore how ByteVancer can help.