JSON-LD structured-data validator
Paste a URL. We fetch the page, extract every <script type="application/ld+json"> block, and validate each against schema.org. Required + recommended fields are checked across 20 types. Copyable JSON-LD snippets are generated for missing schemas.
Type coverage
path /wiki/Schema.org
✓ detected · ! missing critical · ~ recommended for this page kind · · not relevant
Recommended snippets
Identifies the publisher behind the site so agents can attribute citations.
Drop this in your <head> on every page. Replace logo + sameAs with your real assets.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "En",
"url": "https://en.wikipedia.org",
"logo": "https://en.wikipedia.org/logo.png",
"sameAs": [
"https://twitter.com/en",
"https://www.linkedin.com/company/en"
]
}
</script>
Declares the site, supports SearchAction sitelinks, and anchors brand recognition.
Drop this in your <head>. The SearchAction enables Sitelinks search box in agent answers.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "En",
"url": "https://en.wikipedia.org",
"potentialAction": {
"@type": "SearchAction",
"target": "https://en.wikipedia.org/search?q={search_term_string}",
"query-input": "required name=search_term_string"
}
}
</script>
Helps agents understand the page hierarchy and link to parent sections.
Render per-page so the position values map to the actual hierarchy of the current page.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://en.wikipedia.org"
},
{
"@type": "ListItem",
"position": 2,
"name": "Section",
"item": "https://en.wikipedia.org/section"
},
{
"@type": "ListItem",
"position": 3,
"name": "This page",
"item": "https://en.wikipedia.org/wiki/Schema.org"
}
]
}
</script>
Watch this URL — get alerted when this changes
Turn this one-off check into a scheduled watch. We re-run it, diff the result, and alert you on a regression through the same channels as your agent alerts. Watches are a paid feature.
Manage watches at /watches. You’ll be asked to sign in if you haven’t already.
Click an example to run the tool with pre-filled inputs.
Agents prefer JSON-LD because it is typed and machine-parseable. Microdata and RDFa get ignored. Sites without Organization or WebSite schema lose brand recognition in agent answers, because agents have to infer the publisher from page text instead of citing a structured source.
AgentSpeed scores every site against three structured-data checks: structured_data.jsonld_present, structured_data.validates, and structured_data.type_coverage.
What's the difference between Organization and Person schema?
Do I need both schema.org and Open Graph?
Why does Google show some types and not others?
Does invalid JSON-LD hurt SEO?
Can I have more than one Organization block?
Score the entire site against 30 agent-readiness checks across discoverability, readability, structured data, actionability, and performance.
Get the full report for en.wikipedia.org →