Should a multi-page ProductGroup declare its own canonical URL?

Definition: No. Google's product variant documentation says that a multi-page ProductGroup has no single canonical URL because its variants are distributed across equally important pages. The url property is for single-page websites only.

Key facts

• Google separates product variant implementations into single-page and multi-page designs in its product variant structured data documentation.
• For a single-page site, Google requires one distinct canonical URL for the overall ProductGroup, usually the base URL with no variant selected.
• For a multi-page site, Google says there is no single canonical URL representing the ProductGroup.
• Google says not to use the ProductGroup url property on a multi-page website.
• Each multi-page variant page needs full, self-contained markup for the entities defined on that page.

Why does the answer differ between single-page and multi-page stores?

Google's product variant documentation, last updated 8 September 2026, describes a single-page site as one where all variants are selectable without page reloads, usually through query parameters. Its single-page guidance assigns the group one URL without variant selectors, while the variant URLs identify preselected versions. The group URL therefore identifies the page that represents the overall product group.

The documentation gives this single-page pattern for the group URL:

{
  "@type": "ProductGroup",
  "url": "https://www.example.com/winter_coat"
}

That rule does not carry over to a multi-page site. Google's multi-page examples place variants on different URLs and treat those pages as equally important, so no one page represents the whole ProductGroup.

What should the structured data contain on multi-page URLs?

Google says that the full ProductGroup definition must be repeated on each variant page because the group contains common attributes such as brand, material, and age group. Each page must also have full and self-contained markup, so an off-page entity cannot be required to understand the markup on the page itself.

In the nested multi-page pattern, the page gives complete data for its own variants. It can also include a variant containing only url to link to a variant on another page. Google's example uses the following shape:

{
  "@type": "ProductGroup",
  "hasVariant": [
    { "url": "https://www.example.com/coat/green?size=small" }
  ]
}

The page can instead define Product entities separately from ProductGroup and connect them with isVariantOf. Google says that structure may be easier for some content management systems to generate. The product group still needs a unique identifier, and each variant needs its own unique identifier in structured data.

Can a variant page still have a page-level canonical?

Yes, the absence of a ProductGroup URL is separate from canonicalization of an HTML document. Google's canonical URL documentation describes rel="canonical" as a method for duplicate or very similar pages and recommends a self-referential canonical on the canonical page itself.

For a duplicate URL that represents the same variant document, the canonical link points to that variant's preferred absolute URL. Google advises against declaring different canonical URLs for the same page through different methods, such as a sitemap and a rel="canonical" link.

<link rel="canonical" href="https://example.com/dresses/green-dresses" />

This element identifies the preferred URL for that document. It does not turn the variant page into a canonical URL for the product group.

How can a store check the implementation?

The product variant documentation says to validate the markup with the Rich Results Test, deploy a few pages, and use the URL Inspection tool to test how Google sees them. It also says each variant must have a unique ID, such as sku or gtin, and each product group must have a unique ID supplied through productGroupID or inProductGroupWithID.

For a multi-page implementation, check the rendered markup on every variant URL. The page should contain the complete group context and the variants defined there, while cross-page variants can be represented by their URLs. For page canonicalization, keep the preferred URL consistent across the HTML, sitemap, and internal links; Google's canonicalization documentation says that consistent internal linking helps it understand the preference.

Related terms

• ProductGroup structured data
• How should product variants be represented in structured data?
• Canonical URL

FAQ

Should a multi-page ProductGroup use the url property?

No. Google documents the url property for single-page websites only and says not to use it for multi-page websites.

Should the ProductGroup appear on every variant page?

Yes. Google says the full ProductGroup definition is repeated on each variant page because it contains attributes shared by the variants, and each page must be self-contained.

Can each multi-page variant URL have its own canonical link?

Yes, when a URL has duplicate or very similar alternatives, Google documents rel="canonical" for the preferred page URL and recommends a self-referential link on that page. That page-level choice does not provide a canonical URL for the overall ProductGroup.

Sources

1. Google Search Central, "Product variant structured data (ProductGroup, Product)", 8 September 2026
2. Google Search Central, "How to specify a canonical URL with rel="canonical" and other methods", 10 July 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer