Skip to content
Beseam
Commerce Fieldbook
Fieldbook/Storefront operations

Product schema recovery after a theme change

Repair product markup after a theme, app, or storefront deployment changes the rendered graph.

Who does this: A developer or theme-agency sequence. Your job is to confirm it's assigned after a release and sign off on Done when.

Reviewed 2026-07-25

This sequence applies when structured-data diagnostics regress after a storefront release.

Capture before editing

Save the rendered HTML, parser output, visible product facts, active variant, market, and a previous known-good page when one is available.

Steps

  1. List every Product, ProductGroup, and Offer entity.
  2. Find the theme, app, or extension that emits each one.
  3. Compare the graph with the product facts shown to the shopper.
  4. Remove or consolidate duplicate emitters.
  5. Repair variant and offer relationships.
  6. Test the rendered HTML in preview.
  7. Deploy through the normal review path.
  8. Check the live page and the external diagnostic again.

Related pages

Keep working on this issue

skill

Product structured-data validation

Check whether the rendered page and its JSON-LD describe the same product, variant, offer, reviews, and merchant terms.

Open page

Open standard

Schema.org

The shared structured-data vocabulary used to describe products, offers, organizations, reviews, and web entities.

Open standard

JSON-LD 1.1

The W3C recommendation for expressing linked data in JSON, commonly used to publish product structured data.

Primary reference

Google Product structured-data documentation

Google's requirements and guidance for Product snippets and merchant-listing structured data in Search.