Free Aggregate Rating Schema Generator — JSON-LD AggregateRating Markup
Generate Google-valid AggregateRating schema markup instantly. Visual star rating builder, individual reviews array, rating breakdown distribution, and live Google SERP preview. Eligibility warnings for local businesses. 12+ parent item types. 5 entity templates. No signup. No watermark.
Rate this tool
Why this beats SEOSmoothie, ContentPowered, InstantSchema, and SEOShouts
How to generate AggregateRating schema markup
LazyTools vs other free aggregate rating schema generators
| Feature | LazyTools | SEOSmoothie | ContentPowered | InstantSchema | SEOShouts | Attrock |
|---|---|---|---|---|---|---|
| Visual star builder | ✅ Click stars | ❌ Number only | ❌ Number only | ❌ Number only | ❌ Number only | ❌ Number only |
| Live Google SERP preview | ✅ Yes | ❌ No | ❌ No | ❌ No | ❌ No | ❌ No |
| Rating breakdown distribution | ✅ Yes | ❌ No | ❌ No | ❌ No | ❌ No | ❌ No |
| Individual reviews array | ✅ 1-5 | ❌ No | ❌ No | ❌ No | ❌ No | ❌ No |
| Eligibility warnings | ✅ Yes | ❌ No | ❌ No | ❌ No | ❌ No | ❌ No |
| ratingCount + reviewCount both | ✅ Both | ❌ One field | ✅ Both | ❌ One field | ❌ One field | ❌ One field |
| Parent types supported | ✅ 12+ | ✔ 5 | ✅ 10 | ✔ 5 | ✔ 8 | ✔ 5 |
| Entity templates | ✅ 5 | ❌ None | ❌ None | ❌ None | ❌ None | ❌ None |
| Completeness score | ✅ Yes | ❌ No | ❌ No | ❌ No | ❌ No | ❌ No |
| Auto-save to browser | ✅ Yes | ❌ No | ❌ No | ❌ No | ❌ No | ❌ No |
| Download .json file | ✅ Yes | ❌ No | ❌ No | ❌ No | ✅ Yes | ❌ No |
| Dark code editor | ✅ Yes | ❌ No | ❌ No | ❌ No | ❌ No | ❌ No |
| No signup required | ✅ Never | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes |
AggregateRating Schema Guide — Star Ratings in Google Search Results in 2025
AggregateRating schema markup is one of the most visually impactful structured data types available. When Google recognises and displays your aggregate rating, your search listing shows gold stars alongside a numeric rating and review count. In a results page of blue links, gold stars are an immediate visual differentiator. Studies consistently show that listings with star ratings earn significantly higher click-through rates — BrightLocal found that a 5-star rating earned 28% more clicks than no rating, and 39% more than a 1-star rating. The impact on organic CTR is substantial and measurable without requiring any improvement in ranking position.
What is AggregateRating Schema?
AggregateRating is a schema.org type that represents the average rating based on multiple individual ratings or reviews. Unlike a Review (which represents a single person's opinion), AggregateRating summarises the collective judgement of many reviewers into a single average score with a total count. In JSON-LD, AggregateRating is always nested inside another entity — a Product, Recipe, Course, Book, Movie, SoftwareApplication, LocalBusiness, or other ratable item. The AggregateRating is not a standalone schema type — it must be embedded in a parent entity that Google recognises as eligible for star rating rich results.
ratingValue, ratingCount, and reviewCount — Which Properties to Use
ratingValue is the average rating score. This is the number displayed next to the stars in Google search results. reviewCount is the number of ratings that include written review text. ratingCount is the total number of ratings including star-only ratings without written text. The important distinction: if your site has 500 users who clicked 4 stars but only 120 who wrote a review, your ratingCount is 500 and your reviewCount is 120. You can include both properties simultaneously — Google will use whichever is most appropriate for its display. bestRating (default 5) and worstRating (default 1) define the scale. If your rating scale is 1-10 or 0-100, set these explicitly so Google can accurately interpret the rating value.
Which Entity Types Are Eligible for Star Rating Rich Results?
Google supports AggregateRating star rich results for these entity types: Book, Course, Event, HowTo, LocalBusiness (with restrictions), Movie, Product, Recipe, Software Application. For each type, Google may display the star rating in different formats. Product ratings appear prominently in shopping results. Recipe ratings appear in recipe carousels. Course ratings appear in course listings. Software app ratings appear in app store-style results. The key requirement is that your AggregateRating must be nested inside one of these supported parent types — a standalone AggregateRating without a parent entity will not generate rich results.
The Critical Local Business Restriction
Since 2019, Google has prohibited local businesses and organisations from using AggregateRating schema on their own websites to display self-rated reviews. The rule: if entity A (your business) controls the website and also controls the reviews about entity A on that website, the AggregateRating schema on your site will be ignored for star rating rich results. This was a response to widespread gaming of the feature where businesses were marking up their own self-created or cherry-picked reviews as "aggregate ratings."
The correct approach for local businesses is to use Google Business Profile — Google will automatically display your GBP rating in Knowledge Panels and local pack results when appropriate. For AggregateRating schema on third-party review sites that review local businesses (e.g., a Yelp-like directory page that reviews "Mike's Plumbing"), the restriction does not apply because the reviewing entity and the reviewed entity are different.
Individual Reviews vs AggregateRating — Using Both
Individual Review objects and AggregateRating can coexist in the same JSON-LD block, both nested inside the parent entity. Google treats them as complementary: the AggregateRating provides the summary star display while individual Review objects provide specific reviewer details that can appear as review snippets. For maximum rich result potential, include both: an AggregateRating with your average score and total count, plus 2-5 of your most representative individual reviews with author name, date, rating, and review text. Each review must correspond to a visible review actually displayed on your page — you cannot mark up reviews that are not visible to users.
Common AggregateRating Schema Mistakes
The most common mistake is fabricating or inflating ratings. Google's algorithms actively detect review manipulation and misrepresentation in schema markup. Sites that use fake ratings or mark up ratings higher than what users actually gave can receive manual actions removing their rich result eligibility entirely. The second most common mistake is omitting the parent entity — placing a bare AggregateRating without nesting it in a Product, Recipe, or other supported type. The third is confusing ratingCount and reviewCount — using ratingCount when you have written reviews means underreporting your review engagement. Always validate using Google's Rich Results Test (search.google.com/test/rich-results) before publishing, and monitor your rich result performance in Google Search Console under Enhancements.
AggregateRating schema — questions answered
AggregateRating schema markup is JSON-LD that tells search engines your average rating from multiple reviews. When correctly implemented and nested inside a supported parent entity (Product, Recipe, Course, etc.), Google may display gold star ratings in your search listings, significantly improving click-through rates.
ratingCount is the total number of ratings (including star-only ratings without written text). reviewCount is the number of ratings that include written review text. Use both if you have both types. Use reviewCount when users wrote reviews. Use ratingCount for platforms where users only click stars. Including both is recommended when you have data for both.
Google prohibits local businesses and organisations from using self-hosted AggregateRating schema on their own websites for star rating rich results (since 2019). If your business controls both the website and the reviews about itself on that website, Google will ignore the schema. Instead, use Google Business Profile reviews, which Google displays automatically in Knowledge Panels.
No. Valid AggregateRating schema makes your page eligible for star rating rich results, but Google decides whether to show them based on query relevance, site trustworthiness, and content quality. Having valid schema is necessary but not sufficient. Most sites with valid, genuine review data and high-quality content do earn star ratings within a few weeks.
Yes. Both can coexist nested inside the same parent entity (Product, Recipe, etc.). AggregateRating provides the summary stars while individual Review objects can generate review snippets. Each review must correspond to a visible review on your page. This combination gives Google maximum data to create rich results.
LazyTools Aggregate Rating Schema Generator is 100% free. No signup, no account, no credit card. Visual star builder, 12+ parent types, individual reviews array, rating breakdown, eligibility warnings, Google SERP preview, completeness score, 5 entity templates, dark editor, JSON download, auto-saved.