How should I handle schema.org markup for a product with multiple sizes/prices

Question

While implementing schema.org markup for one of my cusomters online-shops I noticed a little difficulty. I think it's a missing option in the markup. Neighter offer nor aggregateOffer can handle this case correctly - although I think it is quite common.

• One page for one product (let's say it's a body-lotion)
• The body-lotion comes in 3 sizes, 100, 200 and 250ml
• It basically has an internal productId (BL100, BL200 and BL250) for each size as well as a EAN (http://en.wikipedia.org/wiki/International_Article_Number_(EAN)) for each size.
• How to buy: Go on the product page, chose your size, the price changes via javascript, click add to chart

Q: How can I markup ONE product with MULTIPLE sizes and MULTIPLE prices correctly?

Problems: http://schema.org/Product suggests only ONE productID which is wrong for me. If I add three offers (http://schema.org/Offer), search engines might think, the pricing is totally weird because the same product has three different offers.

http://schema.org/AggregateOffer doesn't seem right to me eighter.

Thanks for your help.

Answer 1

I think the correct way to mark up this particular scenario is by nesting several Offers inside of a single Product. To add additional information to each Offer, use an IndividualProduct. I'm not 100% sure, but this seems to work well in the Google Structured Data Testing Tool.

It looks like schema.org is still being updated with new ways to markup your products. The schema.org project pulled in a lot of structure from the Good Relations e-commerce product vocabulary. See E-commerce SEO Using Schema.org Just Got A Lot More Granular for more information about the new vocabulary items.

Say we want to list information about Sumatra coffee beans for sale on a website. We want to sell two different sizes (12 oz. and 16 oz.) with different prices for each. However, both product sizes should have the same images ('tis just a coffee bean) and name. The structure will look something like:

Product (name, description, and image)
  aggregateRating
  Offer (price and priceCurrency)
    IndividualProduct (sku and weight)
  Offer (price and priceCurrency)
    IndividualProduct (sku and weight)

Copy and paste the following into Google's Structured Data Testing Tool to see how Google will interpret the HTML.

jsFiddle display

<article class="product" itemscope itemtype="http://schema.org/Product">
  <div class="images">
    <a href="images/product.jpg">
      <img alt="Sumatra Coffee Beans" itemprop="image" src="images/product.jpg">
    </a>
  </div>
  <div class="content">
    <header>
      <h1 itemprop="name">Sumatra Coffee Beans</h1>
    </header>
    <div class="code">
      <span class="label">Item Number:</span>
      <span itemprop="productID">sumatra-coffee</span>
    </div>
    <div itemprop="description">
      <p>Error 418</p>
    </div>
    <div class="reviews" itemprop="aggregateRating" itemscope itemtype="http://schema.org/AggregateRating">
      <div class="details">
        Rated <span itemprop="ratingValue">4.5</span>/5
      </div>
      <div class="count">
        (<span itemprop="reviewCount">9</span> reviews)
      </div>
    </div>
    <div class="offer" itemprop="offers" itemscope itemtype="http://schema.org/Offer">
      <div itemprop="itemOffered" itemscope itemtype="http://schema.org/IndividualProduct">
        <span class="sku" itemprop="sku">scb-ov1</span>
        – (<span itemprop="weight">12 oz.</span>)
      </div>
      <div class="price">$<span itemprop="price">14.99<span></div>
      <meta content="USD" itemprop="priceCurrency">
    </div>
    <div class="offer" itemprop="offers" itemscope itemtype="http://schema.org/Offer">
      <div itemprop="itemOffered" itemscope itemtype="http://schema.org/IndividualProduct">
        <span class="sku" itemprop="sku">scb-ov2</span>
        – (<span itemprop="weight">16 oz.</span>)
      </div>
      <div class="price">$<span itemprop="price">20.99</span></div>
      <meta content="USD" itemprop="priceCurrency">
    </div>
  </div>
</article>

Answer 2

I think I would have one Product that contains multiple Offers, one per size. The limitation, of course, is that it doesn't offer a formal means for specifying multiple product IDs, but perhaps you could informally put those in the Offer's Description or URL property. That's not an exact fit, but maybe it's close enough.

Another option is to join the Public Vocabs email list (lists.w3.org/Archives/Public/public-vocabs), which asserts that it is "the place to propose extensions, new types, or feedback from deployment experience with the existing vocabulary" (lists.w3.org/Archives/Public/public-vocabs/2011Oct/0162.html), and propose a solution to your problem.

Answer 3

I would recommend a slightly different way of thinking about this particular web page. Instead of thinking about this specific webpage as a 'Product' page, think about it as a 'WebPage' type. This 'WebPage' then actually contains three different 'Products', each with their own 'Offer' and their own 'productID'. When you're saying that each size has it's own EAN, that's a big indicator to me that each size's price/size/id should be contained inside if it's own 'Product' div.

Answer 4

This is what Google says to do: Use itemOffered The item being sold. Typically, this includes a nested Product, but it can also contain other item types or free text.

Answer 5

All the different variations should be represented as separate Products with separate Offers. Use Product's isSimilarTo and isRelatedTo properties to link them together.

reference: http://schema.org/Product

Answer 6

Consider using "AggregateOffer" for the product, than within each offer specify each size as a different "itemOffered"

https://schema.org/itemOffered

While several common expected types are listed explicitly in this definition, others can be used. Using a second type, such as Product or a subtype of Product, can clarify the nature of the offer.

Answer 7

I think ProductGroup is the key. See https://schema.org/ProductGroup

I have a similiar quest and I find it hard to match google suggestions for xml product feeds with schema.org specs. Thing is, that feed should include each sku as single feed item (each shoe size separately), yet wa sell them as one product with different sizes. Our developer uses AggregateOffer to link all the sizes together, but specs does not allow each offer item to differ or even include an sku field. Product seems to suit the case better. Both sku and +size* are valid, properties of Product. Different sizes should be linked by productGroup.

In Your case i would look into ProductModel for grouping multiple Product options, as it allows PropertyValue fields. See https://schema.org/ProductModel