Engines can’t cite what they can’t parse. Make your pages legible.
Paste any URL — we detect the structured data you already have, flag what’s broken, and generate the exact copy-paste JSON-LD to fill every gap, pre-filled from your real content.
-
The present/missing matrix Every JSON-LD block on your page, parsed and validity-graded — beside the AEO types you don’t have.
-
Broken blocks, caught Malformed JSON, missing required properties, wrong @type — present-but-broken schema is flagged with the reason.
-
One generated block — free Your highest-impact missing type, written as complete JSON-LD from your page’s real content. Judge the quality before any email.
-
Every missing block · email-gated The full set of generated blocks, each code-validated with an install note — paste-ready, built only from facts on your page.
What it checks
- Every JSON-LD block already on your page — parsed, typed, and validity-checked
- The AEO-relevant types you’re missing — LocalBusiness, Organization, Service, Product, BreadcrumbList, WebSite
- Present-but-broken schema — missing required properties, wrong @type, malformed JSON
- Generates the missing blocks pre-filled from your page’s real name, services, and address — never placeholder text
What it won’t do
- Every generated block must parse as valid JSON and carry @context + @type, or it is dropped — broken schema is worse than none, so we never ship it.
- It reads the delivered HTML — schema injected later by JavaScript is a blind spot, and the report says so.
- No fabricated business facts. If your page doesn’t state it, the generated schema doesn’t claim it.
- No login, no card. The #1 missing block is free; the full set unlocks with a work email.
Before you run it
-
Is the generated JSON-LD actually valid?
Every block is parsed and validated in code before it renders — valid JSON, @context and @type present, pre-filled from your page. Paste it into your <head>, then confirm in Google’s Rich Results Test. Broken blocks are dropped, never shipped.
-
Will schema get me cited by AI engines?
Honest answer: schema makes your content machine-readable and eligible — nobody can promise citations, and the strongest independent study found no automatic lift. It is table stakes, not a guarantee. We say the same thing in the report.
-
What if I already have some schema?
That’s the point of the scan — we show what’s present, what’s broken, and what’s missing, each with evidence. The generator only fills the gaps; it never falsely claims a present type is missing.
-
Where do I paste the generated blocks?
Into your page’s <head>, inside a script type="application/ld+json" tag — the report ships per-type install notes and the Rich Results Test link to verify.
