Review snippet rules decide if rating markup has a chance to show as stars and review summary data in search. Google treats review snippets as a search feature tied to valid Review or AggregateRating markup, visible page content, and feature specific quality rules. Even valid markup is only eligible, not guaranteed, so the right goal is clean eligibility, not a promise of display.
If you want the wider schema cluster first, start with Schema for SEO. If you need the format first, read JSON LD Basics. If the page is about a SaaS product, pair this page with Product Schema for SaaS and SoftwareApplication Schema.
The short answer
Use review snippet markup only when the page shows real review content or a visible aggregate rating for a supported item type, and keep the markup tied to the main thing the page is about. For Google, that means the review data must match visible content on the page, use supported structured data formats, and follow the review specific rules plus the broader structured data policies.
What review snippets apply to
Google’s review snippet documentation lists support for review snippets on these main types: Book, Course list, Event, Local business, Movie, Product, Recipe, and Software App. It also supports reviews for several related Schema.org types, including CreativeWorkSeason, CreativeWorkSeries, Episode, Game, MediaObject, MusicPlaylist, MusicRecording, and Organization, with extra limits for local business and organization reviews.
For Schema.org itself, AggregateRating is the average rating based on multiple ratings or reviews, while Review describes a single review and uses reviewRating for the rating tied to that review. That distinction is the core split between a single editorial or user review and a rolled up rating shown from many reviews.
The rule most sites get wrong
Google no longer shows self serving review rich results for LocalBusiness and Organization when the business marks up reviews about itself on its own site. Google’s public update on review rich results says those self serving review snippets are no longer displayed for businesses and organizations, and the review snippet documentation still points local business and organization publishers to that limit.
That means a company should not expect stars in search for markup that says people reviewed the company on the company’s own site if the marked up item is the organization or local business itself. This is the cleanest reason to treat review snippet work as page type specific, not site wide.
The content must be visible on page
Google’s review snippet rules say the review content you mark up must be readily available to users on the marked up page. If you mark up reviews, users should be able to see the review text and rating; if you use AggregateRating, users should be able to see that aggregate rating on page. Google’s general structured data policies also say the markup must represent the main content, must not be hidden, and must not be misleading.
This is where lots of pages fail. Teams add stars in JSON LD, but the page itself does not show the review or the rolled up rating in a clear way. That breaks the page to markup match Google is looking for.
Review snippet rules for product and software pages
Review snippets fit especially well on product pages and software pages because Google lists Product and Software App among the supported types. Product structured data can also carry review information for product snippets, so product pages that show ratings, price, and availability often need product markup decisions and review snippet decisions at the same time.
On Semantec SEO, that makes this page a close sibling to Product Schema for SaaS and SoftwareApplication Schema. If the page is mainly about the software entity, use the software page type logic first. If the page is mainly about commercial product details, check the product page logic first.
Review vs aggregate rating
Use Review when the page contains a single review or a clearly defined set of individual reviews tied to a specific item. Use AggregateRating when the page shows a rolled up rating from multiple reviews or ratings. Google’s technical guidelines for review snippets call out AggregateRating for the evaluation of an item by many people. Schema.org also defines AggregateRating as the overall rating based on a collection of reviews or ratings.
A simple editorial test helps here:
- one reviewer, one review block =
Review - many reviewers, one visible combined score =
AggregateRating
The page must point to a specific reviewed item
Google says the review should refer clearly to a specific product or service by nesting the review inside another Schema.org type or by using a supported type as the value for itemReviewed. In plain terms, the stars need a clear target. “This page has a rating” is weak. “This product has a rating” is clear.
That is why entity clarity still comes first. If the page blurs product, brand, article, and comparison intent into one URL, review markup gets messy fast. In those cases, work through Entity Markup and the page brief before you touch the schema.
Use the main page type, then add review data
Google’s general structured data policies say the page should include the main structured data type that reflects the main focus of the page. If the page is mainly about a product, include product markup and then add the review data that belongs with it. If the page is mainly about software, start from the software page type. This helps Google understand the page focus and any secondary items on the page.
That rule is easy to miss on mixed pages. A SaaS page can have software details, product details, pricing details, and review data, but the page still needs one clear primary type.
Google’s baseline quality rules
Google’s structured data policies say rich result eligibility can be lost when markup is misleading, hidden, irrelevant to the page focus, or missing required properties. Google also says structured data should follow content and spam policies, and fake reviews or ratings can lead to manual action. Google recommends JSON LD, though Microdata and RDFa are also supported.
So the working rule is simple: show the review content on page, mark up only what the page really contains, fill required properties, and validate before publishing.
A clean JSON LD pattern
Here is a simple starter example for a software review page that shows a visible combined rating.
{
"@context": "https://schema.org",
"@type": "SoftwareApplication",
"name": "MIRENA",
"applicationCategory": "BusinessApplication",
"operatingSystem": "Web",
"url": "https://semantecseo.com/mirena/",
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.9",
"ratingCount": "26"
}
}
This pattern works only if the page clearly shows the software as the main reviewed item and shows the same combined rating on page. If the page shows a single named review instead, switch to a Review pattern and make the reviewer, review text, and rating visible on page.
Five review snippet rules worth checking before publish
1. The reviewed item is supported
Start by checking that the item type is one Google supports for review snippets, such as Product or Software App.
2. The review is visible
The review text or aggregate score must be visible to users on the marked up page.
3. The page type is clear
Use the main structured data type that reflects the page focus, then attach review data to that item.
4. The reviews are not self serving for organization or local business
If the site is marking up reviews about itself as an organization or local business, Google says those self serving rich review snippets are not shown.
5. The markup is validated
Google recommends validating with the Rich Results Test, then checking the page with URL Inspection after deployment. Search Console also has a review snippet enhancement report for tracking issues on marked up pages.
Common mistakes
Marking up ratings with no visible review content
This is one of the fastest ways to lose eligibility. Google wants the review or aggregate score visible on the page.
Adding stars to the company’s own about page
For Organization and LocalBusiness, self serving review rich results are not shown.
Mixing review data into the wrong page type
A broad article about industry tools is not the same thing as a product review page for one item. Keep the page role clear first.
Treating markup as a display promise
Google says structured data can make a feature eligible, but it does not guarantee that the feature will appear in search.
How this fits the wider schema workflow
Review snippet work is stronger when it is planned in the brief, not bolted on at the end. The brief should lock the page purpose, the main entity, the reviewed item, the visible review block, and the markup type before the page goes live. If you want that planned inside the product workflow, go to MIRENA or MIRENA for Content Briefs.
For the rest of this cluster, read Schema for SEO for the broader markup model, JSON LD Basics for syntax and placement, Product Schema for SaaS for commercial product pages, and SoftwareApplication Schema for software first pages.
Final take
Review snippet rules are not about sprinkling stars across a site. They are about using the right item type, showing real review content on page, avoiding self serving markup where Google has drawn a line, and validating the result before release. The cleanest path is simple: pick the right page type, attach the review to a specific item, keep the review visible, and publish markup that matches the page.
FAQ
Can review snippets appear for software pages?
Yes. Google lists Software App among the supported review snippet item types.
Can a business mark up its own company reviews and get stars?
Not for self serving Organization or LocalBusiness review rich results. Google says those are not shown.
Do I need both Review and AggregateRating?
Not always. Use the one that matches what the page shows. A single review points to Review. A visible rolled up score from many reviews points to AggregateRating.
Is JSON LD the best format for this?
Google supports JSON LD, Microdata, and RDFa, and recommends JSON LD.
Does valid review markup guarantee stars in search?
No. Google says valid structured data makes a feature eligible, not guaranteed.