JSON-LD check
JSON-LD: distinguish JSON syntax from schema meaning
TL;DR
Inspect static JSON-LD blocks. A successful JSON.parse is not JSON-LD conformance, schema validation or alignment with visible content.
What the current check observes
Eligible script blocks with type application/ld+json are extracted from sampled static HTML. The auditor parses JSON, recursively collects type strings, counts blocks and records parse failures. Missing blocks and missing type conventions are advisory.
Context and prerequisites
The parser does not resolve contexts, validate required schema fields, establish entity truth or compare claims to rendered content. A number, empty object or misplaced schema can parse as JSON without being useful structured data. Not every page needs JSON-LD.
How to review the observation
When a real entity or supported content type is applicable, choose accurate identifiers and verify every claim against the visible page. Repair malformed JSON in an existing block. Use an appropriate schema/consumer validator separately, then review applicability manually.
Illustrative example, not a universal prescription
{"@context":"https://schema.org","@type":"Organization","name":"Example"}The example parses as JSON and contains an Organization type string. It does not establish a real organization, ownership, complete schema or citation benefit. Do not add it to a page without a matching entity.
Measurement and experimental legacy calculation
Public measurement separates Confirmed issue, Advisory, Unknown, Not applicable and Observed pass. An observed pass applies only to an explicit bounded rule; absence of an emitted failure is not a pass. Missing prerequisites do not earn repair credit.
No blocks now returns 100 (optional nonpenalty, changed from v7). Otherwise start 100 and subtract 10 per invalid JSON block. Missing types and sampled block coverage do not deduct. Clamp to 0..100 and round.
Legacy values are clamped to 0..100 and rounded. They are not readiness certification, risk indicators or predicted citation outcomes. Method changes do not rewrite historical records.
Full methodology and fixed weightsSources and further manual validation
The observations above describe the local implementation, not guarantees from these sources. Protocol and provider documents help interpret purpose and perform checks this audit does not implement.
What observations does this check return?
LLMScore audits eleven readiness categories. Free, no signup.
Run this check on your site →