Free Offer Schema Generator

What is Offer structured data?

An Offer describes the terms for getting something: the price, the currency, whether it is in stock, its condition, and who sells it. It is never the main thing on the page. You place it in the offers property of the item being sold:

• Product: the price and stock shown in Google's product snippets and merchant listings.
• Event: ticket price, ticket availability, and when tickets go on sale.
• Course and SoftwareApplication: what the course or app costs.

Because Google reads Offer through those parent types, there's no separate "Offer rich result." Getting Offer right is what makes the price and availability in your Product or Event markup usable.

Required and recommended properties (merchant listings)

Google's merchant listing documentation requires two things on every Offer:

• price: the current price as a number, for example 199.00. You can put it in priceSpecification.price instead.
• priceCurrency: the three-letter ISO 4217 code, such as USD, EUR, or GBP.

Google recommends adding:

• availability: a schema.org value such as https://schema.org/InStock, OutOfStock, or PreOrder.
• itemCondition: NewCondition, RefurbishedCondition, or UsedCondition.
• priceValidUntil: the date the price stops applying, for example the last day of a sale.
• url: the page where people can buy the item.
• shippingDetails: shipping cost and delivery time, using OfferShippingDetails.
• hasMerchantReturnPolicy: return window and fees, using MerchantReturnPolicy.

Price rules that trip people up

• Numbers only. Write 1299.99, not "$1,299.99". The currency goes in priceCurrency, never in the price.
• Merchant listings need a price above zero. Product snippets accept a price of 0, but merchant listings don't.
• Match the page. The price, currency, and availability in your markup must be what the visitor sees. If the page shows a sale price, the markup shows the sale price.
• One currency per Offer. priceCurrency names the currency of that Offer's price, so a price in another currency needs its own Offer.

Showing a sale price

To show a reduced price with the original price crossed out, use priceSpecification with two entries:

1. The active sale price, with no priceType.
2. The original price, with priceType set to https://schema.org/StrikethroughPrice.

Google's docs are explicit that the active price must not carry a priceType. See the "Sale price with a strikethrough price" example on this page.

Offer vs. AggregateOffer

• Use Offer when you are the one selling the item. Merchant listings require an Offer, because the merchant has to be the seller.
• Use AggregateOffer on a page that compares several sellers, with lowPrice, highPrice, priceCurrency, and optionally offerCount. Product snippets accept it; merchant listings don't.

Offers on events

Event ticket offers use the same type with event-specific guidance. Google recommends:

• price: the lowest available ticket price, including service charges and fees
• priceCurrency: the three-letter currency code
• availability: InStock, SoldOut, or PreOrder
• validFrom: when tickets go on sale, if sales start on a set date
• url: the page where people buy tickets

How to build an Offer here

Common errors and fixes

• Price written as text: the price contains a currency symbol, a comma, or words. Use a plain number.
• Missing priceCurrency: every Offer needs a currency, even when the page only uses one.
• Price in the markup doesn't match the page: update both together, especially when a sale starts or ends.
• Out-of-stock items marked InStock: keep availability in sync with your inventory.
• AggregateOffer on your own product page: if you are the only seller, use Offer so the page can qualify for merchant listings.
• Offer with no parent item: an Offer on its own describes nothing. Nest it under the Product or Event it belongs to.