A site can have genuinely happy customers and zero stars in Google. The reason is almost always the same: Review and AggregateRating schema is either missing, or it's attached to the wrong entity type. This guide covers the required properties, the mistake that disqualifies most attempts (the self-serving badge), and how to actually verify it's working before you conclude "schema doesn't move the needle."
What Review and AggregateRating Actually Do
The two types work together but measure different things. AggregateRating carries the average score compiled from multiple reviews (a single value plus a count). Review carries one individual review: author, rating, date, text. Neither works alone — both need to be nested inside the entity being rated (most often Product, but also LocalBusiness, Recipe, Course, SoftwareApplication, Event, Book, Movie...).
Direct answer: if you want stars in Google results, AggregateRating is the minimum requirement. Review alone, without an aggregated average, doesn't reliably trigger the star display across every eligible type.
The Eligible Types: A Closed List
Google only shows stars for a specific, closed list of schema.org types. Step outside that list, and the markup is valid but invisible in the SERP.
| Eligible type | Typical use case |
|---|---|
Product | E-commerce product pages |
LocalBusiness | Physical location (restaurant, shop) |
SoftwareApplication | App, plugin, SaaS tool |
Recipe | Cooking recipes |
Course | Online courses |
Book, Movie, MusicRecording | Editorial and media content |
Event | Events, ticketing |
A generic B2B service page that isn't one of these types will never get stars, no matter how technically correct the markup is. That's the first thing to check before spending time on implementation.
The Required Properties — And What Makes the Whole Thing Disappear
Google is strict on this exact point: a missing required property doesn't degrade the rich result, it removes it entirely.
| Property | On | Required |
|---|---|---|
ratingValue | AggregateRating | Yes |
ratingCount or reviewCount | AggregateRating | Yes (at least one) |
itemReviewed (or parent name) | AggregateRating / Review | Yes |
author | Review | Yes |
reviewRating | Review | Yes |
For a Product, Google also requires a valid Offer (price, currency, availability) alongside the rating to show the full product rich result. A page with a flawless AggregateRating but a broken or missing Offer can lose the entire rich result, not just the stars.
The Mistake That Disqualifies Most Attempts: The Self-Serving Badge
This is the part Google's own documentation states without hedging: if the entity being reviewed controls the reviews about itself, pages using LocalBusiness or any other Organization type are ineligible for the star review feature. In practice: a company displaying "4.8/5 based on our customer reviews" on its homepage, with an AggregateRating nested inside its Organization, will never show stars. Google ignores that markup on principle, not because of a bug.
The nuance that trips up most people: it's not against the rules to display your own customer reviews on your homepage. It's the Organization/LocalBusiness self-rated markup specifically that's ineligible. The fix: mark up reviews on individual Product pages (each product rated separately) rather than on your company's overall entity. A SaaS tool with reviews per feature or per plan, marked up as SoftwareApplication, stays eligible even if the vendor hosts those reviews itself.
Other causes of penalty explicitly listed by Google: undisclosed incentivized reviews, fabricated reviews, editorial curation of local ratings, and aggregating reviews pulled from other sites without authorization. A detected violation triggers a manual action that removes stars site-wide, not just from the offending page.
How to Actually Implement It
Here's the minimal JSON-LD structure for a product with an aggregate rating:
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Product name",
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.6",
"reviewCount": "89"
},
"offers": {
"@type": "Offer",
"price": "49.00",
"priceCurrency": "EUR",
"availability": "https://schema.org/InStock"
}
}
Three things to watch during implementation:
- The rating needs to be visible to users on the page, not just in the JSON-LD. A
ratingValueof 4.6 that doesn't appear anywhere visually on the product page reads as manipulation to Google. - The review count needs to be verifiable, not inflated. A counter that climbs without matching visible reviews attached draws attention during manual review.
- Practical minimum threshold: roughly 5 genuine reviews. Below that, the average carries little statistical weight, and the risk of manual suppression outweighs the visibility gain.
How to Verify It's Actually Working
Three checks before you consider this done:
- Google's Rich Results Test on the URL in question: confirms the markup is valid and eligible, not just present.
- Search for the entity in the SERP from a computer not signed into your Google account, in private browsing: stars don't display for 100% of queries even with perfect markup — Google decides case by case.
- Track it in Search Console (Enhancements > Review snippets report) to catch errors and warnings site-wide, not page by page.
When This Isn't the Priority Fight
If you have fewer than 5 genuine reviews per product, this isn't worth the effort yet: spend that time collecting more reviews before marking up anything. For a B2B SaaS with very few public reviews but a strong presence on G2 or Capterra, third-party reviews carry different weight for AI visibility than on-site Review schema: the two levers don't replace each other, but if you have to prioritize with limited time, a strong presence on high-authority third-party review platforms can move the GEO needle more than an AggregateRating with 3 reviews on your own product page.
Key Takeaways
AggregateRatingcarries the average score,Reviewcarries the individual review: both nest inside the rated entity, never standalone- Only a closed list of types (Product, LocalBusiness, SoftwareApplication, Recipe...) is eligible for stars in Google
- A single missing required property removes the entire rich result, not just the affected field
- The self-serving badge (an Organization/LocalBusiness rating its own overall business) is the top cause of ineligibility — the fix is marking up at the Product level, not the company level
- Roughly 5 genuine reviews is the practical threshold below which it's not worth the effort yet
FAQ
What's the minimum number of reviews needed to use AggregateRating?
Google's documentation doesn't set a hard numeric minimum, but below roughly 5 genuine reviews, the average carries little statistical weight and the risk-to-benefit ratio turns unfavorable. It's better to wait for a representative volume.
Why aren't my stars showing even though the markup is valid?
Passing the Rich Results Test is necessary but not sufficient. Google decides case by case whether to display the rich result, and can withhold it if the review volume looks too low, the entity isn't on the eligible list, or the page has been hit by a manual action.
Can I display my customer reviews on my homepage?
Yes, displaying them isn't against the rules. It's the schema markup on a self-rated Organization or LocalBusiness that's ineligible for stars. Shift the markup to individual Product entities if you want to stay eligible.
Does Review schema also help AI visibility (GEO)?
Indirectly: an average rating with a solid review count is a trust signal that answer engines can fold into a synthesis. But the most documented lever for AI citation remains presence on high-authority third-party review platforms (G2, Capterra, Trustpilot), not on-site schema alone.
A misplaced AggregateRating (on Organization instead of Product) is one of the most common mistakes we find auditing e-commerce and SaaS sites. Run your free SeAudit audit to check where your markup stands, or upgrade to the full report for a page-by-page prioritized fix plan.