Rubric / Structured data
Schema type coverage
structured_data.type_coverage
weight 1heuristic
Declared JSON-LD types cover the apparent page purpose (e.g. a product page has Product, a blog post has Article).
Definition
Check ID
structured_data.type_coverage
Category
Structured data
Weight
1
Counts toward the score
Yes.
Evaluated by
A fixed rule whose threshold AgentSpeed chose. Reproducible; another rubric may reasonably disagree.
Chosen parameter
match = type-to-purpose inference
Standard maturity
established
Canonical spec
None. This check has no published external specification — it is an AgentSpeed rule.
Introduced in
r2026.04.1
Retired in
Still active.
History
Every change to the instrument— including the versions that changed this check
Machine-readable
/rubric.json— this check, and every other, as data
How often this check is right
No rate published. Too few labelled cases to publish a rate: 1 flagged case (30 needed to publish), 1 defective case (30 needed to publish). The counts are the honest answer here. The matrix behind structured_data.type_coverage is 2 labelled cases — reported here rather than turned into a percentage that would read as more certain than the evidence is.
Corpus v1, measured under rubric r2026.11.0. Full method and every other check at /rubric/accuracy.
How to fix it
Align JSON-LD type to page purpose. Product pages without Product markup are skipped by agent shopping flows.
Does your site pass this check?
Free scan, 30 seconds, no signup — this check and the other 35, with the exact evidence for each verdict.
Scan my site →