AggregateRating Schema
AggregateRating schema is the Schema.org property that declares the aggregate rating of an entity (business, product, service, app) from multiple reviews. Required for star-rating display in SERPs, Local Pack ranking influence, and AI Overview trust-signal extraction. Must reflect real verifiable reviews from real sources (typically Google Business Profile, App Store, third-party review platforms).
Also called: aggregateRating JSON-LD, Review aggregate schema · Last updated: May 27, 2026 · By Joseph W. Anady
Why it matters.
AggregateRating turns the reviewers' collective verdict into a structured data point Google can extract and surface. The visible reward is star-rating display in SERPs (improves CTR substantially). The hidden reward is Local Pack ranking influence — Google's local algorithm weights aggregate rating as a trust signal. The catch: faked ratings violate Google's spam policies and are increasingly detected.
How it works.
AggregateRating typically appears as a property of Organization, LocalBusiness, Product, Service, or CreativeWork schema (not standalone). Required: @type AggregateRating, ratingValue (the average), reviewCount or ratingCount. Recommended: bestRating (default 5), worstRating (default 1). The ratings must reflect real reviews from verifiable sources — fake ratings trigger Google's spam policies and can deindex pages.
2026 reality check.
Faked aggregateRating is the #1 schema spam pattern Google's quality team targets. 2024-2025 cracked down on review aggregation manipulation; 2026 cracked down on cross-platform rating inflation. The safe path: only declare aggregateRating that exactly matches your real reviews on verifiable sources. Real 4.7 stars / 12 reviews outperforms fake 5.0 stars / 47 reviews because Google detects the fakery.
Data points
- Schema.org AggregateRating documented at https://schema.org/AggregateRating
- Most commonly attached to Organization, LocalBusiness, Product, Service, CreativeWork, SoftwareApplication
- Faked aggregateRating triggers Google spam policies (can deindex pages)
- Real verifiable ratings outperform fake high ratings due to cross-platform detection
- TDG verified GBP: ratingValue 5.0, reviewCount 7, CID 7763394265835378411
First-hand insight from ThatDeveloperGuy.
ThatDeveloperGuy's Organization schema includes aggregateRating reflecting the real verified Google Business Profile: ratingValue 5.0, reviewCount 7, bestRating 5, worstRating 1. The CID 7763394265835378411 is wired into hasMap so Google can cross-reference. Initial GBP audit revealed the schema previously had a fictional CID (14210859426953573340) — that was corrected May 27, 2026, and Local Pack ranking improved measurably within days.
How TDG approaches it
TDG's aggregateRating reflects the live Google Business Profile (5.0/7 as of May 2026, updated when reviews change). Every page across the network references the same Organization schema via @id, so the rating is consistent. Cross-validated against the verified CID in hasMap. Never inflated, never faked.
Common mistakes.
- Declaring ratings that don't match the verifiable source (GBP, App Store, etc.)
- Using aggregateRating without reviews actually existing somewhere
- Adding aggregateRating to entities that can't have ratings (e.g., generic web pages)
- Not updating aggregateRating as new reviews accumulate (stale rating loses trust signal)
- Forgetting bestRating/worstRating (defaults exist but explicit is safer)
FAQ.
Can I use aggregateRating without an Organization or Product?
Technically yes (it's a CreativeWork property), but practically aggregateRating is most valuable on Organization/LocalBusiness/Product/Service schema where Google can validate against external sources.
Does Google verify my aggregateRating?
Increasingly yes. Google cross-references aggregateRating against verified Google Business Profile (for LocalBusiness), App Store (for Apps), and other authoritative sources. Mismatches lose trust signal.
How often should I update aggregateRating?
Whenever the real rating or count changes. For TDG: any time the Google Business Profile review count or average changes. Stale ratings (months out of date) lose trust signal.
What's the difference between ratingValue and ratingCount vs reviewCount?
ratingCount = total number of ratings (including those without text reviews). reviewCount = number of ratings with text reviews. Use whichever matches your actual data source.
Does aggregateRating affect SEO directly?
Indirectly. Star-rating display improves CTR (visible reward). Local Pack algorithm weights it as a trust signal (hidden reward). AI Overview cites star ratings when discussing businesses (citation extraction).
Maintained by Joseph W. Anady at ThatDeveloperGuy. Back to glossary · Suggest a term