---
title: "Kit check json-ld | Agent Ready Checklist"
description: "Kit check json-ld: JSON-LD present and parseable. The command that runs it, the evidence it prints and what it cannot prove. It maps to AR-READ-08."
canonical: https://agentreadychecklist.com/kit/json-ld
site: "Agent Ready Checklist"
last_updated: 2026-11-05
section: "Kit"
---

# Kit check json-ld | Agent Ready Checklist

> Kit check json-ld: JSON-LD present and parseable. The command that runs it, the evidence it prints and what it cannot prove. It maps to AR-READ-08.

Source: https://agentreadychecklist.com/kit/json-ld
Site: Agent Ready Checklist
Last reviewed: 2026-11-05
Agent endpoints: https://agentreadychecklist.com/llms.txt (index), https://agentreadychecklist.com/openapi.json (API), https://agentreadychecklist.com/mcp (MCP server), https://agentreadychecklist.com/ask (search)
Access: https://agentreadychecklist.com/auth.md (no key). Pricing: https://agentreadychecklist.com/pricing.md (free).

# Kit check: JSON-LD present and parseable

The json-ld check of the Verify Kit: Extracts every <script type="application/ld+json"> block, parses each with jq and prints the @type values. The json-ld check tests this: JSON-LD present and parseable. It maps to AR-READ-08. Run it alone with --only=json-ld. On the pass fixture it reports: 1 block(s) parse; @type WebSite.

## Run it

```bash
curl -fsSL https://agentreadychecklist.com/kit/verify.sh | bash -s -- https://example.com --only=json-ld
```

```bash
node verify.mjs https://example.com --only=json-ld
```

## What it tests

Extracts every <script type="application/ld+json"> block, parses each with jq and prints the @type values.

## What it cannot prove

Does not validate against schema.org types or check the facts match visible text.

## Requirements it maps to

-   [AR-READ-08](https://agentreadychecklist.com/checklist/ar-read-08/)JSON-LD on key pages

## Evidence on the fixtures

The pass fixture

PASS 1 block(s) parse; @type WebSite

The js-only fixture

FAIL no application/ld+json block in the response

The 403 fixture

FAIL no application/ld+json block in the response

## The one-line sketch

The shipped script is more careful than this sketch, which shows the idea in one line of shell.

```bash
curl -s "$URL" | node -e "let h=require(\"fs\").readFileSync(0,\"utf8\");for(const m of h.matchAll(/<script[^>]*application\/ld\+json[^>]*>([\s\S]*?)<\/script>/g)){try{console.log(\"PASS\",JSON.parse(m[1])[\"@type\"])}catch{console.log(\"FAIL unparseable block\")}}"
```

## Sources

-   [w3.org/TR/json-ld11/](https://www.w3.org/TR/json-ld11/)read 2026-11-04

Last reviewed 2026-11-05. AgentReady v2.0, read 2026-11-04.