Product markup conflicts with a declared product list
structured_data_product_markup_on_list_page · Review item
Review whether Product/Offer describes this URL or an individual list item.
Severity: Medium. Review item about conflicting declared page roles; not a penalty or eligibility verdict.
Why it matters
Google recommends product-focused pages, including variants; a declaration describing a whole collection deserves review.
What to do
- Review whether Product/Offer describes this URL or an individual list item.
- Correct the conflicting page-level declaration while retaining accurate entities for individual products.
- Keep variant/detail pages and related-product recommendations where they accurately describe the page; recheck through another full audit.
When to leave it as it is: Keep markup that accurately describes the page and its entities; this check does not require removing valid item-level product markup.
What we read
The original complete HTML5 tree and bound three-format structured graph from the current successful HTML response.
A current-page CollectionPage with one main ItemList, source-bound Product destinations, a current-page Product/Offer claim, and at least three distinct matching destinations with one local price each in the same non-navigation ul/ol.
Original declarations, links, local prices and exact byte ranges are retained as evidence.
Example & evidence
Illustrative declaration correction; item-level products are retained.
CollectionPage(mainEntity=ItemList[A,B,C]); Product(url=current page)CollectionPage(mainEntity=ItemList[A,B,C]); Product(url=A), Product(url=B), Product(url=C)Confirm & check again
Check for yourself: Compare the original captured declarations and static element byte ranges with the current page.
Check again: Full audit — Run another full audit of the same URL. The shared evaluator and lifecycle compare only sufficiently covered results; unknown or missing coverage never proves a fix.
Limits & sources
Three priced links or pagination alone never establish a category page. Product detail with recommendations and Product declarations only for list items do not fire.
ProductGroup/variant/bundle relations, ambiguous mainEntity, untyped or foreign markup, partial captures and missing link-price association remain unknown, never fixed.
The static price heuristic recognizes dollar, euro and pound symbol patterns. Other layouts/formats are not inferred. This is a conservative subset, not general page-type detection.
No rendered DOM, product purchasability, Google rich-result eligibility or deception is established.
Confidence: Medium Medium for the recorded static declarations and supported page-role conflict. Rendering and Google eligibility are not established.
Sources
- Google Search Central, Merchant listing structured data — Product rich results focus on one product or its variants; the rule conservatively reviews an explicit collection/current-product role conflict. Checked 5 October 2026.
Editorial review: 2 November 2026