How should product variants be canonicalized when size, color, and configuration have different URLs?

Classify variants by whether they represent independently useful landing pages.

If a variant has unique search demand, distinct content or specifications, a stable SKU, and can be purchased directly, it may deserve an indexable self-canonical URL. Examples can include materially different models, capacities, or product configurations.

If color/size variants are only selectable states with almost identical content, a single canonical product page is usually easier to maintain. Variant parameters can remain functional for users while canonicalizing to the primary product URL, provided the canonical truly represents the same product family.

Keep structured data consistent with the visible purchase experience. If the page supports multiple offers/variants, model them accurately rather than publishing one price/availability value that conflicts with the selected option.

Avoid creating internal links and sitemaps for every low-value variant. Promote only the variants you intentionally want discovered. Ensure canonical variants are linked directly and return 200 without requiring a prior session state.

For out-of-stock variants, do not automatically canonicalize to an unrelated in-stock option. Preserve useful variant URLs when they may return; otherwise handle discontinued variants according to replacement quality.

Test faceted/category links as well. A variant strategy can be correct on the product page while navigation still exposes thousands of duplicate parameter URLs.

The governing question is whether the variant is a durable search destination or merely an interface state.