ShipworkSite inspection
Checks

Crawlability

PaginationAre paginated pages set up right?Internal searchIs site search eating crawl budget?URL parametersAre parameters creating duplicates?Log analyserWhat does Googlebot actually crawl?Robots builderNeed a robots.txt file?Soft 404sAre pages “not found” but returning 200?JavaScriptCan crawlers see it without running JS?FreshnessIs my site quietly going stale?Robots.txtDoes robots.txt say what I think?

Indexing

Sitemap lastmodAre my sitemap dates valid?SitemapIs my sitemap actually fetchable?IndexingIs Google allowed to index my pages?CanonicalsIs Google indexing the wrong URL?Index signalsDo sitemap and index signals agree?Sitemap generatorNeed a sitemap.xml for my site?Bulk URL statusWhere does each of these URLs really land?Redirect builderNeed the redirect rules?RedirectsAre my URLs answering directly, over HTTPS?

On-page

Keyword ideasWhat are people searching for?SERP previewHow does my page look in Google?Content qualityAre your pages too thin or too alike?Image weightAre images slowing the page?CannibalizationAre pages competing with each other?On-page checkDoes the page use its target phrase?ImagesAre my images accessible and loading?Meta tag builderWhat should my title and share tags say?DuplicatesDo my pages compete for one query?

Links

Orphan pagesWhich pages can no link reach?Link graphHow deep do your pages sit?Anchor textDo links say what they point at?Outbound linksAre external links still alive?Broken linksAre internal links sending visitors nowhere?

Structured data

Rich resultsIs my markup eligible for a rich result?Structured dataIs my product schema valid?Schema coverageDo my key pages carry structured data?Social previewHow does my page look when shared?Schema vs pageDoes markup match the page price?Schema builderNeed valid JSON-LD?

International

Hreflang sitemapDo page and sitemap hreflang agree?HreflangDo my language versions link back?Hreflang builderNeed the hreflang tags?Page DoctorWhy is this page not doing well?Redirect planMy site has dead links — what redirects do I write?Sitemap diffIs anything missing from my sitemap?Robots simulatorWhat does my robots.txt actually block?Can Googlebot?Can Googlebot fetch this URL?
Every error, explainedGuides
Pricing Learn Error guides Run free audit

+1 free check

Welcome to Shipwork

Sign in free and your next check this month is on us.

Continue with GoogleContinue with email

We email you a 6-digit code. No password.

No card needed. Reports and watches follow you to any device.

ProductGroup schema: marking up product variants

When one product comes in several sizes or colours, Google can read the variants as a group if the page uses ProductGroup markup. This guide shows a complete JSON-LD example, what each property does, and how to check it.

Published

What ProductGroup does

ProductGroup is a schema.org type for a set of products that differ only in a few attributes, such as size or colour. Each variant is still a Product with its own SKU, price and availability. The group ties them together and says which attributes vary. Google documents this as product variant structured data for merchant listings; see Google’s product variants guide.

A complete example

A T-shirt sold in two sizes and two colours. The example uses placeholder URLs and values.

{
  "@context": "https://schema.org",
  "@type": "ProductGroup",
  "name": "Organic cotton T-shirt",
  "url": "https://example.test/products/tee",
  "brand": { "@type": "Brand", "name": "Example" },
  "productGroupID": "TEE-01",
  "variesBy": ["https://schema.org/size", "https://schema.org/color"],
  "hasVariant": [
    {
      "@type": "Product",
      "sku": "TEE-01-S-BLK",
      "name": "Organic cotton T-shirt, small, black",
      "size": "S",
      "color": "Black",
      "image": "https://example.test/img/tee-black.jpg",
      "offers": {
        "@type": "Offer",
        "url": "https://example.test/products/tee?variant=s-black",
        "price": "25.00",
        "priceCurrency": "USD",
        "availability": "https://schema.org/InStock"
      }
    },
    {
      "@type": "Product",
      "sku": "TEE-01-M-WHT",
      "name": "Organic cotton T-shirt, medium, white",
      "size": "M",
      "color": "White",
      "image": "https://example.test/img/tee-white.jpg",
      "offers": {
        "@type": "Offer",
        "url": "https://example.test/products/tee?variant=m-white",
        "price": "25.00",
        "priceCurrency": "USD",
        "availability": "https://schema.org/OutOfStock"
      }
    }
  ]
}

The properties that matter

  • productGroupID: the parent ID, often the parent SKU. Keep it stable; if your product feed has an item group ID, use the same value.
  • variesBy: the attributes that change between variants, as schema.org URLs such as https://schema.org/size and https://schema.org/color.
  • hasVariant: the list of variant Product objects. Each one carries the attribute values named in variesBy.
  • Variant offers: price, currency and availability belong on each variant, because they can differ.
  • Variant identifiers: sku and, where you have one, gtin, so the variant can be matched to your feed.

If each variant has its own page, a variant page can instead mark up a single Product and point back with isVariantOf or inProductGroupWithID. Pick one pattern per site and use it consistently.

Common mistakes

  • Prices in the markup that differ from the page. The price and availability shown to shoppers must match the markup for the selected variant.
  • Variant URLs that all return the same content. If ?variant= URLs do not preselect the variant, use the one product URL and rely on the variant list.
  • Attributes named in variesBy but missing on variants. Every variant should carry a value for each varying attribute.
  • A ProductGroup with one variant. A single item is a Product, not a group.
  • Markup that disagrees with the product feed. Different IDs, prices or availability between the page and Merchant Center can cause disapprovals.

Check it

Run the page through Google’s Rich Results Test to confirm the markup parses as merchant listing data, and check the Merchant listings report in Search Console after Google recrawls. Shipwork’s free audit reads the structured data on sampled product pages and flags missing price, availability and identifier fields, and the schema generator builds starter JSON-LD you can adapt.

Find out if this is happening to you

Shipwork reads the structured data on sampled product pages and flags variants missing price, availability or identifiers. Free, no account, no signup. Paste your store address.

Generate structured data

Questions

What is ProductGroup schema?
A schema.org type that groups product variants, such as sizes or colours, under one parent with a productGroupID, the attributes that vary and a list of variant Products.
Do I need ProductGroup if each variant has its own URL?
You can mark up each variant page as a Product that points to the group with isVariantOf or inProductGroupWithID. Use one pattern consistently.
Does ProductGroup markup guarantee rich results?
No. Valid markup makes a page eligible; Google decides what to show.

Keep reading