aide
← Back to Learn
content

Schema.org JSON-LD

Does the homepage embed at least one well-formed JSON-LD block describing the site, org, or key content?

What it is

Schema.org is the vocabulary, and JSON-LD (<script type="application/ld+json">) is the serialisation. For agents, structured data is one of the cheapest ways to extract ground truth from a page — name, author, date, offer, rating, breadcrumbs — without parsing prose.

This is an aide extra (weight 2, in Content category) because it's broadly useful and broadly missing.

Remediation Prompt

I want to improve my site's agent readiness. Please implement the following fix for Schema.org JSON-LD across our codebase.

Instructions:
Please fix the Schema.org JSON-LD issue on my site so it is agent-ready.

How we test it

  1. GET / with Accept: text/html
  2. Parse HTML with Cheerio, extract every <script type="application/ld+json"> content block
  3. Parse each as JSON, validate against known schema types

Pass Warn Fail Matrix

Condition Status Score
≥1 block present, parses, has recognisable @type (Organization / WebSite / Article / Product / BreadcrumbList / …) pass 1.0
Present but malformed JSON in at least one block warn 0.5
None present fail 0.0

Sub Tests

id Weight Pass when
ld-json-present 0.5 ≥1 script block
valid-json 0.25 All present blocks parse
known-type 0.25 At least one block has a @type from the core Schema.org vocabulary

Remediation Prompt

Please add at least one Schema.org JSON-LD block to my homepage. For a typical company site, include WebSite + Organization:

    <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "WebSite",
      "name": "Example",
      "url": "https://example.com/"
    }
    </script>

    <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "Organization",
      "name": "Example Inc.",
      "url": "https://example.com/",
      "logo": "https://example.com/logo.png",
      "sameAs": ["https://twitter.com/example", "https://github.com/example"]
    }
    </script>

For article/blog pages, add Article or BlogPosting. For product pages, Product with Offer. Keep one block per logical entity; do not stuff unrelated types together.

References

Test Fixtures

  • pass-website-organization.html
  • warn-malformed-json.html
  • fail-none.html
← Previous Check
RSS / Atom Feeds
Next Check →
security.txt (RFC 9116)
Schema.org JSON-LD — how to make your site agent-ready | aide