A theme change broke our product structured data

A theme release can damage product markup while the page still looks fine to a shopper.

Typical symptoms

• Rich-result or merchant diagnostics change after deployment.
• Visible product details remain correct while JSON-LD changes.
• Price, availability, or variant markup no longer matches the page.
• More than one app or theme extension emits a Product entity.

What to capture

Save the rendered HTML, expected product and variant facts, parsed graph, deployment diff, app and theme-extension changes, and the relevant external diagnostic.

Don't assume

Passing a parser only proves that the syntax can be read. It does not show that the graph describes the product on the page or that a search engine will display it.

Steps

1. Parse every Product, ProductGroup, and Offer entity.
2. Compare each field with what the shopper sees.
3. Find duplicate entities, missing links, and incorrect variants.
4. Trace every entity to its theme or app source.
5. Fix the template or extension that owns it.
6. Test the rendered page, then check the external diagnostic.

Done when

• One coherent graph describes the visible product.
• Offer data matches the active variant and market.
• Reviews and ratings are visible and supported.
• Search display is described as a search-engine decision, not an assured result.