7 supported types
WebPage, WebSite, Organization, Article, BreadcrumbList, FAQPage, and HowTo, each with its own required and recommended property set.
Schema markup
Generate markup from facts you can trace .
Pick a page and a type. Every property that gets emitted names the evidence it was copied from, and every property that does not gets a stated reason instead of an invented value.
Evidence to JSON-LD
Markup assembled from your page, not from a template.
The generator reads facts the product already stored, then reports exactly what it could and could not fill.
Three evidence sources
An audited page, a page from your content inventory, or a URL you paste — the pasted path fetched once through the safe-URL authority.
Property-level provenance
Each emitted property names the stored fact it came from, so a reviewer can check the markup against the page without guessing.
Conformance report
Required gaps and recommended suggestions are reported separately, stamped with the registry version that produced them.
Product truth
Conformance to a type, never a rich-result promise.
This illustrative frame mirrors normalized output. It is not a Rich Results test.
| Signal | What the product shows | Source |
|---|---|---|
| Emitted property | Copied verbatim from a named stored fact | First-party data |
| Required gap | No stored evidence, so the property is omitted with a reason | First-party data |
| Property selection | Chosen by AI, then checked for verbatim copying | AI interpretation |
How it runs
Deterministic assembly, bounded AI, safe serialization.
Cadence, source, and the serializer's guarantees stay visible beside every result.
On demand
Generation runs when you ask. Reopening a stored result is a read, and the audited-page path issues no outbound request at all.
Stored page facts
Facts come from your audit crawl or content inventory. A pasted URL is fetched once, bounded, and the HTML discarded after extraction.
Escaped on the way out
Output goes through a serializer that escapes every character that could break out of a script tag, so hostile page text stays inert.
What we don't doHonest limit Honest limit Honest limit
Three things this feature will never claim.
Every limit below is enforced in the product, not written on a disclaimer page.
Conformance, not rich results
Output conforms to schema.org's requirements for the type you selected. It is never a guarantee that Google will show a rich result, and no page here will say otherwise.
Omitted beats invented
A property with no stored evidence is omitted with a stated reason. Ratings, prices, reviews, authors, and dates are never fabricated — which is why an Article commonly reports a published-date gap.
Copy or download only
Markup is copied to your clipboard or downloaded as a file. It is never injected into your site, your CMS, or your tag manager.
Every limit below is enforced by the product, not a disclaimer.
Traceable markup
Ship markup you can defend line by line.
Create an account to generate from an audited page, or begin with a free site audit.