Choose one real product
Use its canonical product URL, current image, visible description, price, currency and stock state.
Turn the visible facts on a real product page into machine-readable Product and Offer data. Build the markup, understand every field, and validate it before publishing.
Build an example →Product structured data is a JSON-LD description of an individual product page. It can identify the product, brand, image, SKU and current offer. It does not replace the content shoppers see; it must describe the same information.
Only publish values that are current, visible and verifiable on that product page. Never create a review, rating, discount, price or availability state merely to make the markup look complete.
This browser-based helper does not upload or store the values you enter. Replace the example data with one real product, then give the output to the person who manages your storefront.
This v1 builder intentionally excludes reviews and aggregate ratings. Add them only when your implementation meets the relevant eligibility and accuracy requirements.
Passing a validator is a technical check, not a guarantee of a rich result. Search engines decide eligibility and presentation.
Use its canonical product URL, current image, visible description, price, currency and stock state.
Make every generated value agree with what a shopper can see on the page.
Add the script to that product template through your platform, theme, plugin or development team.
Validate the deployed page, correct errors, and recheck whenever the catalogue template changes.
After implementation, test the public product URL. A copied example can be syntactically valid while still being inaccurate for your store.
This independent ECIndex learning guide draws on publicly available documentation from Google Search Central and the Schema.org Product specification. These are authoritative external references. ECIndex is not affiliated with, sponsored by or endorsed by Google or Schema.org.