Check a Product Variant Before You Fix Its Structured Data
By STEADYWRK Team
Before changing a product's markup, identify the exact item and variant a visitor is viewing. A shirt in one size can have a different price or availability from another size. Comparing the page for one variant with the markup for another creates a finding that may be wrong before anyone edits the store.
This exercise uses a fictional notebook product. The identifiers, amounts and stock states are illustrative and do not describe a real store or a STEADYWRK offer. Download the review sheet and keep a separate row for every variant you inspect.
Establish one reproducible view
Open the product's public URL in a fresh browser session. Select the intended variant and record the resulting URL, selected option labels and observation time. If the URL stays the same, record the selection steps so another reviewer can reproduce the view.
Use this fictional example as your starting note:
| Item | Observed value |
|---|---|
| Product | Demo notebook |
| Variant | Blue cover, small |
| SKU | DEMO-BLUE-S |
| Displayed price | 14.00 |
| Displayed currency | JOD |
| Availability | Out of stock |
Copy the values as displayed before interpreting them. “Unavailable in this size” and “ships later” may describe different states. If the currency is absent, record not shown; your location or another product's currency does not settle the question.
Compare the same fields in the same state
Inspect the structured data emitted for that view, including any markup added after the page loads. Identify the Product and Offer that refer to the selected variant. When several products or offers appear, keep their identifiers with your notes so you do not accidentally compare a recommendation card with the main product.
Google's product variant documentation describes ProductGroup, Product and the relationship between a group and its variants. The distinguishes product snippets from merchant listings. Check the documentation relevant to your page structure; this worksheet does not replace a complete markup implementation review.