To align WooCommerce product structured data with variants, describe the shared design as a ProductGroup and each distinct buyable option as a Product in that group. Put the variation’s SKU on its Product and its current price, currency and availability on its Offer. Check that the URL used for the variant opens the matching selection and displays the same information.
Start with the individual WooCommerce variation, not the price range or stock message on the unselected parent page. For example, a green option can be out of stock while a brown option from the same group is available at a different price. The storefront, rendered markup and optional Merchant Center feed can format those facts differently. The test is whether they describe the same option.
1. Decide what counts as a distinct variation
Open the WooCommerce variable product and list the combinations the store actually offers. Record the attributes shoppers use to choose between them, such as color or size, then identify the variation behind each complete selection. If a product varies by both color and size, green alone is not specific enough to identify an offer. You need to know which green size the price and stock status belong to.
Use WooCommerce to locate the values and the storefront to confirm how they resolve. A variation may have its own price, stock settings and image, but not every value needs to be managed independently. For example, a variation can use stock managed at the parent level. In that case, record the availability that applies to the selected option rather than guessing from whether the variation has its own quantity field.
Working example: Consider a variable product offered in green and brown, with color as the only choice. The two variations share a design but have distinct SKUs and photos. Green is temporarily out of stock. Brown is available and has a different current price. Both belong to the same group, but neither should borrow the other’s offer. If the unselected page shows a price range, that is a page-level summary, not the price of either specific option.
Make one worksheet row per variation. Start each row with the customer-facing attribute values and a stable identifier. Add the price shown for that choice, its availability, the image that represents it and the URL behavior you observe when opening the variant directly. Keep the parent’s information separate so it cannot accidentally fill a blank in a row that needs a variation-specific value.
Before handing the worksheet to whoever manages markup or feeds, ask them to find both example rows using only a storefront selection and the corresponding internal SKU. If those details still leave more than one candidate, settle the identity problem before debugging the offer.
2. Keep the product group stable and the variants distinct
Use the product group for facts that belong to the shared design and the variant Product for facts that identify an individual version. In the green and brown example, the group represents the design sold in two colors. It does not stand in for the brown variation merely because brown is the default selection, nor does it become a green product when the shopper chooses green.
Google’s variant documentation uses productGroupID to identify the group and variesBy to describe what changes between variants. For the example, the variation dimension is color. If size is later introduced as a genuine choice, review the group definition and the individual variant attributes together. Adding a size selector without updating the representation can leave multiple offers that look indistinguishable to someone reading only the markup.
The group can associate its variants through hasVariant. A variant can refer back to its group through isVariantOf where appropriate to the page model. Follow the variant documentation for the structure that matches your site rather than treating these properties as interchangeable fields to add everywhere. In either model, the relationship needs to identify the same parent design across its related choices.
Choose a group reference that survives changes to merchandising. A different default color, a temporary stockout or a revised display title does not, by itself, change which design the options belong to. If a feed is in use, its item_group_id should group the corresponding variant rows. The feed and markup identifiers need not be formatted alike, but keep a record of their correspondence so a reviewer can follow the relationship in both directions.
Test the grouping with the default set to brown and then inspect green. Expect the group reference to stay put while the selected SKU, color, image and offer can change. If both selections expose the same variant SKU, investigate identity first. If switching color produces an unrelated group reference, investigate the way the parent relationship is generated.
3. Map WooCommerce fields to markup and feed fields
Build the mapping around what each destination is supposed to describe. A WooCommerce variation is the reference for the chosen option. The markup describes that option and its offer; a Merchant Center feed, if you use one, submits the corresponding item. The labels and formats can differ, but matching labels are less important than matching the underlying product and commercial facts.
| Field | WooCommerce and storefront | Structured data | Merchant Center feed |
|---|---|---|---|
| Current price | Price shown for the selected variation | Offer price and priceCurrency | price and, where applicable, sale_price |
| Availability | Stock and ordering status for that selection | Offer availability | availability |
| Variant identity | Distinct variation SKU | Product sku | Stable item id mapped to the variation |
| Parent group | Shared variable product | ProductGroup productGroupID and variant relationship | Shared item_group_id |
| Color and image | Selected color and its representative photo | Variant Product color and image | color and image_link |
Treat identity as a deliberate mapping, not a shortcut. If the feed uses an internal variation ID instead of the store SKU for its item ID, document which feed row goes with which SKU. That difference is not itself a mismatch. It becomes a problem when the row for green lands on brown, or when two rows intended to represent different options point to the same selected option.
For price and availability, compare meaning after accounting for format. The storefront may show a currency symbol next to the price, while markup expresses the amount and currency separately. An availability message and a structured value may use different words. Compare what the customer can actually order, not whether the strings look identical.
Add one more column to your working sheet: who owns the decision when values disagree. A price discrepancy may originate in a variation setting or in how a feed export applies sale pricing. Recording the owner alongside the mapping makes the sheet useful during a release, when the person who spots the mismatch might not control the component that produced it.
4. Match each offer to the price and availability shoppers see
Check a variation’s offer after making a complete selection. If brown has its own price, its offer should describe that price, not the lowest number in a parent range and not the amount shown for green. When a sale is active, verify which price is currently displayed and how the feed represents regular and sale amounts. The comparison is about the effective offer for that selection, not whether every destination stores one price field.
Record the currency at the same time. A matching amount is not enough if the markup identifies a different currency from the one displayed to shoppers. If your store serves more than one currency, note which storefront context you inspected and compare it with the corresponding feed, if applicable. Do not compare a price from one storefront context with a feed submission intended for another and label the difference a variation error.
Availability needs its own check. Select green and confirm that the visible message and order controls reflect its out-of-stock state. Check the green offer and the green feed item, without treating brown’s availability as evidence for green. Now select brown and verify that it still shows its available offer. This second check catches a different mistake: an update that marks the entire group unavailable when only one option is affected.
Be careful with backorders. A quantity at or below zero does not tell you, on its own, whether the selected item can be ordered. Inspect the variation’s ordering policy and what the storefront communicates. Translate that state using the availability values supported by each destination rather than exporting a raw quantity or assuming that every depleted item is unavailable.
Separate selection from the accepted cart action. A shopper may be able to select a color and view its photo even when it cannot be added to the cart. For an option that is supposed to be orderable, an accepted add-to-cart action can confirm which variation was accepted. It is not a payment test; no purchase is needed to check the offer mapping.
5. Check that the variant URL opens the intended selection
Decide whether the store presents variants on one product page or on separate pages. A single WooCommerce product page can give shoppers a selector for multiple options, but that does not remove the need to identify individual variants by URL. Google’s variant documentation distinguishes single-page and multi-page designs. Use the guidance for the design visitors actually encounter, not the one suggested by the number of products in the WooCommerce dashboard.
For the example, open the address used for brown in a fresh browser session. Observe what appears once the page settles: the selected color, current price, stock message and representative photo. Repeat with the address for green. Opening the addresses directly matters because a variant may work when clicked from the parent page but fail to initialize when reached independently. A previously selected option can hide this problem during a routine check.
If the green address opens the brown selection, treat it as a mismatch even if green can be selected manually afterward. Check whether navigation discards the selection information or whether the storefront receives it without applying it. Also test any default selection. An unselected parent page or a brown default can be appropriate when opening the general product page, but neither should replace green at the address intended to identify green.
For products that genuinely use separate variant pages, inspect each page independently and check that the markup on each represents the variants and group as the documentation specifies for that arrangement. Being able to navigate to brown from green is not the same as having a brown address that opens the correct product. Confirm that each relevant page exposes the intended variant facts when entered directly.
Keep URL results in the mapping sheet. Record the intended option and the option actually shown, plus whether the price, stock and photo match. That short record helps separate a routing or selection problem from a markup problem: changing an offer in the markup does not make a URL select the right product.
6. Inspect what the storefront publishes, not just what the settings say
Identify where product structured data is generated and where the feed values are prepared. These may be different parts of the store setup. An update saved in WooCommerce is the start of the check, not proof that each output has changed. For a given variation, collect three pieces of evidence: what the storefront shows, what its rendered markup says and, if relevant, what the exported feed row contains.
On a page that describes several variants, find the Product entry for green by SKU and color before reading its offer. You may see information for brown on the same page; its presence is not a conflict if it is correctly attached to brown. The problem is competing information for the same entity, such as two entries that claim to describe the green variation but assign it different prices.
If more than one component publishes product information, identify what each contributes before removing or changing anything. A useful diagnostic is to follow the group reference to the variant and then follow the variant to its offer. That makes it easier to distinguish a duplicate entry from an intended group-and-variant relationship. Give one owner responsibility for resolving contradictions instead of patching the displayed price and the marked-up price independently.
For the feed, locate the item by its mapped ID and check its destination address, grouping, price, availability and image. The submitted photo should represent that option, even if the feed and storefront use different versions of the image file. If green has a distinct photo and its feed row shows brown, it is a variant mismatch, not merely a difference in file names.
Run a markup validator to check syntax and required fields. Then check the storefront yourself. A validator may accept an offer that is well formed but attached to the wrong color; it does not establish what your shopper can see or order. Record validation and visible agreement as separate results so that a pass on one cannot hide a failure on the other.
7. Run mismatch tests after stock, price and image changes
Start with a baseline for both colors. Open each variant directly and record its visible color, current price, availability and representative photo. Save the corresponding rendered markup values and, if used, the feed row. Record when you checked each surface. Change one field at a time so you can tell whether the intended value moved and whether any neighboring value changed unexpectedly.
- Stock test. In a controlled test, capture green before and after it moves from available to out of stock. Check that the selected page reports the new state and that its ordering behavior agrees. Inspect the green offer and feed item, then confirm that brown remains available.
- Price test. Change the current price of brown and reload its direct selection. Compare the displayed amount and currency with the brown offer and the effective price in the feed. Confirm that the green price was not overwritten and that brown did not inherit the low end of a group range.
- Image test. Replace the representative green photo and reopen green directly. Compare the visible photo with the image associated with green in the markup and feed. Check brown as a control: its photo should not switch to green.
When a test fails, write down the exact disagreement and where you found it. “Green is out of stock on the page, but the rendered green offer reports it as available” is actionable. “Stock schema broken” leaves the next person guessing which option, which output and which direction the mismatch went. If the URL opens the wrong choice, resolve that before using the page as evidence for other field comparisons.
Recheck after the relevant page refresh or feed export, and record when agreement returns. A temporary discrepancy during an update and a persistent mapping fault warrant different fixes. Keep the before and after observations and repeat the test that caught the issue; a corrected value on the parent page alone does not prove that the individual variation now passes.
8. Handle exceptions without substituting parent values
Shared stock: If the parent manages stock for several variations, calculate the availability each selected option actually presents. Do not assume every blank variation quantity means out of stock, or that a parent quantity makes every variation independently orderable. Inspect the storefront and the applicable stock settings before deciding whether the same availability legitimately applies to multiple offers.
Temporarily unavailable versus removed: An out-of-stock green option that still exists is different from a color the store has removed. If green is still represented, make sure its visible state, offer and feed entry agree. If green has been removed, check that the current group and feed no longer describe it as a live option. Open the old address as part of the review so you know what a visitor reaches instead.
Partial selections: On a product with color and size, verify that the customer has chosen enough attributes to identify a specific combination. For example, a green image may appear before a size is selected. That visual change does not establish which green SKU or price applies. Test a complete selection and check that the variant address identifies that same combination rather than only the color.
Shared images: Some variations may legitimately use the parent image. The useful question is whether it represents the selected option. A shared photo is not automatically a defect, but if shoppers see a distinct brown photo when they choose brown, a green photo in the brown markup or feed is not a valid fallback. Check that image assignment follows the intended variation rather than whichever option was uploaded first.
Store defaults: When the default selection changes, run the direct-entry checks again. The generic product page may now open with brown instead of green, but any address meant to select green should still do so, and the group reference should still identify the same design. A clean separation between default behavior and variant identity prevents a merchandising update from silently changing what several listings describe.
9. Measure agreement and make the checks part of publishing
Measure agreement by variation and field, rather than giving the whole product a single pass or fail. A brown variant might have the right SKU and price but the wrong photo. A green variant might have correct markup and an outdated feed row. A useful review sheet records which combination failed, the output where it failed and when it was last observed. Count separately how many checked variants opened with the wrong selection.
Measure update lag as well as mismatch counts. Note when a controlled change became visible on the selected storefront page, when it appeared in the rendered markup and when it appeared in the next relevant feed export. This distinguishes an output that is consistently late from one that never reads the variation field at all. Use what you observe to choose when to recheck after an edit rather than assuming every surface updates at once.
Prioritize changes that can affect multiple listings. A routine price edit may only require a before-and-after check of the edited variation and a sibling. A change to the markup generator, feed mapping or variant selection behavior calls for a broader sample. Include a product with each meaningful condition your store supports, such as an unavailable option, a sale price, shared stock or more than one selection attribute.
Set release criteria your team can verify: the variant URL opens the intended choice, the visible price and availability match the offer, the SKU identifies that choice, and the parent reference still joins the right variants. If the store submits a feed, require the relevant row to agree as well. Record any unresolved discrepancy with an owner and a recheck date rather than treating the validator result as final approval.
Use validation and these storefront checks to judge data quality, not to predict a particular search appearance. The practical outcome is a mapping you can verify after a change: green remains green wherever it is represented, brown keeps its own offer, and both stay attached to the same product group.
Related guides
- How to turn pre-purchase questions into useful product-page answers
- A store-specific checklist for evaluating an AI chatbot
