Plain-language meaning
Machine-readable information describing entities, properties, and relationships represented by a page.
Why it matters
Structured data affects how a website is discovered, understood, used, maintained, or evaluated. In an Asuruas report, the term remains connected to evidence and context.
Use “Structured data” precisely
In an audit, structured data should name a specific condition, object, relationship, or decision—not serve as a vague synonym for website quality. Attach the term to the exact evidence and affected scope so a reviewer can understand what was observed and what remains uncertain.
Evidence to inspect for Structured data
- Visible entities, page purpose, json-ld graphs, identifiers, relationships, required properties, and consumer-specific eligibility.
- Agreement between structured data and information a visitor can actually see on the page.
- Document how the term affects the outcome to describe real entities and relationships accurately without manufacturing unsupported claims.
- Parse the deployed json-ld, validate the graph, compare it with visible content, and test any target consumer requirements.
Decision and verification record
Scope
Name the website, environment, URLs, entities, templates, or user journeys included in the structured data decision.
Decision
Record the chosen action, owner, priority, dependencies, approval, and the evidence that justified it.
Verification
Parse the deployed json-ld, validate the graph, compare it with visible content, and test any target consumer requirements.
Turn structured data into an accountable record.
A shared working definition of structured data used consistently across reports and operational records.