Reviews and Ratings
Star ratings are the rich result everyone asks for. They're also the one with the most rules. Here's how to mark up reviews honestly, and why "put stars on our homepage" isn't going to work.
Two different things
A Review is one person's opinion of one thing: who wrote it, when, what they said, and the score they gave. An AggregateRating is the summary: the average score across everyone, and how many ratings or reviews that average is based on.
A product page usually has both. "4.8 out of 5 from 23 reviews" at the top is the AggregateRating. Each review underneath is a Review. You'll normally nest them inside the thing being reviewed, using its aggregateRating and review properties.
Which things can show stars
Google only shows review snippets for certain types. According to its review snippet docs, the reviewed item can be a:
Things you sell or make
Product, Book, Course, SoftwareApplication, Game, Recipe, Event
Media
Movie, Episode, CreativeWorkSeason, CreativeWorkSeries, MusicRecording, MusicPlaylist, MediaObject
Businesses (with a catch)
LocalBusiness and Organization, but only when the reviews are about other businesses. More on this below.
Everything else
Valid Schema.org, but no stars in Google. A Service or an Article won't get a star snippet.
The self-serving review rule
This is the big one. If a business publishes reviews of itself on its own site, and marks them up with LocalBusiness or Organization, Google calls those self-serving reviews. They aren't eligible for star snippets. That's true even when the reviews are real, and even when they come from an embedded third-party widget.
So Fern & Ink can't put "4.9 stars from 60 clients" on its homepage Organization and expect stars in search. The place for those reviews to count is where other people control them: Google Business Profile, Yelp, and similar sites.
What Fern & Ink can do is mark up reviews of a product it sells. A review site, a directory, or a magazine reviewing local print shops could also mark up reviews of Fern & Ink, because they're reviewing someone else.
In plain termsReviews of your products on your product pages: fine. Reviews of your company on your company's own website: valid markup, but no stars. Don't over-promise this to a client.
The code
Fern & Ink sells a hand-printed notebook on its shop page, and customers leave reviews there. The page shows "4.8 out of 5, based on 23 reviews," then lists the reviews. Here's the markup, with the summary and one of those reviews:
{
"@context": "https://schema.org",
"@type": "Product",
"@id": "https://fernandink.example/shop/letterpress-notebook/#product",
"name": "Fern & Ink Letterpress Notebook",
"image": "https://fernandink.example/images/letterpress-notebook.jpg",
"description": "A 96-page dot-grid notebook with a hand-printed letterpress cover on cotton board.",
"brand": { "@type": "Brand", "name": "Fern & Ink" },
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 4.8,
"reviewCount": 23,
"bestRating": 5,
"worstRating": 1
},
"review": [
{
"@type": "Review",
"author": { "@type": "Person", "name": "Priya Shah" },
"datePublished": "2026-10-21",
"reviewBody": "The cover is beautiful and you can feel the impression. The paper takes fountain pen without bleeding.",
"reviewRating": {
"@type": "Rating",
"ratingValue": 5,
"bestRating": 5,
"worstRating": 1
}
}
]
}
The example shows one review to keep it short. On the real page, you can include every review that's visible, or a subset. What you can't do is include reviews that aren't on the page.
Line by line
| Property | What it holds | Status |
|---|---|---|
| Review | ||
author | A Person or Organization with a real name. Not "Happy customer" or a sales message. | Required |
itemReviewed | The thing being reviewed. Skip it when the review is nested inside that thing, as above. | Required |
reviewRating | A Rating with a ratingValue. | Required |
bestRating, worstRating | The top and bottom of the scale. Google assumes 5 and 1 if you leave them out. | Recommended |
datePublished | When the review was posted. | Recommended |
reviewBody | The review's text, as shown on the page. | Optional |
| AggregateRating | ||
ratingValue | The average score, with a dot for decimals: 4.8, not 4,8. | Required |
ratingCount or reviewCount | At least one. ratingCount counts all ratings; reviewCount counts people who left a review. | Required |
itemReviewed | Skip it when nested inside the reviewed item. | Required |
bestRating, worstRating | The scale. Defaults to 5 and 1. | Recommended |
Rating on a 10-point scale? Say so with "bestRating": 10. Otherwise an 8 looks like an impossible score on a five-star scale.
A standalone review
Sometimes the whole page is a review. Say Maya Lund writes a blog post reviewing a printing handbook. Then the Review is the main thing, and itemReviewed says what it's about:
{
"@context": "https://schema.org",
"@type": "Review",
"itemReviewed": {
"@type": "Book",
"name": "Ink and Iron: A Small-Press Printing Handbook"
},
"author": { "@id": "https://fernandink.example/about/#maya" },
"datePublished": "2026-11-02",
"reviewRating": {
"@type": "Rating",
"ratingValue": 4,
"bestRating": 5
},
"publisher": { "@id": "https://fernandink.example/#organization" }
}
The author here points at Maya's Person by @id. That works when her full Person markup (with her name) is on the page or in your site's graph. If it isn't, write { "@type": "Person", "name": "Maya Lund" } instead, because a review's author needs a name.
Keep it honest
Review markup is where people get tempted to cut corners, and where Google is quickest to act. Google can issue a manual action for spammy structured data, which takes away rich results for the site. The rules are short:
- Only mark up reviews people can see on the page. No pulling in reviews from elsewhere, no "summary" ratings that aren't displayed.
- Only real reviews from real people. No reviews written by the business, its staff, or anyone paid to write them.
- Keep the numbers in sync. When a new review comes in and the page says 24, the markup should say 24 too. This is why ratings are best generated by the same code that displays them, not typed by hand.
Common mistakes
- Adding
aggregateRatingto your ownOrganizationorLocalBusinessand expecting stars. - Ratings in the markup that don't appear anywhere on the page.
- An
AggregateRatingwith noratingCountorreviewCount. - Author names like "Verified Buyer" or "Save 20% today!" instead of a real name.
- Hard-coded counts that go stale as new reviews arrive.
- Review markup on a type that can't show stars, like
Service, then wondering why nothing appears.
Try it
Fern & Ink's notebook page gets a second review: Marcus Bell, posted November 9, 2026, four stars. Add it to the review array in the example. Then work out what else on the page and in the markup needs to change. (Hint: the count, and maybe the average.)
Check yourself
- I can explain the difference between a
Reviewand anAggregateRating. - My reviewed item is a type that can show stars.
- I'm not marking up reviews of my own business on my own site and expecting stars.
- Every review in my markup is visible on the page, with a real author name.
- My
AggregateRatinghas aratingValueand a count that match the page.
Reviews alongside the other rich-content types: Schema Markup Explained, Part 3: FAQ, Person, Event, Recipe, and Reviews.