AggregateRating is a Schema.org type that represents a summarized numerical score derived from a collection of individual Review ratings. It averages multiple ratingValue inputs into a single ratingValue and specifies the total reviewCount or ratingCount, providing a statistically significant overview rather than a single subjective opinion.
Glossary
AggregateRating

What is AggregateRating?
A structured data type that computes a single representative rating from multiple user reviews or scores, enabling search engines to display aggregate star ratings in rich results.
This type is critical for Generative Engine Optimization because AI-driven search interfaces use AggregateRating to establish entity trust and quality signals. When properly implemented via JSON-LD on Product, LocalBusiness, or CreativeWork pages, it directly populates star-rich snippets and provides factual grounding for AI-generated summaries, influencing click-through rates and citation confidence.
Key Properties of AggregateRating
The AggregateRating type synthesizes multiple individual reviews into a single, statistically representative score. Understanding its core properties is essential for generating valid rich results and providing accurate summary data to AI-driven search engines.
ratingValue
The numerical quality score derived from aggregating all underlying ratings. This is the primary value displayed in search results.
- Data Type: Number or Text
- Requirement: Must be explicitly provided unless
ratingCountis 0. - Scale: Typically a 1-5 or 1-10 scale, but must be consistent with
bestRating. - Example: A product with an average of 4.5 out of 5 stars would set
ratingValueto4.5.
reviewCount
The total number of individual reviews or ratings compiled to calculate the ratingValue. This property provides statistical significance to the aggregate score.
- Data Type: Integer
- Distinction: Do not confuse with
ratingCount, which is a simpler tally of ratings without attached textual reviews. - Best Practice: Always provide a truthful count. A high
reviewCountcombined with a highratingValueserves as a strong trust signal to both users and AI algorithms.
bestRating & worstRating
These properties define the upper and lower bounds of the rating scale, allowing search engines to normalize the ratingValue.
bestRating: The highest possible value (e.g.,5).worstRating: The lowest possible value (e.g.,1).- Critical Rule: The
ratingValuemust fall between these two bounds. A scale of 1-5 is standard, but 10-point scales are also valid. Without these anchors, a 4.5 rating is ambiguous.
itemReviewed
The entity that is the subject of the rating. This property establishes the semantic link between the score and the product, service, or organization being evaluated.
- Data Type: Thing (typically
Product,Organization,CreativeWork, orService). - Nesting: The
AggregateRatingis usually nested directly inside theitemReviewedentity, but explicit linking viaitemReviewedis crucial for disambiguation. - Example:
"itemReviewed": {"@type": "Product", "name": "Widget X"}
ratingCount
The total number of simple ratings (e.g., star clicks without text) assigned to the item. This is distinct from reviewCount.
- Data Type: Integer
- Usage: Use this when users can leave a numeric rating without writing a full review.
- Combined Metrics: If a system collects both ratings and reviews, provide both
ratingCountandreviewCountto give a complete picture of user engagement volume.
author
The organization or person that performed the aggregation. This is not the end-user reviewer, but the entity compiling the statistics.
- Data Type: Organization or Person
- Trust Signal: Specifying the
author(e.g., a third-party review platform) adds a layer of provenance and credibility to the aggregate data. - Example:
"author": {"@type": "Organization", "name": "TrustPilot"}
Frequently Asked Questions
Clear, technically precise answers to the most common questions about implementing and understanding the Schema.org AggregateRating type for AI-driven search visibility.
AggregateRating is a Schema.org structured data type that represents a summary statistic of multiple individual ratings, calculated as an average. It works by aggregating discrete Review or Rating data points into a single, machine-readable object containing the ratingValue (the numerical mean) and reviewCount or ratingCount (the total number of contributions). When implemented correctly via JSON-LD, Microdata, or RDFa, this markup enables search engines and AI-driven answer engines to parse the collective sentiment about a Product, Organization, CreativeWork, or LocalBusiness without crawling every individual review. The mechanism relies on the itemReviewed property to link the aggregate score to a specific entity, allowing generative models to cite a statistically grounded reputation score rather than an anecdotal opinion.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Understanding AggregateRating requires familiarity with the broader Schema.org vocabulary for reviews, entities, and rich results. These related types and properties form the foundation of structured data markup.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us