Schema · Free

Free Review Schema Generator

Generate Review and AggregateRating JSON-LD schema for products, services, and businesses. Two modes: individual reviews with author and body, or aggregate ratings with average + count. Strictly for real, visible reviews.

  • No signup, no email required
  • Works entirely in your browser
  • Output you can copy and paste directly
  • Built by a working SEO team, not gated by upsells

Honesty notice. Google requires reviews and aggregate ratings in schema to reflect content actually visible on the page. Fabricating review counts or ratings is the single most-penalized form of structured data — typically results in a manual action that removes ALL rich results from your site. Use this tool for real reviews you actually have.

Reviews

0 valid · 1 total
Review 01

Output

JSON-LD
// Add an item name plus at least one complete review to generate.
Open Rich Results Test

What it does

Review schema marks up customer feedback in structured form so search engines can display star ratings in search results. Two flavors are supported here:

  • Individual reviews — each review is its own entity with author, rating, body, and date. Use when you have multiple distinct reviews on a page (testimonial section, case study quotes).
  • AggregateRating — the rolled-up average and count of multiple reviews, attached directly to the item being reviewed. Use when you display an overall rating (4.5/5 from 12 reviews) alongside the item.

Both produce valid schema.org JSON-LD ready to paste into your page head. The tool wraps the review around the right item type (Product, Service, LocalBusiness, Book, Movie, SoftwareApplication) so Google parses the relationship correctly.

Why review schema is high-stakes

Review snippets — the gold star ratings under blue-link results — are one of the highest-converting SERP elements available. Pages that earn them see CTR improvements of 15–35% versus comparable star-less results.

But review schema is also the single most-policed structured data type. Google's explicit rules:

  • Self-serving reviews are banned. Reviews of an entity left on the entity's own website do not qualify for the star-rating rich result. Reviews must come from third parties (Trustpilot, G2, Capterra, etc.).
  • Aggregate ratings must reflect visible reviews. The count and average must match reviews actually visible on the page or in a linked dataset Google can reach.
  • Fabricated counts get manual actions. Google's ML detection on review schema improved substantially in 2024–2026. Pattern-matched fake review counts get flagged automatically. Manual actions typically remove ALL rich results from the site.

The tool exists to make legitimate review markup easy. It is not a workaround for the rules.

How to use this generator

  1. Pick a mode. Use Individual Reviews when you have specific, named reviews visible on the page. Use Aggregate Rating when you have an overall score derived from multiple reviews.
  2. Set the item being reviewed. Name, type (Product / Service / LocalBusiness / etc.), and URL.
  3. Add the review data. For individual reviews: real author name (or pseudonym matching what's shown visibly), real rating, the review body verbatim. For aggregate: the actual average and count from your review source.
  4. Copy the output into the <head> of the page that displays the reviews visibly. Validate with the Rich Results Test.

Legitimate paths to review rich results

  • Third-party reviews on platforms. Reviews on G2, Capterra, Trustpilot, Clutch — those domains show up with stars in SERP for your brand queries. You don't need schema on your own site.
  • Service schema with linked third-party rating. If you have, say, 47 verified Trustpilot reviews at 4.8 average, mark up Organization or Service with aggregateRating pulling those numbers — Google validates against Trustpilot.
  • Embedded real testimonials with Review schema. If a real customer is willing to be quoted by name with their company, that's a Review entity Google will respect.
  • Product schema without aggregate rating. Pages with Product schema can earn product rich results without any rating claim — keeps you eligible for other rich results without review-snippet risk.

Review schema best practices

  • Match exactly to visible content. The review body in your schema must match the visible quote verbatim. Author name must match the visible byline. Rating must match what's shown.
  • Include datePublished. Old reviews show as old; that's fine. Hidden dating triggers freshness heuristics that flag the schema.
  • Use Person for author. Real human authors on real reviews. Brand-as-author or anonymous reviews don't qualify for the rich result.
  • Don't inflate ratings. The average in your AggregateRating must match the actual computed average of visible reviews. Rounding up is detectable and risky.
  • One review entity per visible review. Don't pad the count with fake reviews. The visible count and the schema count must match.

Common review schema mistakes

  • Self-serving reviews schema. Reviews written by you about your own products. Banned by Google.
  • Aggregate without visible reviews. Claiming an aggregate rating when the page has no reviews visible. Auto-flagged by Google's spam detection.
  • Padded review counts. Showing 8 reviews visibly but claiming 487 in schema. The single most common self-inflicted manual action in 2024–2026.
  • Wrong itemType wrapper. Putting Review schema inside a generic WebPage instead of a typed item (Product, Service, LocalBusiness). Reduces rich-result eligibility.
  • Stale schema after content changes. Removing visible reviews without removing them from schema, or vice versa.

Frequently asked questions

Will this tool make stars appear in my search results?

Only if the underlying reviews are real, third-party, and visible on the page. Self-serving review schema (reviews of your own product written by you) is explicitly banned by Google and will not earn the star-rating rich result. The path to legitimate stars is to collect real reviews on platforms like G2, Trustpilot, or Capterra and mark up verifiable aggregate data.

Why are self-serving reviews banned?

Because they're trivially gameable and corrupt the SERP. Google's stated policy: review snippets are not allowed for reviews left on the same entity's own website. The reviews must come from third parties to qualify. This rule has been in place since 2019 and enforcement has only gotten stricter.

What if I really do have customer reviews on my site?

If they're real customer reviews collected through a verifiable system (a review platform you embed, a CMS-managed system you can demonstrate is bona fide), the schema can be valid — but Google may still apply review-snippet ineligibility for self-hosted reviews on certain item types. The safer pattern is to collect reviews on a third-party platform and link to them.

Is AggregateRating safer than individual Review schema?

Same rules apply to both. AggregateRating must reflect verifiable, visible review data on the page. Faking it is the same risk as faking individual reviews.

Can I use this for case-study quotes?

Technically the schema accepts case-study quotes as Review entities — but case-study quotes are unlikely to qualify for the review-snippet rich result because they're self-published. Better to focus case-study marketing on content quality and let Trustpilot/G2 carry the rating signal separately.

What item types can I review?

Schema.org supports Review on most types — Product, Service, LocalBusiness, Book, Movie, SoftwareApplication, Restaurant, Event, and many more. This tool covers the most common six. For others, use the schema.org type with the same Review structure.

Will this tool log my data?

No. Everything runs in your browser. The fields you fill never leave your device — there is no server endpoint and nothing to log.