Begin with the visible facts
Structured product data should describe the product the visitor actually sees. Review the name, price, currency, availability and destination against the rendered page and the underlying catalog. Do not publish an attractive starting price that the selected offer cannot be purchased for.
Google documents different product experiences and their requirements. Check the appropriate documentation for the type of page rather than copying an unrelated snippet from another site.
Test a changing product
Use an item with two variants, a sale price and a stock change. Inspect the output after each change. A stale script that still says “in stock” after the product becomes unavailable undermines the value of the markup.
Example: a product displays $49 for one option and $79 for another. The structured representation needs to match the offer structure actually supported on that page; a single copied price cannot explain every possible variant.
- Do not invent reviews or aggregate ratings.
- Keep image URLs accessible and relevant.
- Validate generated output with the applicable testing tool.
- Review the rendered source after deployment, not only the template.
Treat eligibility separately from appearance
Valid structured data can support search understanding, but it does not guarantee a rich result or override content policies. A schema check is one part of a publication review.
For a Torva launch, verify the production page with the final catalog and domain. Public demo data, private previews and staging URLs should not be mistaken for a merchant’s real searchable inventory.
Sources
Explore the Desk demo, walk through the eight themes or compare the Torva packages. No account required to explore.