Product structured data does the same job an in store price tag does. Without it, a search engine has to infer price and availability from whatever text happens to sit near the product name, which is unreliable on a page with several variants, a sale price and a strikethrough original price all in view at once. The markup states each fact once, unambiguously, in a place built for machines to read.
The form runs entirely in your browser. Draft pricing for a product that has not launched can be turned into markup without it ever leaving your machine before you are ready to publish.
The properties Google actually requires for product rich results
Google's own guidance is narrower than the full schema.org Product vocabulary. To be eligible for a rich result at all, a Product needs a name, and at least one of an offer or a review or rating. An offer in turn needs a price, a priceCurrency using a three letter ISO code, and an availability value drawn from schema.org's fixed list such as InStock or OutOfStock.
Everything else, a detailed description, a brand, a SKU, is useful for shoppers and for other systems that read the same markup, but is not what gates eligibility for the price and rating display in search. This generator marks the required fields so you can see at a glance what is load bearing and what is optional polish.
Aggregate rating versus a single review
A star rating in a rich result comes from either an aggregateRating summarising many reviews, or a single embedded review, never from a number you simply assert without evidence backing it. aggregateRating needs a ratingValue and a reviewCount or ratingCount, and the ratingValue must be a genuine average of real customer feedback collected on your own site or through a review platform you use.
Do not populate an aggregateRating with an invented score to make a new product look established. Google's structured data guidelines explicitly treat fabricated or incentivised reviews as a policy violation, and it is also simply false advertising to a shopper who trusts the stars they see next to your listing.
Availability values this product schema generator supports
The availability property accepts a fixed set of schema.org values rather than free text, since a search engine needs to match it against a known list to decide how to render stock status. The common values are InStock, OutOfStock, PreOrder, Discontinued and LimitedAvailability, and this tool exposes them as a dropdown so a typo cannot silently produce an availability value nothing recognises.
Keep this value current. A product marked InStock in the markup that is actually sold out is a mismatch between your structured data and your page that erodes trust in every other claim the markup makes, and can trigger a manual review of your Merchant Center feed if you run one alongside your organic listing.
- InStock: available to purchase and ship or fulfil now.
- OutOfStock: currently unavailable, expected to return.
- PreOrder: orderable now, ships on a future date.
- Discontinued: no longer sold and not expected to return.
- LimitedAvailability: in stock but in short supply.
Currency codes and why a symbol is not enough
priceCurrency must be a three letter ISO 4217 code such as USD, EUR or GBP, not a symbol like $ or £. A symbol alone is ambiguous, since a dollar sign is shared by more than twenty currencies, and structured data has no room for the kind of contextual guessing a human reader does automatically from the page's language or the seller's country.
This generator validates the currency field against the ISO code shape before building the output, catching the common mistake of pasting a symbol or a lower case currency name into a field that needs an exact three letter code.
How this product schema generator handles the product image
The image property should be an absolute URL pointing at a real product photograph, ideally one that also satisfies Google's general image guidelines for size and format. A relative path breaks in the same way it does for every other URL property in structured data, since JSON-LD carries no base URL of its own to resolve it against.
If a product has several photographs, supplying the single most representative one here is sufficient for eligibility. Additional images belong in the page's own markup or an image sitemap rather than being crammed into a single image property that only accepts one canonical picture per product.
How to generate product schema
- 1
Enter the product name and image
Add the product's name and an absolute URL to its main photograph.
- 2
Add price and availability
Enter the price, a three letter currency code and pick the current availability from the list.
- 3
Add a rating if you have real reviews
Enter an aggregate rating value and review count only if it reflects genuine customer feedback.
- 4
Generate and paste
Press generate, review the warnings, then copy the script tag into the product page.
Related tools worth bookmarking
Sources and further reading
- schema.org: ProductThe vocabulary definition for Product, Offer and AggregateRating.schema.org
- Google Search Central: Product structured dataGoogle's required and recommended properties for product rich results, including availability values.developers.google.com
- W3C: JSON-LD 1.1The specification for the serialisation format this tool emits.w3.org
Frequently asked questions
Common questions about the product schema generator.
Google requires a name plus at least one offer or review. An offer in turn needs a price, a three letter ISO currency code and an availability value from schema.org's fixed list. Everything else improves the markup but is not what gates rich result eligibility.
No. aggregateRating must reflect real customer feedback with a genuine review count behind it. Google's structured data guidelines treat fabricated ratings as a policy violation, and it misleads the shopper reading your listing, so a brand new product with no reviews should simply omit the rating entirely until it has some.
priceCurrency requires a three letter ISO 4217 code such as USD or EUR because a symbol like $ is shared by more than twenty currencies worldwide and is ambiguous without extra context a machine parser does not have. This generator validates the field to catch that mistake before you publish.
The markup keeps showing whatever value it had at the time you published it, since nothing updates it automatically. A page claiming InStock that is actually sold out is a mismatch that damages trust in the rest of your structured data, so update the value whenever real stock status changes.
It needs to be a real, absolute URL that resolves to an actual product photograph, but it does not strictly need to be on your own domain, provided the image is publicly accessible and stays available. Hosting it yourself is still the safer choice since a third party image can move or disappear without notice.