Price and availability are the two facts an AI answer about a product cannot guess. A model that recommends a product has to say what it costs and whether the shopper can buy it. You state both facts in the Offer block inside your Product markup, using the price, priceCurrency, and availability properties. When those three fields match the visible page and update when inventory changes, an AI system can quote your price and your stock status with confidence. When they are missing, stale, or different from the page, the system either skips your product or quotes a price you no longer charge.
This guide covers the Offer fields that carry price and stock. For the full Product block, including name, image, brand, and identifiers, see our product schema guide.
What the Offer block holds
An Offer is a schema.org type nested inside a Product. It describes one commercial offer for that product: the price a shopper pays, the currency, the condition, and whether the item is available. Google splits product markup into two uses, product snippets for pages where people cannot buy directly, and merchant listings for pages where they can. Merchant listings are the use that matters here, because they are the pages where a shopper can purchase. For a merchant listing, Google requires a Product with a name, an image, and an Offer with a price above zero and a three-letter priceCurrency. Availability is recommended, not required, but for AI answers it is the field that decides whether a recommendation is useful. A price with no stock status leaves the next question unanswered.
Price is a plain number, with no currency symbol, no thousands separator, and no range. The currency goes in priceCurrency as a three-letter code, such as USD. A price without a currency is a number, not a fact, because the same digits mean different amounts in different currencies. If you sell in more than one currency, each currency needs its own Offer, and each Offer needs its own URL.
The complete Offer block
Here is a full JSON-LD block for a bicycle accessories store. In the example, [yourdomain.com] is a placeholder, replacing yourdomain.com with your actual domain. The store is fictional, and the values are teaching samples for your own store, not real prices.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Cascade Rear Rack",
"image": [
"https://[yourdomain.com]/images/cascade-rear-rack.jpg"
],
"description": "Steel rear rack for city and touring bikes, rated for panniers and a top bag.",
"sku": "HBR-RACK-01",
"brand": {
"@type": "Brand",
"name": "Harbor Cycle Works"
},
"offers": {
"@type": "Offer",
"url": "https://[yourdomain.com]/products/cascade-rear-rack",
"price": "64.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"itemCondition": "https://schema.org/NewCondition"
}
}
</script>
Field by field:
- offers.price: the current selling price, as a plain number. This is the price a shopper pays now, not the original price and not a range.
- offers.priceCurrency: the three-letter currency code for the price. Always include it. Google requires it for merchant listings.
- offers.availability: one schema.org ItemAvailability value, written as a full URL, such as https://schema.org/InStock. The common values are InStock, OutOfStock, PreOrder, BackOrder, Discontinued, LimitedAvailability, SoldOut, InStoreOnly, OnlineOnly, and PreSale. Pick exactly one value, the one that matches the page today.
- offers.url: the canonical URL of the product page the offer belongs to. If a variant has its own URL, that variant gets its own Offer with its own URL. See our guide to marking up product variants.
- offers.itemCondition: NewCondition, UsedCondition, or RefurbishedCondition. Include it, because an AI system uses it to filter, and a used item priced as new is a mismatch.
- sku and brand: identifiers that keep this product consistent across your site and your feed. Keep the name and the SKU identical in the markup, on the page, and in the feed.
Sale prices: the active price and the struck-through price
A sale has two prices, and the markup has to keep them apart. The active price, the price a shopper pays now, goes in offers.price. The original price, the higher price the product normally sells for, goes in a priceSpecification of type UnitPriceSpecification, with priceType set to https://schema.org/StrikethroughPrice. Do not put the original price in offers.price and the sale price somewhere else. Google documents this pattern in its merchant listing guide, and it is the pattern that lets a system show both numbers without confusing them.
"offers": {
"@type": "Offer",
"url": "https://[yourdomain.com]/products/cascade-rear-rack",
"price": "64.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"itemCondition": "https://schema.org/NewCondition",
"priceSpecification": {
"@type": "UnitPriceSpecification",
"priceType": "https://schema.org/StrikethroughPrice",
"price": "79.00",
"priceCurrency": "USD"
}
}
Do not mark the active price with a priceType. The active price has no priceType. The struck-through price carries the StrikethroughPrice type, and nothing else does.
Sale end dates and availability windows
A sale price needs an end. Google documents three properties for this, all in ISO 8601 form. Use validFrom for the start of the sale, and use either validThrough or priceValidUntil for the end. Put both a start and an end on the sale so the period is clearly defined, and put them on the Offer node when the price on that node is the sale price. In the teaching sample below, YYYY-MM-DD is a placeholder. Replace it with the real end date of your sale, in the same form, and remove the placeholder before you publish.
"priceValidUntil": "YYYY-MM-DD"
A priceValidUntil value in the past is a live problem. Google warns that a listing may not display when priceValidUntil indicates a past date, so a sale that ended last week with its end date still in the markup can hide the product. When a sale ends, update the price back to the regular price and remove the sale fields in the same change. Do not leave a sale price in the markup after the page has returned to the regular price.
Availability has its own timing. PreOrder means the product can be ordered before it is in stock. BackOrder means it can be ordered while it is out of stock and will ship later. OutOfStock means it cannot be ordered. SoldOut and Discontinued are stronger: the product is gone, and Discontinued means it will not return. Use the value that matches what the shopper can actually do on the page. If the page says out of stock but the button still takes an order, the page and the markup disagree, and the markup should follow the page.
What happens when price or stock changes
Markup goes stale in three common ways, and each one has a fix.
The price changed and the markup did not. This is the most damaging failure. Google treats markup that does not match the visible page as a true representation problem, and a mismatch between markup and page creates conflicting facts for any AI system reading both. Generate the markup from the same data that renders the page, never from a separate feed or a hand-edited copy. One source of truth, rendered in two places, cannot drift.
The item sold out and the markup still says InStock. The shopper follows a recommendation to a product that cannot be bought. Update availability in the same step that updates inventory, not as a later cleanup task. If your platform updates inventory automatically, check that the markup is generated from that same inventory value.
The sale ended and the markup still shows the sale price. The system quotes a price the shopper cannot get at checkout. Tie the sale end to the same change that restores the regular price on the page, and check the markup on the first page you change.
Validate before you ship
Two free tools, no signup, and they check different things:
- Google's Rich Results Test: paste a product URL and it shows which product fields Google detects, with errors and warnings per field.
- The Schema Markup Validator: checks the JSON-LD against the schema.org vocabulary itself, which catches typos in property names that Google's tool may not flag.
Run both on a handful of product pages, including one product on sale, one out-of-stock product, and one pre-order product. The out-of-stock check matters most: your availability values have to change when inventory does, and neither validator will tell you the value is stale. Only a read of the page against your inventory can do that.
Say you run a bike shop with a sale rack
Say you run a small bike accessories store. You put a rear rack on sale, and the page shows the sale price, the original price struck through, and an in-stock badge. Your markup says the same three facts: offers.price holds the sale price, the priceSpecification holds the original price with the StrikethroughPrice type, and availability says InStock. An AI system asked for a rear rack under a budget can quote the sale price and confirm it is available.
Then the rack sells out. The page badge changes to out of stock, but the markup is cached and still says InStock. The next AI answer sends a shopper to a product that cannot be bought, and the shopper learns not to trust the next recommendation from your store. The fix is not more markup. It is one source of truth: the inventory value that renders the badge also renders the availability field, in the same change.
Common mistakes
A price range in a single Offer. A product with variants at different prices does not get one Offer with a range. Each variant gets its own Offer with its own price. See our guide to marking up product variants.
A currency symbol in the price. The price is digits only. The currency lives in priceCurrency. A price of $64.00 in the markup is a string a parser has to clean up, and some parsers will not.
AggregateOffer for a single product. AggregateOffer describes one product sold by multiple sellers, with lowPrice and offerCount. It is not a way to show a price range for one seller. A single seller with one product uses a single Offer.
Availability left blank or set to a made-up value. The value must be one of the schema.org ItemAvailability values, written as a full URL. A value such as Available or In Stock Now is not in the vocabulary and will not be read as stock status.
Markup on the wrong page. Offer markup belongs on the product page it describes. Putting it on a category page or the homepage creates a price with no product page behind it.
What this guide does not cover
This guide covers the price and availability fields in the Offer block. It does not cover marking up variants, which is our guide to product variants, or marking up reviews, which is our guide to review schema, or fixing the case where the same product shows different prices in different places, which is our guide to fixing conflicting product data. It also does not cover keeping prices accurate as inventory changes over time, which is monitoring work, or turning a recommendation into a completed purchase, which is the transaction layer.
Check your own brand now
Run the free scan. It takes seconds, no signup, and shows whether AI crawlers can read your product pages today: aizii.ai/aeo-scan
Run the free scanSources
- Google Search Central, Merchant listing structured data (specific): https://developers.google.com/search/docs/appearance/structured-data/merchant-listing
- Google Search Central, Product structured data (specific): https://developers.google.com/search/docs/appearance/structured-data/product
- Schema.org, Offer type (general standard): https://schema.org/Offer
- Schema.org, ItemAvailability type (specific): https://schema.org/ItemAvailability
- Google Rich Results Test (general docs): https://search.google.com/test/rich-results
- Schema Markup Validator (general docs): https://validator.schema.org/
Note: links marked specific point to the page that supports the claim in this guide. Links marked general docs point to the vendor's general docs section for that topic, not to a page that proves every step. Check the vendor docs for the current path before relying on a menu name or click path in this guide.
