Glossary
Rendering & JS dependency
Raw HTML and the post-JavaScript DOM are two representations. Dependency is measured; it is not automatically a defect.
Raw versus rendered
Field-level comparison of initial HTML vs browser DOM after scripts run.
Compared fields include title, canonical, H1, visible text, links, and JSON-LD counts/presence.
When the browser step is skipped, the class column shows UNMEASURED and representations stay “Raw HTML only.”
On the report Raw versus rendered section
Diff class (UNCHANGED / JS_ADDED / JS_REMOVED / JS_CHANGED / UNMEASURED)
How a field changed between raw HTML and rendered DOM.
UNCHANGED: same value or count. JS_ADDED: present or larger only after render. JS_REMOVED: present or larger only in raw. JS_CHANGED: both present but disagree. UNMEASURED: no browser comparison.
On the report Raw versus rendered · Class column
JS dependency (LOW / MEDIUM / HIGH / UNMEASURED)
Magnitude of reliance on JavaScript to surface content machines might need — not an automatic fail grade.
Derived from content, link, schema, title, and canonical deltas between raw and rendered. UNMEASURED when browser capture did not run.
HIGH means more of the representation depends on JS. Whether that is a problem depends on which facts moved and whether crawlers execute JS.
On the report Section note · Measurement components bar
- HIGH is not automatically a defect.
Fact classes (page-level)
Page-level counters for how fact-bearing text shifted after JS — not per-fact provenance labels.
Shown in the rendering meta line as initial / JS_ADDED / JS_REMOVED / JS_CHANGED counts.
Easy to confuse with AtomicFact provenance. These are aggregate deltas for the page representation.
On the report Raw versus rendered · meta line
Schema injected
Whether more JSON-LD blocks appear after render than in initial HTML.
A yes means machines that only see raw HTML may miss schema that only exists post-JS.
On the report Raw versus rendered · Schema injected