JSON-LD structured data

What is measured

The scanner extracts every <script type="application/ld+json"> block from the homepage /, parses it as JSON and walks the graph, including members of @graph. Pass when at least one block is valid JSON and declares @context https://schema.org plus an @type that names the page entity (WebSite, Organization, Article); partial when a block exists but is invalid JSON, or parses yet has no @context or no @type; fail when the page has no JSON-LD block at all.

Reproduce it yourself

You do not have to take our word for any of this. Run the same measurement against your own domain:

              DOMAIN="https://example.com"
curl -sL "$DOMAIN/" | perl -0777 -ne 'while (m{<script[^>]*application/ld\+json[^>]*>(.*?)</script>}gsi) { print "$1\n" }' | jq -r '[(."@context"? // empty | tostring)] + [.. | objects | select(has("@type")) | ."@type" | tostring] | unique | @tsv'
            

The fix

This is the artifact to ship. It is the complete change, not a description of one.

              <script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "Acme Agent Readiness",
  "url": "https://www.example.com/",
  "description": "Audits how well a website serves autonomous AI agents.",
  "publisher": {
    "@type": "Organization",
    "name": "Acme",
    "url": "https://www.example.com/",
    "logo": "https://www.example.com/logo.svg"
  }
}
</script>
            

Standards referenced

• schema.org

Related checks