GEO-004 · Present JSON-LD parses and meets documented requirements
Structured data that does not parse, or lacks the properties its type requires, is ignored. Absence is not a finding.
- Evidence class
- E1
- Weight
- 2
- Subject
- each route group
- Scope
- URL/repo
- Default severity
- medium
- Lifecycle
- stable
- Platforms
- Any web stack
Sub-checks
A subject fails if any evaluated sub-check fails, and passes only when every applicable sub-check ran and passed. url sub-checks need a URL; both can also run from source.
| Sub-check | Scope | Checks that |
|---|---|---|
parses | both | every application/ld+json block is valid JSON |
required_properties | both | known types carry their documented required properties |
Preconditions
- At least one JSON-LD block is present; otherwise not applicable
Remediation
Fix the JSON syntax, then add the required properties for the declared @type.
Fix class: contextual
Known false positives
- Types GEO does not model are checked for parsing only.
Evidence
Platform policies and standards are cited as such; anything else is labelled guidance. These links were carried forward from the specification and should be rechecked before quoting them as current policy.
- Google: structured data general guidelines (platform-policy)
Run it
npx geopilot explain GEO-004
npx geopilot scan . --rule GEO-004