Decide whether the variants need distinct destinations
Keep ordinary size choices on a shared shirt destination when the content and buyer purpose remain equivalent. Evaluate separate pages when fit or specifications create a distinct item to compare. Preserve the shopper’s selection through the cart regardless of the preferred search URL chosen for equivalent versions.
Worked example — illustrative data.
| Variant situation | URL approach to evaluate | Reason |
|---|---|---|
| Same shirt, size S or M | One preferred product URL; preserve selection for shoppers | Size alone adds little standalone content |
| Same shirt, navy or cream | Shared product page unless separate buyer value exists | Avoid duplicate pages with changed swatches |
| Different fit and different specification | Evaluate separate product pages | The buyer is comparing different items |
First ask whether opening the proposed URL gives a buyer a materially different answer. If it does not, record one preferred product destination and make the selected variant clear in the page and cart. If it does, document the distinct title, specifications, images and links that justify the separate page. Compare response markup, rendered content and internal links so the site’s signals do not point in opposing directions.
Keep the chosen variant usable after URL consolidation
Open a shared product URL with the intended finish or size selection and inspect the cart path. Check that canonical preference does not erase a meaningful buyer selection or misstate stock. If distinct specifications justify separate product pages, document that identity decision before setting canonical signals. In either case, verify internal links and preferred URLs consistently.
Decision: Use the shared shirt page for the fictional size choices. Reconsider separate URLs only when the catalog and buyer task support distinct pages rather than a different parameter string.
One unavailable size does not describe all sizes: A size may be unavailable while other sizes remain purchasable. Do not mark every version unavailable simply because one selection is empty, and do not use a canonical tag to conceal a broken variant state.
Can a canonical tag repair a broken variant selector?
No. Canonical preference concerns duplicate or similar URL signals. The shopper still needs a working selector, accurate variant information and a correct cart line. Diagnose selection and inventory defects separately from URL preference.
Continue with Guides for stores, software teams and local businesses, eCommerce SEO services and Plan Shopify product options.
For canonical URL signals, see Google canonical URL guidance (checked November 2026).