Is it true that product markup should only be applied to individual pages?

Why does Google refuse product markup on category pages?

The reason concerns the attribution of trust signals. When you mark up a category page with schema.org/Product, Google cannot determine which specific item corresponds to the aggregated reviews. Does a red sweater at €49 and a blue jeans at €89 share the same 4.5 stars? It's impossible to tell.

Rich results display ratings, prices, and availability directly in the SERP. If this data originates from a category aggregating 50 items, the user clicks expecting to find a specific product matching the displayed information. This leads to user disappointment, causing a high bounce rate, which is a negative signal for ranking.

What is Google's exact definition of a product page?

Google considers any URL presenting a uniquely identifiable item by an SKU, model name, or specific variant as a product page. An iPhone 15 Pro 256GB Titanium Blue is a distinct product from an iPhone 15 Pro 512GB Natural Titanium, even though they share the same parent listing.

Pages listing multiple products without a clear main focus do not fit this definition. This includes classic categories, but also pages of internal search, dynamic filters, or thematic landing pages aggregating multiple references.

Does this rule apply to variants and options?

The gray area lies with parent pages with variant selectors. A T-shirt page with a drop-down menu (sizes, colors) raises the question: is it a unique product with variations or multiple products on the same URL?

Google tolerates product markup if a default variant is clearly defined and the structured data reflects that specific variant. Does color change via JavaScript? The markup must update dynamically to remain compliant. Otherwise, create distinct URLs for each significant variant.

• Only mark up pages presenting a uniquely identifiable product (SKU, model, specific variant)
• Absolutely avoid product markup on categories, search pages, filters, or multiple listings
• For variants: distinct URLs or dynamic markup updates are mandatory
• Reviews and ratings must correspond exactly to the marked product, not to an aggregation of different references
• Test your structured data with the Rich Results Test tool to detect ambiguities

Does this position truly reflect observed real-world practices?

Overall, the directive aligns with what has been observed for years. Sites that massively markup their categories with schema.org/Product do not obtain rich snippets for those pages. Google simply ignores structured data deemed inappropriate.

However, the wording remains vague on a critical point: hybrid pages. A mobile plans sales site sometimes displays a comparison with 3-4 main offers on a commercial landing page. Technically, this is not a classic category, but it is also not a unique product sheet. Google gives no numerical indication of the acceptable threshold. [To be verified] based on your own tests.

What are the real risks of incorrect markup?

First level: no rich snippets. Your competitors display stars and prices in the SERP, while you remain invisible with a standard text snippet. This results in a direct loss of CTR, quantifiable between 15% and 40% depending on the sectors based on our client observations.

Second level, less documented but real: manual actions for spam structured data. Rare, but they exist. Google may consider that a site attempting to manipulate result displays through abusive markup deserves a penalty. This has been applied to sites marking thousands of category pages with aggregated fake reviews.

In what cases can this rule be nuanced?

Marketplaces pose a specific problem. An Amazon or eBay page sometimes lists a unique product sold by multiple vendors. Technically, it's a product page (same SKU, same item), but with multiple offers. Google accepts product markup if the item remains unique, even with several sellers.

Another observable exception: SEA landing pages created for Google Shopping campaigns. Some sites create hybrid landing pages presenting 2-3 major variations of a product to maximize conversions. The markup remains acceptable if one main variant visually dominates and the structured data only pertains to that one. But you're playing with fire.

How can you quickly audit and correct existing markup?

Start by crawling your site with Screaming Frog or Oncrawl by enabling structured data extraction. Filter all pages containing schema.org/Product and cross-reference them with your URL taxonomy. Any category, filter, or multiple listing URL must show up as an anomaly.

Then use Google Search Console, under Search Appearance > Structured Data. The errors “Multiple products detected” or “Non-specific product” often indicate markup on a category. Prioritize corrections for pages generating significant organic traffic.

What technical implementation should be preferred for large-scale e-commerce?

On a catalog of 10,000+ products, dynamic JSON-LD markup on the server-side remains the most maintainable solution. Your CMS or e-commerce platform should automatically generate the script block from product data (price, stock, verified reviews).

Avoid generic WordPress plugins that markup everything by default without distinction. Prefer a strict conditional logic: if page_type == 'single_product' AND SKU exists AND stock > 0, then generate markup. Otherwise, do nothing. Tools like WooCommerce or Shopify offer fine-tuning options, enable them.

What should I do if my architecture does not allow distinct product URLs?

Some legacy sites or single-page JavaScript applications (SPA) load everything dynamically without changing the URL. Technically, you can implement client-side dynamic markup updates during variant changes, but this is risky.

Google may only crawl the initial state, without executing all your JS events. The clean solution is to refactor the URL architecture to isolate each product. If impossible in the short term, use parameter URLs (example.com/product?sku=12345) and ensure that Googlebot crawls them as distinct pages via robots.txt and sitemaps.

• Audit all your pages with schema.org/Product through a crawler and Search Console
• Remove category markup, filters, searches, and multiple listings without delay
• Test each product page with Rich Results Test to validate potential display in SERP
• Implement strict conditional logic in your CMS to avoid future regressions
• Create distinct URLs for each significant variant (color, critical size) if your market demands it
• Monitor the evolution of rich impressions in Search Console after corrections to measure impact