AI Visibility

Review and AggregateRating Schema: JSON-LD for Stars, Ratings, and AI Trust Signals

By Reviewed by Hawrry Bhattarai
August 30, 2026 7 min read
Contents
TL;DR — the short answer

Complete guide to Review and AggregateRating schema JSON-LD. Covers implementation for products, services, and local businesses, rich result requirements, and AI trust signals.

7 min read · AI Visibility · Last updated July 2026

Quick answer: AggregateRating schema provides structured review data (star rating and review count) that enables star-rating rich results in Google and signals trustworthiness to AI systems. Review schema adds individual reviewer details. Both must represent real, on-page reviews to comply with Google’s guidelines.

Introduction

Star ratings in search results are one of the highest CTR-boosting rich result types — studies show 15-25% CTR improvement for results displaying star ratings. Beyond search results, AI systems use rating data when making recommendations.

When ChatGPT recommends “the best CRM for small businesses,” it is, in part, drawing on aggregated quality signals — including review data that has been indexed from the web. Structured rating data makes your quality signals machine-readable and citation-ready.

What you’ll learn:
– The difference between Review and AggregateRating schema
– When and where each type is appropriate
– Google’s compliance requirements for review schema
– AI recommendation signals from rating data
– Implementation patterns for products, services, and local businesses

Table of Contents

  1. Review vs. AggregateRating: Key Differences
  2. AggregateRating Schema Structure
  3. Review Schema Structure
  4. Where to Use Review Schema
  5. Google’s Review Schema Requirements
  6. AI Trust Signals from Rating Data
  7. Implementation Examples
  8. Frequently Asked Questions

Review vs. AggregateRating: Key Differences

AggregateRating: Represents the combined average rating across all reviews.
– Shows as star rating + review count in search results
– Required for rich result star display
– Can stand alone without individual Review schema

Review: Represents a single individual review.
– Provides reviewer name, rating, and review text
– Used alongside AggregateRating for richer data
– Google may use individual reviews for “review snippet” rich results

Typical implementation: AggregateRating on product/service pages; individual Review objects nested within the parent entity or on dedicated review pages.

AggregateRating Schema Structure

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "AI Visibility Audit by Ignited Nepal",
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.9",
    "bestRating": "5",
    "worstRating": "1",
    "reviewCount": "63",
    "ratingCount": "71"
  }
}

Property explanations:
– ratingValue — the average rating (decimal, e.g. “4.9”)
– bestRating — maximum rating scale value (typically “5”)
– worstRating — minimum rating scale value (typically “1”)
– reviewCount — number of written reviews
– ratingCount — total number of ratings (including those without reviews)

When reviewCount differs from ratingCount: Some users rate without writing a review. ratingCount includes all ratings; reviewCount includes only those with written text. Both can be included.

Review Schema Structure

Individual reviews can be nested within the parent entity:

{
  "@type": "Review",
  "reviewRating": {
    "@type": "Rating",
    "ratingValue": "5",
    "bestRating": "5"
  },
  "name": "Best investment in our marketing stack",
  "reviewBody": "The AI Visibility Audit identified 14 specific gaps in our entity and schema setup. Three months after fixing them, we're being cited in 70% of relevant ChatGPT responses. ROI is clear.",
  "datePublished": "2026-04-15",
  "author": {
    "@type": "Person",
    "name": "Marcus Webb"
  }
}

Include review as an array within your Product, LocalBusiness, or Service entity:

{
  "@type": "LocalBusiness",
  "name": "Ignited Nepal",
  "aggregateRating": {...},
  "review": [
    {first review object},
    {second review object}
  ]
}

Where to Use Review Schema

Product pages: Product schema with AggregateRating for star-rating rich results on e-commerce product pages.

Service pages: Service or Product schema with AggregateRating for agency, SaaS, and professional service pages.

LocalBusiness pages: LocalBusiness schema with AggregateRating for location-based businesses (restaurants, clinics, salons).

Recipe content: Recipe schema includes AggregateRating for starred cooking results.

App listings: SoftwareApplication schema includes AggregateRating.

