What Product Schema means
It's usually paired with a nested Offer containing the commercial details. Together they state unambiguously what the product is and what it costs right now.
For catalogs it's deployed at template level, so fixing the product template fixes every product built on it.
Why it matters for AI search
AI shopping answers assemble from structured product data more than from prose. Incomplete or stale markup means exclusion from those answers regardless of brand strength.
Accuracy matters more than coverage here. Stale prices actively erode trust in all your structured data and can affect merchant listing eligibility.
See it in action
Catalog-wide markup coverage and what it changes.
Products with full markup
What changes
Coverage and accuracy are two different problems.
Most catalogs have some Product schema. Far fewer have complete markup wired to live inventory data, and that's the difference between eligible and excluded.
How to get it right
Deploying Product schema properly
- Deploy at template level rather than page by page
- Include brand, identifiers (GTIN/MPN/SKU), condition and availability, not just name and price
- Wire price and availability to live source data so they never drift
- Only include AggregateRating where genuine reviews exist
- Validate continuously and monitor for breakage after deploys
Common questions
Is Product schema required for AI shopping answers?
Not strictly, but its absence is a severe handicap. Those answers assemble largely from structured data, so incomplete markup means exclusion.
What happens if our prices are stale in schema?
Beyond misleading shoppers, persistent mismatches can cause structured data to be distrusted or ignored, and can affect merchant listing eligibility.
Can we add ratings if we don't have reviews?
No. Marking up ratings that don't exist is a structured data policy violation and a real manual action risk.
Related concepts
These come up alongside Product Schema constantly.