Should structured data really be limited to the main topic of each page?

What does ‘specific to the main topic’ actually mean?

Google draws a clear line between the main content of a page and its peripheral elements. The main topic corresponds to the purpose of the URL: if it is a product page, the structured data should describe that specific product. If it is an article, it should relate to that article.

The engine rejects generic structured data overlaid on the entire site. A typical example: an Organization schema with aggregated reviews present on every page of the site, while these reviews pertain to the company, not the content of each page. Google views this as off-topic markup.

Why this restriction on rating tags?

Star-rich snippets attract clicks. Some sites attempted to display them everywhere by marking their pages with generic AggregateRating, even when the page featured nothing evaluable. An “About” page with 5 stars? Contact page with a rating? Google sees this as manipulation.

The rule is simple: a rating only appears where a user can view the corresponding reviews. Product page with reviews? OK. Homepage with the overall rating of the company without the option to read detailed reviews? Denied.

How does Google detect abuses?

The crawl compares structured markup to visible content. If the schema announces a product but the page displays a blog article, the inconsistency is glaring. Algorithms check that the declared data matches the elements present in the DOM.

Manual actions also target sites that abuse rich snippets. When stars appear on irrelevant pages, the site risks a penalty that removes all enriched snippets for months.

• Structured data must match the main content of each individual URL
• Ratings apply only to evaluable entities on that specific page
• No generic site-wide markup if content varies from page to page
• Google automatically compares schema and visible content to detect inconsistencies
• Violations can trigger manual actions removing rich snippets

Is this statement consistent with real-world observations?

Absolutely. SEOs who attempted to generalize rich snippets have been caught. Documented cases show that Google removes stars on pages where the markup does not match the main content, even if technically the schema is valid.

A gray area remains: the definition of the ‘main topic’ is subjective. On an e-commerce category page listing 30 products, can each product be marked individually? Google says yes. But can you also mark the category itself with a breadcrumb and a CollectionPage schema? Practice shows yes, as long as each type of schema corresponds to a distinct element of the content.

What nuances does Google overlook here?

Mueller does not clarify the case of legitimate secondary content. A product page can contain a related blog article, a FAQ, recommended products. Can these secondary sections be marked? The unofficial answer is yes, if they are substantial and provide value.

The other gray area concerns legitimate site-wide structured data: Organization, WebSite with SearchAction, BreadcrumbList. These can appear on all pages without issue because they describe the site as a whole, not the content of the page. Google tolerates them as long as they do not attempt to generate abusive rich snippets.

In what cases does this rule pose a problem?

Multi-section sites face difficult choices. A page can legitimately cover multiple topics: an article with integrated products, a landing page mixing testimonials and offers. Should you choose a single main schema or can you combine several?

Practice shows that Google accepts complementary schemas as long as they all describe visible elements. However, as soon as a rating appears, it must correspond to an evaluable element on that specific page. [To verify]: Google has never published a numerical limit on the number of different schemas per page, but experience suggests that beyond 3-4 distinct types, the risk of dilution increases.

What steps should you take on an existing site?

Conduct a complete audit of structured data. Google Search Console shows detected errors but does not capture all inconsistencies. Use the rich results test page by page to verify that each schema corresponds to the visible content.

Identify site-wide duplicate tags that have no place everywhere. An AggregateRating stuck on all pages via the template? Remove it and keep it only on pages where reviews are actually displayed. A generic Product schema on non-product pages? Clean it up.

What mistakes should absolutely be avoided?

Never mark an element invisible to the user. If your page does not show detailed reviews, no Review tag. Google detects these attempts and can penalize the entire domain.

Avoid ratings on non-evaluable entities. Your contact page shouldn’t display 5 stars. Neither should your T&Cs page. Even if you could technically mark a ‘clarity rating of the T&Cs’, it won’t pass the common sense test.

Be cautious of contradictory multiple schemas. A page cannot simultaneously be an Article and a Product if the main content is clearly one or the other. Choose the main type and optionally add secondary schemas for complementary sections.

How to quickly check for compliance?

Crawl your site with Screaming Frog or Oncrawl while enabling structured data extraction. Export the list of pages with ratings, then manually check a representative sample. If you find stars on pages where no reviews appear, you have a problem.

Test the strategic pages one by one in the rich results testing tool from Google. The preview shows how the engine interprets your schemas. If the preview shows elements absent from the visible content, it's a red flag.

• Audit all pages with structured data via GSC and third-party tools
• Remove AggregateRating and Review tags from pages without visible reviews
• Check that each schema corresponds to the main content of its page
• Limit site-wide schemas to legitimate types (Organization, WebSite, BreadcrumbList)
• Test a sample of pages in the Google tool to detect inconsistencies
• Monitor GSC to spot new errors after modifications