Do NOT use on:
– Category pages (reviews must be for a specific entity)
– Blog posts (unless the post is a product review)
– Home pages without a specific product or service entity

Google’s Review Schema Requirements

Google’s review schema guidelines have specific compliance rules:

1. Reviews must be on the page: The reviews described in schema must be visible and readable by users on the same page. Hidden or off-page reviews violate guidelines.

2. No self-serving review schema: Reviews cannot be written by the business itself unless clearly disclosed as first-party reviews. Testimonials from clients qualify if attributed properly.

3. No markup on pages without reviews: If your page does not display reviews, do not add AggregateRating schema. This is explicitly prohibited.

4. Rating scale must match display: If you display reviews on a 5-star scale, your schema must use bestRating: “5”. Mismatches cause validation failures.

5. Accurate counts: reviewCount must match the actual number of reviews displayed. Inflated counts are a spam signal.

Penalties for violations: Google can demote rich result eligibility for pages that violate review schema guidelines. The consequences are temporary rich result loss, not organic ranking penalties.

AI Trust Signals from Rating Data

Beyond rich results, rating data influences AI recommendation behavior in two ways:

Direct structured data: When AI systems index your structured product/service pages, the ratingValue and reviewCount from schema are stored as product attributes. For comparison queries, products with high structured ratings are cited more frequently.

Third-party review sites: AI systems also draw from review platform content (Google Reviews, Trustpilot, G2, Capterra). Maintaining high ratings on these platforms supplements your schema-based signals.

The compound effect: A product page with AggregateRating schema showing 4.9 stars from 63 reviews, combined with strong Google Business Profile ratings and Trustpilot presence, creates multiple reinforcing signals across the sources AI systems retrieve from.

For “best X” queries: AI systems recommending “the best accounting software for freelancers” consistently weight both organic quality signals and structured rating data. High rating schema on your service pages is a direct input to this recommendation process.

Implementation Examples

SaaS product with plan variants:

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Ignited Nepal AEO Toolkit",
  "applicationCategory": "BusinessApplication",
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.8",
    "reviewCount": "142",
    "bestRating": "5"
  },
  "offers": {
    "@type": "Offer",
    "price": "97",
    "priceCurrency": "USD"
  }
}

Local restaurant:

{
  "@context": "https://schema.org",
  "@type": "Restaurant",
  "name": "The Kathmandu Kitchen",
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.7",
    "reviewCount": "312",
    "bestRating": "5"
  },
  "servesCuisine": "Nepali",
  "priceRange": "$$"
}

Frequently Asked Questions

Q: Can I show AggregateRating on my homepage?
A: Only if your homepage represents a specific product, service, or business entity AND the reviews are displayed on the homepage. For most businesses, AggregateRating belongs on specific product/service pages, not generic homepages.

Q: What happens if my reviews drop below 4 stars? Should I remove the schema?
A: Keep the schema but keep it accurate. Removing schema to hide a low rating will not improve rankings and violates the principle of accurate schema representation. Instead, focus on improving the actual service quality and review score.

Q: Does Google require a minimum number of reviews for rich results?
A: Google does not publish a hard minimum, but single reviews rarely trigger rich results. In practice, 5+ reviews appear to be the informal threshold for rich result display, with more reviews improving display frequency.

Conclusion

AggregateRating schema is one of the most visible structured data wins available — star ratings in search results improve CTR significantly and provide direct AI recommendation signals. Implement it wherever you have genuine, on-page reviews, keep the data accurate, and ensure your third-party review platform ratings are maintained.

Get AI-Ready with Ignited Nepal

We implement complete review schema strategies alongside your full entity and AI visibility infrastructure.

→ Request an AI Visibility Audit

Written by the Ignited Nepal AI Visibility team. ignitednepal.com

NR

Article by

Niraj Raut

Head of Search at Ignited Nepal. Drove 340% organic traffic growth for EzyDog (Australia), 4× revenue for The Turf Man (Australia), and 120% month-on-month traffic growth for ThemeGrill (Nepal). Keynote speaker at WordCamp Nepal 2023 and verified WordPress.org open-source contributor.