Should you really remove aggregate ratings from your homepage?

Why does Google prohibit reviews on homepage pages? 

Google's position is based on a simple principle: an aggregate review must be about a specific entity — a product, service, local business. The homepage of a site is not an entity in itself; it is an entry point. 

The Schema.org guidelines state that an aggregateRating must be associated with a typed object: Product, LocalBusiness, Recipe, etc. Plastering stars on a homepage amounts to rating "the site" as a whole, which makes no structural sense. Google aims to prevent webmasters from manipulating SERPs with fake stars that offer no informational value. 

What do the numbers say about actual usage? 

The findings are stark: 23.9% of mobile pages and 23.7% of desktop pages display aggregate ratings. Nearly a quarter of the web ignores or circumvents this rule. There are two possible explanations: either ignorance of the guidelines or a risk/benefit calculation where the gain in CTR compensates for the theoretical risk. 

This data also indicates that Google still massively tolerates this practice — otherwise, we would see waves of manual actions. The question becomes: how long will this tolerance last? Algorithms are evolving, and what passes today may be penalized tomorrow without warning. 

What’s the difference between a homepage and a business page? 

A classic pitfall: confusing a generic homepage with an entity page . If your site is that of a restaurant, hotel, or local agency, the homepage *can* rightfully carry a LocalBusiness Schema with aggregateRating — because it represents the rated physical entity. 

On the other hand, on a multi-product e-commerce site or a media site, displaying generic stars on the homepage has no semantic grounding. The type of site makes all the difference : a bakery can rate its homepage; Amazon cannot. 

• Aggregate ratings must pertain to a typed entity : product, service, local business, recipe, event. 
• 23.9% of sites violate this rule , indicating either a lack of awareness or a calculated risk/gain decision. 
• The current tolerance of Google guarantees nothing for the future — detection algorithms for abuse in rich snippets are continuously improving. 
• A homepage representing a LocalBusiness can legitimately display reviews , unlike a generic portal or a catalog site. 
• The main risk: loss of rich snippets , or even manual action if Google detects blatant manipulation of structured data markup. 

Is this rule strictly enforced by Google? 

Let’s be honest: if 23.9% of sites violate the rule with no visible consequences , it shows that enforcement remains lax. Google communicates a theoretical standard, but automatic filters do not consistently impose penalties. We even observe major sites with homepage stars that have retained their rich snippets for years. 

That said, this tolerance is not a permission. [To be verified] : Google has never published data on the rate of manual actions specifically related to homepage aggregate ratings. The risk remains difficult to quantify — making it an uncomfortable gamble for a corporate site or a pure e-commerce player exposed to it. 

What nuances should be considered based on the type of site? 

The rule carries different weight everywhere. For a single-entity local site (restaurant, medical practice, artisan), the homepage *is* the entity. The LocalBusiness Schema with aggregateRating fits perfectly, and Google explicitly validates it. No compliance issues.

For an e-commerce, SaaS, or media site , the homepage is merely a navigation hub. Adding aggregate stars there equals creating a non-typed object. The gain in CTR may be tempting, but the legal and algorithmic fragility is real. If Google tightens its filters tomorrow, these sites will be the first affected. 

The real issue: confusion between Schema types 

Many webmasters use a Schema Organization on the homepage , then add an aggregateRating. Technically, it passes Schema.org validation — Organization accepts aggregateRating. But semantically, it makes no sense if the Organization is not the rated object (a media does not rate "Le Monde"; it rates articles). 

The nuance: an aggregateRating must reflect reviews *about* the entity , not *issued by* the entity. This confusion fuels 90% of abuses. Google is increasingly detecting this inconsistency through the Knowledge Graph and external citation signals (Trustpilot, Google Reviews, etc.). 

What should you do if you have aggregate reviews on your homepage? 

Your first reflex: identify the type of entity your site represents . If it’s a LocalBusiness, Restaurant, or Hotel, keep your stars — they are legitimate. Just ensure that the Schema is correctly typed and that the reviews correspond to real, verifiable reviews. 

If your site is a portal, a multi-product e-commerce, or a media outlet, remove the aggregateRating from the homepage . Move it to product, service, or article pages where it has a semantic anchor. The gain in rich snippets on these targeted pages will more than compensate for the hypothetical loss on the homepage. 

How can you check the compliance of your markup? 

Run your homepage through the Google Rich Results Test . If the tool detects an aggregateRating, look at what type of object it’s attached to. If it’s an Organization, Product, or generic WebPage without a review context, you’re outside the guidelines.

Supplement with Google Search Console : Enhancements section > Reviews. If errors or warnings appear on the homepage, it’s a signal that Google detects an inconsistency. Don’t rely on the absence of a visible error — filters evolve, and what passes today may be flagged tomorrow. 

What mistakes should you absolutely avoid? 

Don’t fall into the trap of "Schema stuffing" : stacking Organization + Product + aggregateRating on a homepage to maximize rich snippets. Google increasingly penalizes this over-optimization, especially when the data does not correspond to any real entity crawlable elsewhere on the web. 

Also, avoid creating fake reviews or recycling product reviews to aggregate them on your homepage. Google cross-references its data with third-party sources (Trustpilot, Yelp, Google Business Profile) — any blatant inconsistency exposes you to manual action. Consistency between sources is becoming an increasingly scrutinized validation criterion. 

• Audit the Schema of your homepage with Rich Results Test and validate the type of entity 
• Remove any aggregateRating if your site is not a uniquely rated entity (LocalBusiness, Restaurant, Hotel, etc.) 
• Move aggregate reviews to product, service, or local pages where they have a precise semantic anchor 
• Check the consistency between your structured reviews and external sources (Trustpilot, Google Reviews) 
• Monitor Google Search Console's Enhancements section > Reviews for any emerging warnings 
• Document the origin of each aggregated review to justify the legitimacy of the markup in case of inspection