Technical SEO & AI Search

Product Variants and SEO: One URL or Many?

Should each color or size get its own URL? Learn when to keep variants on one page, when to split them, how canonicals work and how to mark up variants.

TL;DR
  • Keep variants on one product page when they differ only by size or other details nobody searches for. Split them into separate pages when people search for the variant itself, usually by color, material or model.
  • On a single page, each variant should still be selectable through its own URL (often a query parameter), with one canonical URL for the whole product.
  • Google supports variant structured data (ProductGroup with hasVariant and variesBy), which helps it understand how your variants relate.

Why do product variants cause SEO problems?

A single shoe can come in 6 colors and 10 sizes, which is 60 variants. How those variants appear in URLs and pages decides whether Google sees one strong product page, 60 weak near-copies or something in between.

Common problems:

  • Duplicate content: many URLs with almost identical content compete with each other.
  • Wasted crawling: search engines spend time on variant URLs that add nothing, which matters more on large catalogs with limited crawl budget.
  • Missed demand: if a color people search for (“green rain jacket”) is hidden as a dropdown option, there is no page that can rank for it.
  • Wrong details in results: price, image or availability shown in search does not match the variant the shopper wanted.

When should variants share one URL, and when should they get their own?

The deciding question: do people search for this variant specifically?

Variant type Do people search for it? Usual approach
Size Rarely One page, size selector
Color for fashion or home Often (“sage green linen duvet”) Separate pages per color, or one page with color URLs that Google can index
Material or finish Often (“walnut desk”, “brass faucet”) Separate pages
Pack size or quantity Sometimes One page, unless pack sizes are distinct products
Model or generation Yes Separate pages

Check with real data. Look in Search Console and keyword tools for searches that include the color, material or model. If there is clear demand, a dedicated page can rank and convert better than a generic one. If not, consolidating strength into one page is usually better.

How does the single-page approach work?

On a single-page setup, all variants live on one product page and the shopper switches between them with selectors.

Good practice:

  • Each variant can be preselected through a distinct URL, often using a query parameter such as ?color=green&size=m or a variant ID. Loading that URL should show the right image, price and availability and allow adding to cart.
  • One canonical URL for the whole product, usually the base URL with no variant preselected. Variant URLs point their canonical tag to it.
  • The base page shows something sensible by default, such as the best-selling variant, with accurate price and availability.

Shopify works this way by default: variants share the product URL, a ?variant= parameter preselects a variant and the canonical points to the base product URL.

How does the multi-page approach work?

On a multi-page setup, each important variant (often each color) has its own product page with its own title, images and description, and links between siblings.

Good practice:

  • Each page has unique content: title that includes the variant (“Linen Duvet Cover, Sage Green”), variant-specific images and a description that mentions the variant.
  • Each page is self-canonical, because each one is a distinct page that should rank on its own.
  • Sibling links let shoppers switch colors easily, so the experience feels like one product.
  • Collections avoid clutter. Showing every color as a separate card can overwhelm category pages. Many themes group them or show swatches.

On Shopify, separate products per color are common. Shopify also offers a Combined Listings app for Shopify Plus stores that groups separate products so they display together as one listing with options.

What structured data should you add for variants?

Google added support for product variant structured data in February 2024. It uses the Schema.org ProductGroup type alongside Product.

Key properties:

  • ProductGroup with a productGroupID (the parent ID).
  • variesBy to state which properties change, such as size or color.
  • hasVariant to nest each variant (a Product with its own SKU, price, availability and image).
  • On multi-page setups, each variant page carries full markup for what it shows, and variants can reference their group.
{
  "@context": "https://schema.org",
  "@type": "ProductGroup",
  "name": "Linen Duvet Cover",
  "productGroupID": "DUVET-LINEN",
  "variesBy": ["https://schema.org/color", "https://schema.org/size"],
  "hasVariant": [
    {
      "@type": "Product",
      "sku": "DUVET-LINEN-SAGE-Q",
      "name": "Linen Duvet Cover, Sage, Queen",
      "color": "Sage",
      "size": "Queen",
      "offers": {
        "@type": "Offer",
        "price": "189.00",
        "priceCurrency": "USD",
        "availability": "https://schema.org/InStock",
        "url": "https://example.com/products/linen-duvet?variant=sage-queen"
      }
    }
  ]
}

Check your theme or app output in Google’s Rich Results Test. For full product markup, see product schema for eCommerce. Variant data in your Merchant Center feed should match what the markup and page show.

Worked example: splitting colors for a home textiles brand

(Illustrative numbers.) A bedding brand sells duvet covers in 8 colors on one product page per style. Search Console shows almost no impressions for color-specific queries, but keyword tools show steady searches for several colors (“sage green duvet cover”, “terracotta duvet cover”).

The team:

  1. Splits the three colors with clear search demand into separate product pages, each with its own title, images and description.
  2. Keeps the five low-demand colors on the main page as variants.
  3. Adds sibling color links on every page.
  4. Adds ProductGroup markup with color and size as variesBy properties.
  5. Links the new color pages from the relevant collection and from a color-themed guide using descriptive anchors.

Three months later, the team checks impressions and clicks for color queries, and organic revenue for those colors, compared with the period before the split.

Checklist: product variant SEO

  • [ ] Variant types reviewed for real search demand (color, material, model, size)
  • [ ] Decision made per product type: single page or separate pages
  • [ ] Single-page products: each variant selectable by a distinct URL
  • [ ] Single-page products: one canonical URL for the whole product
  • [ ] Separate pages: unique titles, images and descriptions per variant
  • [ ] Separate pages: self-canonical and linked to sibling variants
  • [ ] Default variant on each page shows accurate price and availability
  • [ ] ProductGroup structured data with variesBy and hasVariant validated
  • [ ] Merchant Center feed variants match on-page data
  • [ ] Collection pages do not show near-duplicate cards for every variant

FAQ

Does Shopify handle variant SEO automatically?

Shopify’s default setup is a reasonable single-page approach: variants share the product URL, a variant parameter preselects options and the canonical points to the main product. If certain colors deserve their own rankings, you need separate products for them.

Will separate variant pages be seen as duplicate content?

Not if each page is genuinely different for shoppers: unique title, images and a description that reflects the variant. Pages that differ only by a word in the title are likely to compete with each other.

Do I need variant structured data?

It is not required, but it helps Google understand which products belong together and how they differ. It is most useful for stores with many variants, and it should match what the page and your product feed show.

Turn this into a plan for your store

The Free Profit Audit scans your store, sizes your biggest profit leaks and builds a 90-day plan.

Free Profit Audit