Create Review and AggregateRating JSON-LD for products, apps, courses, recipes and more. Add one review or several, calculate the average from them, and check Google’s review snippet rules as you type. Free, no sign-up, and nothing leaves your browser.
Google assumes 1 to 5. Set both for another scale, such as 1 to 10.
Optional, alongside the number of ratings.
Review schema and rating schema are structured data, based on the schema.org Review and AggregateRating types, that describe what people think of an item. A Review is one person’s opinion with a rating. An AggregateRating is the average of many ratings with a count.
When the markup is valid and follows Google’s guidelines, Google may show a review snippet: gold stars, the rating and the number of reviews under your result. Stars draw the eye, so they can lift the share of searchers who click.
Review markup always describes a specific item, such as a product, app, course or recipe. It usually sits inside that item’s own schema, as in the example here.
{
"@context": "https://schema.org",
"@type": "Product",
"name": "AuraCam Camphor Pods",
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 4.6,
"ratingCount": 128
},
"review": [
{
"@type": "Review",
"author": { "@type": "Person", "name": "Priya Sharma" },
"datePublished": "2026-09-14",
"reviewRating": { "@type": "Rating", "ratingValue": 5 },
"reviewBody": "Burns cleanly and the scent lasts for hours."
}
]
}Review and AggregateRating each have their own required properties. The checklist beside the code tracks them as you type.
| Property | Review | AggregateRating |
|---|---|---|
Item name | Required | Required |
ratingValue | Required | Required |
author, under 100 characters | Required | Not used |
ratingCount or reviewCount | Not used | One required |
datePublished | Recommended | Not used |
bestRating, worstRating | If not 1 to 5 | If not 1 to 5 |
reviewBody, publisher | Optional | Not used |
Use AggregateRating for the average your page shows, and Review for each individual review on the page. Most product pages need both.
One person’s opinion
A single review with the author’s name, their rating and, ideally, the date and text. Add one for each review visible on the page.
{
"@type": "Review",
"author": {"@type": "Person", "name": "Rahul"},
"reviewRating": {"@type": "Rating", "ratingValue": 4}
}The average of many
The overall score shown on the page, with the number of ratings or reviews behind it. It drives the stars and count in results.
{
"@type": "AggregateRating",
"ratingValue": 4.6,
"ratingCount": 128
}Valid markup makes a page eligible, but Google decides whether to show stars. When they do not appear, the cause is usually one of these four.
Red types are affected by the self-serving review rule.
Nested markup puts review and aggregateRating inside the item’s own schema, such as your Product. Use it on the item’s page, which is the most common case. Choose “Nested in the item” in the generator.
Standalone markup keeps the Review separate and names the item with itemReviewed. Use it on a page that is mainly a review, such as an editorial review of a phone. If you already have Product schema on the page, nest the reviews inside it instead of adding a second item.
{
"@context": "https://schema.org",
"@type": "Review",
"itemReviewed": {
"@type": "Product",
"name": "Pixel 10 Pro"
},
"author": {
"@type": "Person",
"name": "Ananya Rao"
},
"datePublished": "2026-10-02",
"reviewRating": {
"@type": "Rating",
"ratingValue": 8.5,
"bestRating": 10,
"worstRating": 1
}
}The generator above writes the code. These four steps take it live.
Choose one of the 17 item types and enter the item’s name.
Add each review shown on the page, with the author and rating.
Enter the average and count shown on the page, or calculate them.
Add the code to the item’s page, then run the Rich Results Test.
If your page already has Product, Recipe or Course schema, copy just the review and aggregateRating parts into it, so the page has one item rather than two. Keep the numbers in the markup the same as the page, and update both when new reviews arrive.
Short answers on requirements, stars, scales and Google’s review rules.
Review and AggregateRating schema describe what people think of a specific item. When the markup is valid and follows Google’s guidelines, Google may show a review snippet with stars, the rating and the review count in search results.
For a Review, Google requires the item’s name, a rating value and an author name under 100 characters. For an AggregateRating, it requires the item’s name, the rating value, and a rating count or review count.
A Review is one person’s opinion with their rating. An AggregateRating is the average of many ratings with a count. Use AggregateRating for the overall score on the page and a Review for each individual review shown.
No. If a LocalBusiness or Organization publishes or controls reviews about itself, through its own markup or an embedded widget, Google will not show star results for those pages.
Book, Course, CreativeWorkSeason, CreativeWorkSeries, Episode, Event, Game, HowTo, LocalBusiness, MediaObject, Movie, MusicPlaylist, MusicRecording, Organization, Product, Recipe and SoftwareApplication.
The most common causes are self-serving reviews, ratings that are not visible on the page, an unsupported item type, and ratings copied from other sites. Valid markup makes a page eligible, but Google decides whether to show stars.
Yes, on a product page. Nest review and aggregateRating inside the Product so the page describes one item. Use a standalone Review with itemReviewed only on pages that are mainly a review.
Set bestRating to 10 and worstRating to 1. Google assumes a 1 to 5 scale when they are missing. Always use a dot for decimals, such as 8.5.
No. Google’s guidelines say not to mark up ratings collected on other sites. Only mark up reviews and ratings your own visitors left, shown on your own page.
Yes. It is completely free, with no sign-up and no limit. Everything runs in your browser, so your reviews are never uploaded to a server.
Review markup lives inside the item it describes.
Search Savvy’s technical SEO team audits review markup, fixes eligibility issues and sets up review collection that follows Google’s rules.