Practical guide · Radian Ranks

Check your Shopify product structured data before adding more

A theme and several apps can all output product markup. The first job is to understand what is already there and whether it accurately describes the page.

1. Inspect a representative product page

Choose an available product and a second product with a different variant or stock setup. View the rendered HTML and identify JSON-LD blocks using application/ld+json. Check for Product, ProductGroup or Offer data without assuming every block is a separate error.

Record which theme, app or custom snippet appears to generate each block. Do not delete app output from a live theme just because the same product name appears twice; first understand whether the data complements or contradicts the other output.

2. Compare the data with the shopping page

The name, product identity, price, currency and availability need to describe what the customer can actually buy. Check a selected variant as well as the initial page state where variants change the offer.

  • Does the currency match the market being viewed?
  • Is the visible stock message consistent with the offer data?
  • Do identifiers belong to this product rather than another variant?
  • Are images accessible and relevant to the product?

Do not invent a GTIN, review count, rating or delivery policy to complete a validator’s suggestion. Some properties are recommended only when the business has that information.

3. Resolve ownership and conflicts

If theme output shows one price and an app shows another, investigate which is stale and how each is generated. Assign one clear owner for the overlapping product facts wherever the implementation allows.

Work on a duplicate theme or equivalent safe environment. A change to a shared snippet can affect the whole catalogue, including sold-out items, bundles and subscription products.

Document the reason for the change and the product types tested. Avoid a site-wide “schema fix” that only works for a single simple product.

4. Use validators for the questions they can answer

Google’s Rich Results Test checks supported search features and their technical requirements. A general schema validator can inspect broader schema vocabulary. Neither tool proves the facts are true or guarantees a search appearance.

Run the appropriate tests on the rendered output and again on the public URL after release. Review errors separately from recommendations, then compare the markup with the visible page.

5. Make checks part of releases

Recheck representative products after theme updates, app changes or market configuration changes. Watch Search Console reports where available and investigate the affected template before applying a bulk change.

Structured data should reinforce accurate product information. Useful product pages, a navigable catalogue and reliable market settings still need their own attention; markup is one part of that system.

Sources and further reading

Use the platform documentation alongside your store’s actual setup. This guide does not assume that every theme or market configuration behaves identically.

Need help applying the checks? Request a free SEO review or explore our UK Shopify SEO service.