Should you really limit the Review markup to the main item on the page?

Why does Google emphasize the concept of the main item?

The historical problem is that some websites were marking up everything and anything to display stars in search results. A site selling TVs displayed ratings for the main TV, but also for HDMI accessories, warranties, and promotional products in the sidebar — all marked as Review.

Google has therefore tightened the rules. The main item is what the user primarily comes to consult when landing on the page. If your page talks about a MacBook Pro 16", the MacBook is the main item. Not the USB-C adapter mentioned at the bottom of the page. Not the comparison with a Dell XPS in a sidebar table.

What exactly defines this main item?

It's largely a matter of visual hierarchy and dominant content. The H1 title of your page, the product or service described in the first 300 words, the item covered by the majority of user reviews — that's what matters.

If you have to ask yourself, 'Is this item really the main one?', the answer is probably no. A product page = one marked product. An author page = the marked author. A comparison page of 5 products? This is where it becomes complicated, and Google has never been extremely clear on the case of multi-entity comparisons.

What are the consequences of not following this rule?

Your markup will simply be ignored by Google. Stars will not appear in the SERPs. Worse still, if Google detects a pattern of abuse — for instance, dozens of pages with Review tags on secondary items — you risk facing a manual action on the entire site.

The Search Console often displays warnings ‘Excluded content: does not comply with guidelines’ when the markup does not match the main item. Some sites have lost their rich snippets overnight after a change in Google’s policy.

• One Review tag per page: stick to the main entity to avoid any ambiguity.
• Visual hierarchy: the marked item must be clearly dominant in the HTML and editorial structure.
• Title/content consistency: if your H1 talks about X, the Review markup must focus on X, not on Y mentioned in passing.
• Avoid sidebar reviews: marking reviews of related or suggested products in the margins is a common mistake.
• Test in Search Console: the structured data testing tool highlights consistency issues, so use it regularly.

Is this statement aligned with what we observe in the field?

Yes, but with a significant nuance: Google applies this rule inconsistently. We still see major sites (Amazon, Trustpilot, some comparators) displaying stars for secondary entities without apparent penalties. Either they are benefiting from algorithmic tolerance due to their authority, or Google has not detected the infraction — it’s hard to say.

What is clear is that for a 'normal' site without massive authority, trying to mark up multiple entities per page is a risky gamble. Smaller sites get penalized faster than larger ones. Unfair? Perhaps, but it is the reality observed.

When does this rule become vague or inapplicable?

The comparison pages, for example. If you produce a guide like 'Best Smartphones' with 10 models, each having its rating, which one is the main item? Google does not provide a clear answer.

Some SEOs mark only the #1 ranked model, while others create a dedicated page for each product to avoid ambiguity. [To be verified]: there is no official Google documentation on the case of multi-entity comparisons — it’s a black hole.

Should we systematically avoid multiple Review tags per page?

In practice, yes. Even though technically Schema.org allows multiple Review type objects, Google has chosen to restrict display to cases where the item is unique and obvious. Multiplying tags increases the risk of silent rejection.

There is one exception: review aggregators like Trustpilot or G2 that display hundreds of reviews on a company page. There, the main item is clear (the company), and the multiple reviews are an attribute of that unique item. But for an average e-commerce site, this logic does not hold.

What should you concretely do to comply?

Audit your pages using Google’s structured data testing tool. Look for pages where multiple Review tags coexist — they are probably in violation. Prioritize high-traffic pages, as those are where losing stars hits the hardest.

Then, reorganize your markup: one page = one main item = one Review tag. If you want to mark multiple products, create dedicated pages for each. This also enhances your internal linking and your ability to rank on specific long-tail terms.

What technical mistakes should you absolutely avoid?

Never mark up elements that are not directly visible and detailed on the page. If your sidebar widget displays 'Product of the Day' with a rating, but the main content is about another product, do not mark up the widget. Google considers this spam for rich snippets.

Another pitfall: inconsistent aggregated ratings. If your AggregateRating markup indicates 4.5/5 based on 200 reviews, but only 5 reviews are visible on the page, Google may reject the markup for inconsistency. The marked reviews must be accessible to the user, not hidden behind a tab or login.

How can I verify that my site complies with this rule?

Use a crawler like Screaming Frog or Oncrawl to extract all Review tags from your site. Cross-reference this list with your H1s and meta descriptions — if the marked item doesn’t match the main title, you have a problem.

The Search Console also displays alerts in the ‘Improvements’ section under ‘Reviews’. If you see 'Excluded content' warnings, it's often related to a mismatch between the main item and the marked item. Treat these alerts as priorities.

• Limit yourself to one Review tag per page, targeting the dominant content item.
• Ensure that the displayed reviews match the marked reviews — no ghost ratings.
• Remove Review tags from sidebars, footers, or secondary widgets — only the main content should be marked.
• Test your pages in Search Console before publishing to avoid unpleasant surprises after indexing.
• If you manage a multi-product site, prioritize dedicated pages per entity over listings with multiple markup.
• Document your markup choices in an internal guideline to prevent your editorial team from reintroducing errors.