01 / PRESERVE
Every original block
Malformed JSON-LD remains visible instead of being silently converted into “nothing found.”
FOCUSED ON JSON-LD
From raw source to a useful answer.
The extension stays deliberately narrow: diagnose JSON-LD accurately, preserve its source, explain local findings, and make official confirmation easy.
02 / LOCATE
Line, column, context
Syntax diagnostics include a source excerpt and caret, plus copy and download actions.
03 / UNDERSTAND
Arrays, graphs, nesting
Top-level arrays, @graph, and nested typed entities stay linked to their source block.
04 / NAVIGATE
Issue to JSONPath
Move from a local finding directly to the relevant node or nearest existing parent.
05 / CONFIRM
Official validator shortcuts
Open the current URL in Google Rich Results Test or Schema.org Markup Validator.
06 / SHARE
HTML and PDF-ready reports
Include source blocks, parsing errors, entities, and local results in one focused artifact.
SEE THE WORKFLOW
Inspect, locate, validate, report.
HONEST VALIDATION BOUNDARIES
Local diagnosis and platform eligibility are different jobs.
Inside the extension
JSON parsing, Schema.org structure checks, navigation, report generation, settings, and history run locally in Chrome.
Inside official tools
Google decides rich-result eligibility. Schema.org Markup Validator provides its own vocabulary validation. The extension opens both with the current URL.
Minimal by default
The extension reads the active page only after you invoke it. There is no default all-sites access.
Automatic detection is opt-in
All-sites permission is requested only when you enable automatic detection and removed when you turn it off.
No project telemetry
No analytics, advertising, user tracking, or project-operated data service runs inside the extension.
FAQ
Clear before you install.
Does it modify the page?
No. Source edits are local drafts. JSON-LD Checker never writes them into the inspected website.
Does “valid” guarantee a Google rich result?
No. Local checks are explicitly labeled. Use the shortcut to confirm eligibility in Google Rich Results Test.
Why are there more entities than script blocks?
One block can contain an array, @graph, or nested typed entities. The tool keeps the block-to-entity mapping.
Is AI required?
No. Inspection, syntax diagnostics, validation, navigation, external validator links, and reports work without AI or an API key.