Paste a product URL, upload a row, or use an enriched Central record. Central returns Schema.org/JSON-LD, offer and product fields, x-central metadata where implemented, confidence, review state, and warnings for unsupported claims.
AI-readable product data · confidence on every fact · unsupported claims stay hidden
Hand-written JSON-LD often copies whatever is visible on the product page. If the page is thin or the claims are unsupported, the structured data repeats the same weakness in machine-readable form.
Most JSON-LD generators read the visible page, parse a title, a price, an image, paste it into a Product/Offer template, and ship. If the page hides a claim — "professional grade", "lab-tested", "lead-free" — the schema ships it too. AI shopping agents now consume the same data, with no human filter.
Central generates schema from the verified product record. Fields carry source and confidence internally, and unsupported claims are held before they become structured output.
You bring a product. Central returns JSON-LD grounded in the verified record, with the review state visible before you copy it into the page.
Every JSON-LD field maps to a Central action and a concrete set of properties. Verified evidence is the precondition for the property — not an afterthought.
AI drafts the schema from the verified record. Verification decides which fields ship. Operators review claims and warnings before the product page changes.
A product URL, row, or enriched record.
Available product, offer, and attribute fields.
Missing facts gathered and verified where supported.
Unsupported claims stay hidden or move into review.
JSON-LD and implementation notes for the page or widget.
The team reviews the output before publishing.
Left: the source panel — what Central knows about each field, with confidence and review state. Right: the JSON-LD preview the page or widget can ship.
Paste into the product page <head>. Re-pull when the canonical record changes.
Drop the Product Intelligence Widget on the PDP. Schema follows the published record automatically.
Request the JSON-LD payload from the Central API. Useful for headless storefronts and SSR pipelines.
Resolve held claims and conflicts in the Central queue. Each resolution updates the schema downstream.
One verified record. Five things the SEO / AIO lead, the developer, and the operator can use directly.
Schema.org preview ready to copy into the page head or push through the API.
Product attributes normalized into structured fields — color, weight, material, additional properties.
Where implemented — source count, confidence, verifiedAt — for downstream provenance context.
For the product page, widget, or developer handoff. What to paste, what to render, what to watch.
Warnings for missing required fields, conflicts, and unsupported claims — visible before publish.
Yes. The free tool can help with one product. Central connects schema generation to verified records and batch workflows when you are ready to take the same approach across the catalog.
Central generates structured data from verified facts, so search and AI surfaces receive a clearer, more trustworthy product record.
The JSON-LD preview highlights claim evidence, source state, and review status so the team can promote supported claims, rewrite weak claims, or keep the schema focused on verified facts.
Yes where the output is connected to Central. The page should show the schema as an output of the current verified record — re-published through the widget or API when the record updates, or re-exported on demand for hand-copied JSON-LD.