Schema.org product offer with a price range, or multiple offers with single prices?

[4RS_John]

I'm implementing Schema.org, (JSON-LD), on an eCommerce site. Each product has a few different variations, and these variations can change the price, (think T-shirts, but blue & white cost $5, red is $5.50, and yellow is $6).

In my Schema.org markup, (using JSON-LD), in each Product's Offer, I could either have a single Offer with a price range, (minPricd: $5, maxPrice $6), or I could add a separate Offer for each variation, each with its own, correct, price set.

Is one of these better than the other? Why? I've been looking at the WooCommerce code and they seem to do the single offer with a price range, but that could be because it's more flexible for a system that's used by millions of people.

[BlueprintMarketing]

Each product can have a few different variations

See Google's https://developers.google.com/search/docs/data-types/product

Aggregate offer properties

An AggregateOffer is a kind of Offer representing an aggregation of other offers. When marking up aggregate offers within a product, use the following properties of the schema.org AggregateOffer type:

Properties
lowPrice

Number, required

The lowest price of all offers available. Floating point number.

|
| highPrice |

Number, recommended

The highest price of all offers available. Floating point number.

|
| priceCurrency |

Text, required

The currency used to describe the product price, in three-letter ISO 4217 format.

|
| offerCount |

Number, recommended

The number of offers for the product.

|

https://developers.google.com/search/docs/data-types/product

**Just 1 **

Product rich results provide users with information about a specific product, such as its price, availability, and reviewer ratings. The following guidelines apply to product markup:

• Use markup for a specific product, not a category or list of products. For example, “shoes in our shop” is not a specific product. See also our structured data guidelines for multiple entities on the same page.
• Adult-related products are not supported.
• Reviewer’s name needs to be a valid name for a Person or Team For example, "James Smith" or"CNET Reviewers." By contrast, "50% off on Black Friday" is invalid.

To include product information in Image Search, follow these guidelines for required markup:

• To show your product information in the rich image viewer: Include the name, image, price, and priceCurrency properties. Alternatively, instead of price and priceCurrency, you can include any four properties and exclude price.

• To show your product information in the Related Items feature: Include the name, image, price, priceCurrency, and availability properties.

• Be careful that the text you use is the same text that is on the page

• https://searchengineland.com/spammy-structured-markup-penalty-recovery-use-schema-markup-caution-223289

• https://moz.com/blog/json-ld-for-beginners

• https://www.distilled.net/resources/understanding-and-implementing-json-ld/

• https://yoast.com/rich-snippets-product-listings/

• http://www.remicorson.com/add-woocommerce-product-to-cart-from-url-using-products-sku/

/*

• Remove the default WooCommerce 3 JSON/LD structured data format
  */
  function remove_output_structured_data() {
  remove_action( 'wp_footer', array( WC()->structured_data, 'output_structured_data' ), 10 ); // Frontend pages
  remove_action( 'woocommerce_email_order_details', array( WC()->structured_data, 'output_email_structured_data' ), 30 ); // Emails
  }
  add_action( 'init', 'remove_output_structured_data' );

[4RS_John]

Thanks Thomas.

AggregateOffer is what I was looking for.

[BlueprintMarketing]

Anytime, John, I am happy to help!

[LGist]

I have a question about the offerCount item within an AggregateOffer type.

I want to show the "true" price range of every product in our inventory but we don't automatically load them all to the page. Most implementations I have seen that trigger the price range showing in the SERP have the individual offers marked up further down the page as well, but that wouldn't work for us. We show 10 or so out of 100s.

In my mind there are two options here. We can use the true aggregate price of the set and skip tagging up individual offers. Or we can tag up the offers displayed but still show what I am calling the "true" aggregate price. Any opinions on whether Google needs the individual offers tagged up? And any opinions on whether the individual offers tagged up need to "match" the aggregate offer prices?

THANKS