Why does search show a different color from the variant on my product page?

Start from the exact external link

Open the URL that a shopper receives from the relevant result or feed. Record the variant selected on arrival, visible image, title, SKU, price and availability. Compare those with the actual product structured data. A URL that opens the parent’s default color is not evidence that the requested variant was preselected.

Google documents ProductGroup and variant properties for eligible product implementations, including distinct identifiers and URLs that select the appropriate variant. The right implementation depends on whether your variants live on one page or separate pages. Use the official examples with your developer rather than copying a generic JSON-LD block for a different architecture.

Create a consistency row per variant

Use the context and variant alignment CSV as a manual record. Its sample row is fictional. Replace it with your own authorized evidence; the worksheet does not connect to or change any external account.

Validate the actual page output

For a fictional three-color bottle, test the externally used blue URL in a fresh session. Inspect the page and available validation tools, then add the selected variant to a draft cart if appropriate. A syntactically valid structured-data test does not prove that the visible product or cart choice agrees with it. Review the generated HTML as delivered, especially when client-side scripts change the selected option.

Keep creative repair separate

If the actual image is the wrong color, return to the real variant reference. If it is correct but the markup selects a sibling, repair the publication mapping. Record what was aligned and the tested URLs. Itemlume does not generate store-specific ProductGroup markup or guarantee a search thumbnail. The goal is a truthful consistent offer; search presentation remains the engine’s decision.