Schema.org 'mpn' for product variations

Question

I have an ecommerce site and I am trying to make sure everything is structured correctly and am not sure what to do for the mpn value.

I have different variations of products that each have their own MPN, however, they exist on my site in one product page, with a drop down to select the variation that the user wants.

Should I be adding all MPNs to the structured data? Or how should the information be structured in this case?

unor unor · Accepted Answer · 2019-04-18T20:12:36

Each variant should be its own Product (or ProductModel). Then each Product/ProductModel would have one mpn value.

If one Product is used for all variants, it wouldn’t be possible to convey how the products differ (or that there are variants in the first place), and others couldn’t make statements about a specific variant.

For example, if one ProductModel is used for a shirt that gets offered in two variations, there is no way to convey which name/color/mpn belong together (it’s one product model with two names, two colors, and two MPNs):

{
  "@context": "http://schema.org",
  "@type": "ProductModel",
  "name": ["Blue shirt", "Red shirt"],
  "color": ["Red", "Blue"],
  "mpn": ["23", "24"]
}

So, there should be two ProductModel items instead:

{
  "@context": "http://schema.org",
  "@type": "ProductModel",
  "@id": "#p24",
  "name": "Blue shirt",
  "color": "Blue",
  "mpn": "24",
  "isSimilarTo": {"@id": "#p23", "@type": "ProductModel"}
}

{
  "@context": "http://schema.org",
  "@type": "ProductModel",
  "@id": "#p23",
  "name": "Red shirt",
  "color": "Red",
  "mpn": "23",
  "isSimilarTo": {"@id": "#p24", "@type": "ProductModel"}
}

Schema.org 'mpn' for product variations

1 Answers