The short answer
Product and Offer schema should describe the exact item on the page with visible, current facts such as name, image, brand, price, currency, URL, condition, and availability.
Business outcome
Machines get a clearer version of the same commercial facts buyers see, while your team gains a QA process for price and availability drift.
The process
Build it in five passes
Choose a true product page
Use markup on a page focused on one purchasable product, plan, or clearly defined offer. Do not force Product onto a generic homepage, category essay, or lead-generation service page without checking the applicable search and schema guidance.
Map visible commercial facts
Record the product name, description, canonical URL, primary image, brand, SKU or identifier when real, price, currency, availability, and condition. Capture variants and ranges carefully rather than collapsing them into a misleading single price.
Build the smallest complete object
Use Product with a nested Offer when the page exposes a specific current offer. Choose properties supported by the page and Google's documentation. Never add aggregate ratings or reviews that are absent, ineligible, or written by the seller as fake customer proof.
Connect inventory updates
Price and availability are operational data, not set-and-forget copy. Generate markup from the same trusted source as the visible page whenever possible, and define an alert for mismatches.
Validate and monitor
Test the JSON-LD, compare it manually with the rendered page, inspect the canonical and indexing state, and monitor structured-data reports. Valid markup is eligibility information, not a guarantee of rich display, citation, or recommendation.
Before it ships
Quality checklist
- The page represents one clear product or purchasable offer.
- Name, image, price, currency, and availability are visible to users.
- Product identifiers are real and stable rather than invented for markup.
- Variants and price ranges are represented without hiding conditions.
- Review or rating fields meet applicable policies and visible evidence.
- Markup and page draw current commerce facts from the same source.
Copyable artifact
Product with Offer JSON-LD starter
Use only for a page and offer that meet the applicable rules. Replace placeholders and delete fields your page does not support.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"@id": "https://www.example.com/products/example/#product",
"name": "Example Product",
"description": "A factual description that matches the page.",
"image": ["https://www.example.com/images/example-product.jpg"],
"sku": "EXAMPLE-001",
"brand": {
"@type": "Brand",
"name": "Example Brand"
},
"offers": {
"@type": "Offer",
"url": "https://www.example.com/products/example/",
"priceCurrency": "USD",
"price": "49.00",
"priceValidUntil": "2026-12-31",
"availability": "https://schema.org/InStock",
"itemCondition": "https://schema.org/NewCondition"
}
}
</script>Validation
How you know it is ready
- 01The production JSON-LD parses and matches the visible product page line by line.
- 02A price or inventory change updates both page and markup together.
- 03Google's relevant structured-data validation shows no critical errors.
Do not overclaim
Product markup is designed for product information and search features. It is not required for generative AI search and does not guarantee visibility. Service businesses should confirm that the type and page are genuinely appropriate.
Questions
What teams usually ask
Can a service use Product schema?
Schema.org can represent some services and offers, but Google feature eligibility has specific requirements. Choose types based on what the page truly offers, not which result looks most attractive.
Can I add a review score from another site?
Do not copy or invent review markup casually. Follow the applicable structured-data policies and make sure any rating shown is eligible, attributable, and visible on the page.
How often should Offer data be checked?
Whenever price or availability can change. Ideally both visible page and markup are generated from the same trusted commerce source.
Sources reviewed