Product schema generator for any PDP.
When an AI agent parses your product page, the JSON-LD is the part it trusts. Most themes emit name and price and stop. Paste a product URL: the generator reads the page, detects what schema exists, and produces the complete block — GTIN, brand, material, offers, aggregateRating — with nothing invented.
Rate limit: 1 run per 30 seconds per IP. Missing data is flagged, never fabricated.
The fields, and why engines weigh them
| Field | What it does for AI visibility | Background |
|---|---|---|
gtin / sku | Disambiguates your product from lookalikes and ties it to review and retail data across the web. The single most under-populated field on Shopify PDPs — map it from the barcode field. | Schema for AI search |
brand | Entity clarity: connects the SKU to the brand entity engines already know, so answers attribute the product correctly. | AI brand visibility |
offers — price, availability, url | The machine-readable line a shopping agent needs before it can draft the product into a cart. Blank availability breaks agent flows. | Agentic commerce |
material, color | Attribute coverage for the qualified queries that convert — "merino," "BPA-free," "matte black." Engines match attributes, not vibes. | Product AI visibility |
aggregateRating | Review signal engines surface directly in answers. Only generated when real review data exists on the page — never fabricated. | AI sentiment |
Shipping the block
For Shopify: paste into the product template — sections/main-product.liquid in most OS 2.0 themes, or a snippet included from it — wrapped in <script type="application/ld+json">. If the theme already emits Product JSON-LD, replace it instead of stacking a second block; duplicate Product entities on one page make parsers pick one arbitrarily. For headless builds, render the block server-side so crawlers that skip JavaScript still see it. Validate the deployed page with Google's Rich Results Test.
The generator's discipline is worth stating plainly: it never invents data. A missing GTIN stays missing and becomes a finding telling you to populate the Shopify barcode field; a product with no reviews gets no aggregateRating. Schema that claims things the page cannot support is worse than thin schema — engines cross-check, and inconsistency costs trust. The gap between "schema exists" and "schema an engine can act on" is where most PDPs lose citations; the schema for AI search guide covers the full field-by-field reasoning, and the Product schema glossary entry defines the terms.
One URL at a time is right for audits and hero products. For the catalog, the PDP optimization workflow in the paid product generates schema per SKU from your live data, diffs it against what each PDP currently emits, and pushes approved changes to Shopify — see the fix product schema walkthrough.
Ask AI about the schema generator
Have your favorite AI engine explain Product schema for your catalog.
Frequently asked questions
My theme already outputs Product schema. Why generate more?
Which fields does the generator produce?
Does richer Product schema actually affect AI citations?
Where do I paste the generated block in a Shopify theme?
sections/main-product.liquid in most OS 2.0 themes — inside a <script type="application/ld+json"> tag, replacing any existing Product block rather than adding a second one. Validate with Google's Rich Results Test after deploying.What about variants — one schema block or many?
One block free. Every product, diffed and pushed, on the paid plan.
eCommerce Insights generates, validates, and ships schema across the catalog — with a human approving every change.