§
§ · free tool

Review schema generator. Star ratings in JSON-LD.

Switch between individual Review and aggregate AggregateRating output. Pick the itemReviewed type (Product, LocalBusiness, Movie, Book, Recipe). Inline validator on every keystroke.

Switch mode (Review or AggregateRating), pick what's being reviewed, fill the rating + author. The right panel renders JSON-LD with the itemReviewed nested object. Pure browser code — no fetch, no log.

Mode:
review · single rating
JSON-LD output · live

              
    Sources used by this generator

    Privacy: form runs in-browser only.

    § 02 · two modes · one decision

    Review vs AggregateRating.

    Review represents one user's rating + body + author + date. Use it when you publish individual reviews on the page (Trustpilot widget, Yotpo block, native review system). Each Review object cites the specific reviewer; the rich result can show the user's quote.

    AggregateRating represents the summary across many reviews — the "4.7 / 128 reviews" badge. The rich result shows star count + total. Required: ratingValue, reviewCount > 0, and on the page itself there must be visible reviews backing the aggregate.

    Most product pages use both. An AggregateRating block for the visible badge, plus several Review objects for the individual reviews shown on the page. They reference the same itemReviewed and Google honors both for the rich result.

    itemReviewed types: the schema.org spec accepts Product, LocalBusiness (and subtypes), Movie, Book, Recipe, Service, Event, CreativeWork, SoftwareApplication. Pick the right type so the review-rich-result eligibility evaluates correctly. A Movie review unlocks the IMDB-style box; a Recipe review unlocks the cooking-time + calorie carousel; a LocalBusiness review feeds the local pack.

    Self-serving aggregateRating without underlying visible reviews is prohibited by Google and risks a structured-data manual action. The rule: aggregateRating must reflect reviews actually rendered on the same page. Don't fabricate; don't aggregate from elsewhere.

    § 03 · questions

    Six questions users ask.

    Review or AggregateRating — which do I need?

    Review is for a single user-written review (one rating + body + author). AggregateRating is for the summarized rating across many reviews (the 4.7 / 128 reviews badge). Most product pages use both: an AggregateRating for the visible badge plus several Review objects for the individual reviews shown on the page. Google requires AggregateRating to be backed by visible reviews on the same page — fabricated aggregates risk a structured-data manual action.

    Why pick an itemReviewed type?

    Schema.org Review requires the itemReviewed property pointing at what's being rated. The valid types include Product, LocalBusiness (and subtypes), Movie, Book, Recipe, Service, Event, CreativeWork, and SoftwareApplication. Picking the right type tells Google what kind of review-rich-result eligibility to evaluate.

    What rating scale should I use?

    Schema.org defaults to 5-star (worstRating: 1, bestRating: 5). You can override (10-star like IMDB, 100-point like Wine Spectator), but Google's rich result normalizes to 5-star regardless. Stick with 5-star unless you have a strong category convention.

    Can I include reviews I didn't write?

    Yes if the reviews are real and visible on the page. The schema represents what's published; if you display third-party reviews on your page with attribution, you can mark them up. Faking reviews violates Google's structured-data policy and risks a manual action.

    Should reviewBody be the full text?

    Yes for individual Review schema — include the actual review text. Google will use reviewBody as the visible quote in the rich result.

    Does this tool log my reviews?

    No. The form runs entirely in JavaScript on your device. Nothing is sent to Digital Heroes servers.