BigCommerce Product Schema: Audit and Validation Guide

Inspect the markup the storefront actually emits

Collect the initial HTML and rendered output for representative product pages. Identify structured data from the theme, apps and custom scripts. Do not assume that a platform default describes the current installation. Record which component owns each entity before removing or adding markup.

Multiple entities are not automatically an error. Check whether they describe distinct things coherently or duplicate the same product with conflicting facts. Use Google’s product snippet documentation for current requirements and eligibility.

Map product facts to their source

Audit scope: this table describes evidence to collect and responsibilities to agree. It does not report a completed implementation or imply that every listed field is required for every product.

Follow the required and recommended properties for the intended feature. Do not invent a GTIN, review, rating or identifier to eliminate a validation warning.

Represent variants without flattening the catalog

A product family can need more structure than a single undifferentiated offer. Google documents ProductGroup and product variants. Compare that guidance with the actual product relationships and URL behavior rather than applying a universal one-product, one-offer rule.

A category listing and a page focused on one product have different purposes. Do not assume adding Product markup to a category makes it eligible for the same product snippet treatment as a product detail page.

Keep structured data consistent with visible content

Check the relevant product state for price, currency, availability and options. Review data generated after JavaScript execution as well as the initial HTML. Google recommends including product markup in the initial HTML; dynamically generated, fast-changing offer information needs particular care.

Review Google’s structured data policies. Markup should describe the page accurately. Validation is not evidence that a store has earned review stars or that a particular rich result will appear.

Validate representative products and preserve the evidence

Implementation scope: agree examples covering the store’s relevant product types, such as a simple product, a variant family, a sale item and an unavailable item. Compare the emitted data with the visible page, run the applicable Rich Results Test checks and save the output with the tested URL and date. Investigate errors and assess warnings against the current documentation.

Assign each correction to the responsible theme, app or data source. Test approved changes in a suitable environment, keep a rollback method and recheck after deployment. Search Console enhancement reports can help monitor detected issues; a clean report does not guarantee display.

Connect schema work to the wider SEO review

Structured data is one part of a product page review. Check crawl access, preferred URLs, useful content and internal links alongside markup. Read the BigCommerce SEO guide for the broader investigation.

Use BigCommerce SEO services to define search priorities, BigCommerce Stencil development for theme work, and BigCommerce support to investigate an existing conflict. Bring affected URLs and validation output so scope can be based on the actual installation.