agentspeed.
← all tools
Tool

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.

Tool
›
https://github.comHTTP 200

Type coverage

path /

! Organization! WebSite~ BreadcrumbList· Product· Article· FAQPage

✓ detected · ! missing critical · ~ recommended for this page kind · · not relevant

No JSON-LD blocks found on the page.

Agents prefer JSON-LD over Microdata or RDFa. Use the snippets below to add the schemas this page should declare.

Recommended snippets

Organizationcritical

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": "Github",
  "url": "https://github.com",
  "logo": "https://github.com/logo.png",
  "sameAs": [
    "https://twitter.com/github",
    "https://www.linkedin.com/company/github"
  ]
}
</script>
WebSitecritical

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": "Github",
  "url": "https://github.com",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://github.com/search?q={search_term_string}",
    "query-input": "required name=search_term_string"
  }
}
</script>
BreadcrumbListrecommended

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://github.com"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Section",
      "item": "https://github.com/section"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "This page",
      "item": "https://github.com/"
    }
  ]
}
</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.

Examples

Click an example to run the tool with pre-filled inputs.

Why this matters for AI agents

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.

Common fixes
Missing Organization
Add an Organization block in your <head> on every page. Includes name, url, logo, and sameAs links to your social profiles. Snippet generated below when missing.
Missing WebSite with SearchAction
The WebSite schema with a potentialAction of SearchAction enables the search box in agent results. Snippet generated below.
Product without priceCurrency
Offer requires both price and priceCurrency. Without currency, agents cannot answer pricing queries correctly across markets.
FAQPage without mainEntity
FAQPage needs a mainEntity array of Question objects, each with an acceptedAnswer of type Answer. Plain-text answers only, no HTML.
BreadcrumbList without ListItem positions
Each itemListElement needs a numeric position, plus name and item(URL).
Linked rubric checks
FAQ
What's the difference between Organization and Person schema?
Organization describes a company or non-profit. Person describes an individual (an author, a public figure). Most sites need Organization. Personal blogs and portfolio sites use Person. They are not interchangeable.
Do I need both schema.org and Open Graph?
Yes. They are read by different consumers. schema.org / JSON-LD is read by AI agents, Google for rich results, and structured-data-aware crawlers. Open Graph / Twitter Cards are read by social platforms for link previews. They overlap a little but neither replaces the other.
Why does Google show some types and not others?
Google only renders rich results for a subset of schema.org types and only when its quality bar is met. AI agents are less restrictive, and they read every well-formed block. So even types Google ignores (e.g. Service, Course) are useful for agent visibility.
Does invalid JSON-LD hurt SEO?
Indirectly. Google ignores invalid blocks for rich results. Other crawlers may try to parse and discard. The bigger cost is lost agent visibility: a partially-broken Organization block means agents fall back to text inference for the publisher name.
Can I have more than one Organization block?
Yes, but limit it to one canonical Organization for the publisher. Subsidiary or parent organisations should use subOrganization or parentOrganization properties on the canonical block, not separate sibling Organization entries.
Run a full agent-readiness scan
Full scan

Score the entire site against 30 agent-readiness checks across discoverability, readability, structured data, actionability, and performance.

Get the full report for github.com →