Product structured-data validation

Run this validation after a theme change, app installation, catalog migration, or diagnostic warning about product markup.

Inputs

• Rendered product-page URL
• Expected product and variant data
• Market
• Relevant search or merchant diagnostic
• Recent theme or app changes, when known

Output

• Parsed entity graph
• Comparison of visible and structured values
• Duplicate, missing, and conflicting fields
• Likely template or integration owner
• Retest checklist

Steps

1. Capture rendered HTML, not only the source template.
2. Parse every Product, ProductGroup, Offer, Review, and merchant entity.
3. Compare the graph with the visible page.
4. Check product identity, variant, price, currency, availability, and URL links.
5. Trace duplicate or conflicting entities to their source.
6. Fix the theme, app, or integration that owns the output.
7. Test the rendered page, then rerun the external diagnostic.

Checks

• Product and variant identity
• Offer price, currency, availability, and URL
• ProductGroup relationships
• Reviews and aggregate ratings
• Merchant, shipping, and return-policy links
• Duplicate or contradictory entities

Limits

Valid markup can still be ineligible for display. It also must not state facts or reviews that shoppers cannot see on the page.