Trust & Ratings Schema

Broken Review &
AggregateRating Schema

Your client has 200 five-star reviews. Google is ignoring every one of them.

Where to find it: Google Rich Results Test > AggregateRating > Errors & Warnings

What It Is

Review schema and AggregateRating schema tell Google the collective review score of a product, service, business, or piece of content — enabling review stars to appear in search results. AggregateRating requires a minimum set of properties: ratingValue (the score), reviewCount or ratingCount (how many reviews), and bestRating (the maximum possible score). When any of these are missing, formatted incorrectly, or contain values outside acceptable ranges, Google suppresses the stars entirely. The content still exists; the visibility upgrade simply doesn't appear.

Why It Matters

Review stars in search results are one of the clearest, most measurable rich result upgrades available. Multiple studies have shown that star ratings increase click-through rate by 15–30% at the same ranking position — without any change in ranking. For service businesses, local businesses, and e-commerce clients, this is a direct revenue impact from a technical fix. The reviews already exist. The customers already left them. Broken schema is the only thing preventing them from appearing in search.

Root Diagnostics

Common Causes

Understanding why this failure occurs is the first step to fixing it permanently.

Missing bestRating Property

AggregateRating schema is present but missing the bestRating property that defines the maximum possible score. Without it, Google can't normalize the ratingValue and often rejects the markup.

ratingValue Out of Range

The ratingValue exceeds the bestRating value, or is formatted as a string rather than a number. Google requires ratingValue to be a numeric value between 1 and bestRating.

Schema Not on the Same Page as Reviews

AggregateRating schema is implemented on a different page than where the actual reviews appear. Google requires the schema to be on the same page as the visible review content it references.

Review Count Too Low or Fabricated

Google has guidelines around review schema: the page must display actual user reviews, the count must be accurate, and the schema must not represent reviews that aren't visible on the page. Fabricated review counts trigger quality suppression.

Interactive Standard Operating Procedure

The Fix Blueprint (Interactive SOP)

Check off each step to monitor your implementation progress live!

Implementation Progress: 0% Completed (0/7)

1. Run the Page Through Rich Results Test

Open Google's Rich Results Test and enter the URL of a page where review stars should appear. Look for AggregateRating in the results. If it shows errors or warnings, click through to see exactly which properties are failing.

2. Confirm All Required Properties Are Present

A valid AggregateRating block requires: @type: AggregateRating, ratingValue (numeric), bestRating (numeric, typically 5), and either reviewCount or ratingCount (numeric integer). Confirm all four are present and correctly formatted.

3. Fix ratingValue and bestRating Format

Both values must be plain numbers — not strings, not formatted with symbols. ratingValue: 4.7 and bestRating: 5 are correct. ratingValue: '4.7/5' or bestRating: 'five' are wrong and will cause errors.

4. Ensure Reviews Are Visible on the Same Page

Google requires that the reviews represented by AggregateRating schema are actually displayed on the same page. If reviews load via JavaScript after the initial page render, confirm Google can see them by testing with the Rich Results Test (which renders JavaScript).

5. Nest AggregateRating Within the Parent Schema

For products, nest AggregateRating inside the Product schema block. For local businesses, nest it inside LocalBusiness. For articles, nest inside Article. Standalone AggregateRating without a parent entity type is incomplete.

6. Add Individual Review Schema for Key Reviews

In addition to AggregateRating, add Review schema for 2–3 individual reviews displayed on the page. Each Review needs: author (Person with name), reviewRating (Rating with ratingValue and bestRating), and reviewBody. This strengthens the review signal.

7. Validate and Monitor in Search Console

After deployment, validate with Rich Results Test. Check Search Console Rich Results report over the following 2–4 weeks. Review stars typically begin appearing in search results within 1–2 weeks of successful validation.

Tools

Google's Rich Results Test
Free (search.google.com/test/rich-results) | Shows exactly which AggregateRating properties are missing or invalid with specific error messages
Google Search Console Rich Results Report
Free | Monitors site-wide review schema status and surfaces new errors as they appear
Schema Markup Validator
Free (validator.schema.org) | Secondary validation to confirm syntax and vocabulary before deployment

Time to Fix

30 minutes

To audit and identify review schema errors

1–2 hours

Fix and validate AggregateRating implementation

Pro Tip

Always nest AggregateRating inside the parent entity — never standalone.

A common schema error is adding an AggregateRating block to the page without nesting it inside the relevant parent schema type. An AggregateRating for a product needs to be inside the Product block. For a local business, inside LocalBusiness. For an article, inside Article. A standalone AggregateRating without a parent entity type is incomplete in Google's eyes and won't generate rich results — even if the ratings data itself is perfectly formatted.

Broken Review & AggregateRating Schema