Review parsing and identity separately

Each supplied block receives a JSON parsing outcome. A failed block remains in the summary and export while successfully parsed blocks contribute inventory rows. A JSON parse is not a schema validation pass or a Google rich-result eligibility result.

Inventory rows are objects with explicit @id or @type keys, outside @context and literal @value contents. An object containing only @id (with optional @context or @index) is labeled an ID reference. Other inventoried objects are labeled descriptions. Literal @type values and ordinary property names are shown for review, not checked against a vocabulary.

Follow the worked examples

1. Choose Raw JSON for a JSON value, or HTML with JSON-LD scripts for a document.
2. Load the connected graph and inspect its seven inventoried objects.
3. Compare the two descriptions of the same organization ID. Multiple descriptions can be intentional.
4. Review the person reference that is not described in this sample. It may be external.
5. Load the mixed HTML example to see one parsed block and one deliberate syntax error.
6. Export block outcomes and object paths, then verify the actual saved page separately.

Keep literal matching within its scope

Relative and absolute IDs, compact IRIs and aliases are not expanded. Graph scoping, remote contexts, keyword semantics, duplicate JSON property names and Schema.org requirements are not validated. A matching string does not prove a semantically valid relationship; a missing literal match is not automatically an error. JSON parsing can overwrite duplicate property names without reporting them.

HTML mode reads application/ld+json script text in an inert template. Pasted scripts are never executed; external scripts, URLs and contexts are not fetched. Scripts within nested template contents are not included. Inputs are never inserted into the visible page as HTML.

Use the CSV as a handoff

The table previews 100 objects. The CSV includes every block outcome and inventory row within the limits, with JSON paths and notes. Formula-like cell values receive an apostrophe prefix. Exceeding the traversal limit stops the review and disables export; split a large sample before retrying.

Read the JSON-LD review guide and use the Structured data review worksheet. Review the Google structured data guidelines and test relevant live markup in the Rich Results Test.

Inputs are processed locally. See the Privacy Policy and tool limitations.