Product Structured Data: Match the Real Page

SECTION 01

Make field ownership part of the agency brief

Ask where names, identifiers, prices, currency, stock status and images come from. If the storefront reads current commerce data but the markup uses a spreadsheet copied during launch, the two will diverge. Identify any theme, app or custom component already producing markup before adding another. Duplicate blocks that disagree can be harder to diagnose than a missing optional field.

Google's product-variant guidance distinguishes related variants and different page models. Its structured-data quality rules require the markup to reflect visible, relevant information. The implementation should follow the store's actual product organization rather than a generic example copied unchanged. The agency should explain which properties apply, which evidence exists and which optional fields should remain absent because the business cannot support them.

SECTION 02

Illustrative example: a bottle sold in two sizes

Imagine a reusable-bottle product offered in two capacities at different prices. The small size is available and the larger size is temporarily unavailable. A generic markup snippet describing one lowest price and universal availability could misrepresent the buyer's selection. The agency instead maps the actual variant arrangement using the relevant supported schema structure and preserves consistent identifiers and product URLs.

During an acceptance test, staff change availability and then update a price in the source catalog. The rendered page and its markup are checked again, including the relevant variant URLs. The test does not assume every search feature updates immediately. It demonstrates that the website publishes internally consistent information, which is the part the development team can directly control.

SECTION 03

Validate content meaning as well as syntax

Use the applicable structured-data testing tools, but also compare the output manually against the visible page. Sample a normal product, a multi-variant product, an unavailable item and a product with a supported sale price. Check that images resolve, currency is explicit and any included reviews are genuine visible content. Inspect the public rendered version, not only a development object in source code.

Native platform markup may already cover much of the requirement. A targeted correction can be better than adding a second plugin or custom generator. Handoff should identify the responsible component, document the source fields and provide repeatable sample checks. Ask for an honest distinction between validation success, search-engine eligibility and actual displayed results; these are different outcomes and should not be sold as one guarantee.

SECTION 04

Frequently asked questions