Shopify Product JSON-LD: what to check and why

Inspect what the live product page renders

Start with the live URL, not a theme setting or an app dashboard. Open the rendered page source and search for scripts with type="application/ld+json". Find the entity whose @type is Product orProductGroup.

Shopify's Liquid structured_data filter can generate a Product for an item without variants and a ProductGroup for an item with variants. Themes and apps can also output markup. If more than one system describes the same product, compare the entities for contradictory prices, availability, identifiers, or URLs before adding another schema block.

Match product identity to the visible page

For Google's current merchant-listing eligibility, the core Product structure includes a name and image plus a nested Offer with the active price and matching currency. Other consumers and result types have their own requirements, so always use the current documentation for the experience you target.

Requirements differ between product snippets, merchant listings, and other consumers of Schema.org. Treat this as an accuracy checklist, then validate against the current requirements for the experience you want.

Make every Offer agree with the buy box

Offer data changes faster than most product copy. Compare the markup against the page after market selection, variant selection, discounts, and inventory changes.

For pages offered in multiple currencies, follow the target consumer's current URL and currency guidance. Google currently recommends a distinct URL per currency for product rich results. Do not assume client-side currency conversion updates the JSON-LD correctly.

Represent variants as related offers, not one blurred item

When color, size, material, or another option changes what can be bought, the structured data should preserve that relationship. Google's current variant guidance uses a ProductGroup with productGroupID, variesBy, and hasVariant, or variant Products that point back through isVariantOf.

• Give the group a stable identity and list the properties that actually vary, such as color or size.
• Give each represented variant its own relevant image, identifier, option values, and Offer state.
• Keep variant URLs distinct and resolvable when the storefront supports stable variant selection in the URL.
• Confirm unavailable variants are not summarized as a single blanket InStock offer.

Do not hand-build ProductGroup markup merely to make the graph look larger. First inspect the current theme output and the official requirements. A smaller accurate graph is more useful than duplicated or contradictory entities.

Run a truth test, then a syntax test

1. Truth: compare name, selected variant, image, price, currency, availability, and identifiers with what a shopper can see and buy.
2. Structure: confirm each Offer belongs to the correct Product or variant and that URLs resolve as expected.
3. Syntax: run the live URL through Google's Rich Results Test and review errors separately from optional recommendations.
4. Coverage: repeat across alternate product templates and important inventory states, not every SKU blindly.
5. Monitoring: watch Search Console and retest after theme, pricing, localization, review, or schema-app changes.