Glossary
Structured data
Parse survival is not schema truth. INGEST tests whether intended values survive ordinary parsing.
Standard parse
Whether JSON.parse succeeds on the raw JSON-LD script text.
If standard parse fails, many consumers never see the graph — regardless of “schema validators” that repair aggressively.
On the report Structured data integrity table
One unescape
Whether the block parses after a single HTML-entity unescape repair.
Some publishers emit entity-escaped JSON inside script tags. One unescape may recover a parse that strict consumers miss.
A pass here with a fail on standard parse is a warning sign for portability.
On the report Structured data integrity · One unescape
Intent survives
Whether the intended values remain recoverable without depending on non-standard repair paths.
This is not “the schema is correct for Google.” It is whether the published intent survives the parses INGEST trusts.
Failed intent-survival rows penalize the structured-data leaf.
On the report Structured data integrity · Intent survives
- Not a Rich Results pass/fail.
Values agree
When both standard and unescape parses succeed, whether their values are equal.
Disagreement means repair changed meaning — a high-severity serialization smell.
On the report Structured data integrity · Values agree
Graph identity
Duplicate or unresolved @id values inside JSON-LD blocks.
Broken identity weakens entity coherence and machine linking even when parse is OK.
On the report Structured data · Graph identity notes