Issue #61 · standard
Issue 61
What is this issue?
Pages with visible user reviews or ratings are missing AggregateRating or Review schema, preventing star ratings from appearing in Google search results.
Without AggregateRating schema:
- Star ratings won't appear in search results
- Users won't see social proof before clicking
- Rich snippets showing review counts won't display
- Competitors with ratings may get more clicks
- Product or business credibility is reduced
A proper AggregateRating schema should be nested inside Product, LocalBusiness, Recipe, Movie, or other reviewable schemas and include: ratingValue, reviewCount, bestRating (default 5), worstRating (default 1).
Why does it matter?
AggregateRating schema significantly impacts click-through rates and trust:
- Star ratings in search: Pages with star ratings get 35% more clicks on average
- Social proof: Users trust businesses and products with visible ratings
- Rich snippets: Enables review count and rating display in search results
- Local SEO: LocalBusiness with ratings appear more prominently in maps
- AI search signals: AI engines use rating data to recommend top-rated options
- Conversion rates: Products with ratings have higher conversion rates
Resolving this issue improves your SEO health score by adding powerful social proof signals that increase click-through rates and user trust.
How to fix it
-
Identify reviewable content: Check pages with
Product,LocalBusiness,Recipe,Movie,Book, or similar schemas -
Add AggregateRating to your schema:
{ "@context": "https://schema.org", "@type": "Product", "name": "Product Name", "description": "Product description", "aggregateRating": { "@type": "AggregateRating", "ratingValue": "4.5", "reviewCount": "125", "bestRating": "5", "worstRating": "1" }, "offers": { "@type": "Offer", "price": "29.99", "priceCurrency": "USD" } } -
Use correct values:
ratingValue: Numeric value as string (e.g., "4.5")reviewCount: Integer as string (e.g., "125")bestRating: Usually "5" (default if not specified)worstRating: Usually "1" (default if not specified)
-
Ensure ratings are legitimate:
- Only use real reviews from actual customers
- Don't create fake reviews or manipulate ratings
- Make sure the rating matches what's displayed on the page
-
Validate with Google's Rich Results Test
Examples
Example 1: Missing AggregateRating in Product Schema
Problematic state (Product without AggregateRating):
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Wireless Headphones",
"description": "High-quality wireless headphones"
}
Missing aggregateRating property
Corrected state:
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Wireless Headphones",
"description": "High-quality wireless headphones",
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.5",
"reviewCount": "125",
"bestRating": "5",
"worstRating": "1"
}
}
Example 2: AggregateRating in LocalBusiness Schema
Corrected state (LocalBusiness with ratings):
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Coffee Shop Downtown",
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.8",
"reviewCount": "342",
"bestRating": "5",
"worstRating": "1"
}
}
Example 3: Incomplete AggregateRating Schema
Problematic state (missing required properties):
{
"@context": "https://schema.org",
"@type": "Recipe",
"name": "Chocolate Chip Cookies",
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "5"
}
}
Missing reviewCount property
Corrected state:
{
"@context": "https://schema.org",
"@type": "Recipe",
"name": "Chocolate Chip Cookies",
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "5",
"reviewCount": "89",
"bestRating": "5",
"worstRating": "1"
}
}
How PixyScan detects this
PixyScan follows these logical steps to detect missing or incomplete AggregateRating schema:
-
Find reviewable schemas: The crawler identifies pages with schemas that commonly have ratings:
ProductLocalBusiness(and subtypes)RecipeMovie,Book,Course- Any schema with
revieworaggregateRatingproperties
-
Check for AggregateRating: The crawler examines whether the schema has an
aggregateRatingproperty -
Validate AggregateRating structure: If present, the crawler checks:
- Does it have
@typeset toAggregateRating? - Does it have
ratingValue? - Does it have
reviewCount?
- Does it have
-
Validate rating values: The crawler verifies:
ratingValueis a valid numberreviewCountis a valid integerratingValueis betweenworstRatingandbestRating(if specified)
-
Check page consistency: The crawler compares the schema rating with:
- Visible ratings displayed on the page
- Any
reviewproperties also present in the schema
-
Trigger conditions: The issue is flagged when:
- A reviewable schema exists BUT
aggregateRatingis missing aggregateRatingexists butratingValueis missingaggregateRatingexists butreviewCountis missingratingValueis outside the valid range
- A reviewable schema exists BUT