Product Schema
Product schema marks up price, availability, and reviews so engines can quote them. Learn the required properties and why AI engines repeat what it says.
TL;DR
Product schema is the structured data type that describes an item for sale: its name, price, currency, availability and any aggregate rating. It turns commercial facts that were previously just text into values a machine can read directly. For AI visibility it is the highest-stakes markup on most sites, because price is the fact engines quote most often and get wrong most often.
Why Product schema matters
Pricing is the claim buyers act on and the claim engines repeat, so making it unambiguous protects revenue rather than just rankings.
- Price accuracy: A marked-up price is a labelled number. Prose pricing gets misread, misattributed, or pulled from a stale third-party page.
- Rich results: Price, availability and rating panels in search come directly from valid Product markup.
- Comparison answers: AI responses that compare vendors lean on structured pricing when it is available and guess when it is not.
- Availability signals: Stock status prevents engines describing discontinued items as purchasable.
How to implement Product schema
Mark the primary product only
One Product type per page. Related items belong in their own markup on their own pages, not stacked into one block.
Nest an Offer
Price, priceCurrency, availability and priceValidUntil live inside an Offer rather than on the Product directly.
State currency explicitly
A number without priceCurrency is ambiguous across markets and frequently misinterpreted.
Handle ranges honestly
For tiered pricing use an AggregateOffer with low and high values rather than picking one number that misrepresents the rest.
Only mark up real reviews
AggregateRating must reflect genuine reviews visible on the page. Fabricated ratings are a guidelines violation with real consequences.
Automate from the source of truth
Generate markup from the same data that renders the price, so a pricing change updates both at once.
Product schema vs. SoftwareApplication schema
Product schema: The general commerce type. Suits physical goods and most purchasable items, with price and availability inside an Offer.
SoftwareApplication schema: Built for software, adding properties like operatingSystem and applicationCategory alongside pricing.
SaaS pricing pages can validly use either, and many use both nested together. The deciding factor is whether the software-specific properties add real information for your product.
Markup states your price correctly; it does not stop engines repeating an old one from somewhere else. Findrix checks the facts you define across AI answers and the sources behind them, flags every mismatch, and names the page that produced it. Every gap comes with the fix already written: technical, content and off-site. The audit is free, takes about a minute, and requires no signup.
Required and recommended properties
- name: The product name as customers know it.
- offers: An Offer or AggregateOffer containing the commercial terms.
- price and priceCurrency: The number and its currency, always together.
- availability: In stock, out of stock, or preorder, using schema.org values.
- aggregateRating: Average score and review count, only where genuine reviews exist.
- image and description: Supporting detail that improves rich result eligibility.
Why pricing markup rarely fixes pricing errors
Teams add Product schema expecting AI engines to stop misquoting their prices, and are surprised when the wrong number keeps appearing. The reason is that engines assemble answers from many sources, and a review site with your old pricing often outranks your own page in their source selection.
Your markup makes your page authoritative and readable. It does nothing to the stale third-party page repeating an old figure, and that page may well be the one being cited.
Keep your own markup current so engines reading you get the right answer, then find the outdated third-party sources feeding the wrong one. Correcting the source is usually what changes the answer.
Frequently asked questions
Can I use Product schema for a SaaS pricing page?
Yes, and SoftwareApplication is the more specific alternative. Many SaaS sites nest both. What matters more than the type choice is that the price and currency are marked up and match what the page displays.
How do I mark up tiered or ranged pricing?
Use AggregateOffer with lowPrice, highPrice and priceCurrency. Marking a single tier as the price misrepresents the product and produces answers that quote a number most buyers will not pay.
Does Product schema stop AI engines quoting the wrong price?
It helps for engines reading your page directly, and does nothing about third-party pages carrying outdated figures. Since those are often the cited source, correcting them matters as much as fixing your own markup.