Loading…
Turn a wall of JSON-LD into an expandable entity tree. See every @type at a glance, drill into nested entities, and follow @id references with a click.
The visualizer parses any JSON-LD document — a single entity, an array, or an @graph — and renders it as a tree of entity cards. Each card shows the entity's @type as a badge, a human-readable label (its name or headline), its @id when present, and every property as a row: plain values inline, nested entities as collapsible child cards, and references highlighted in purple.
Clicking a purple @id reference jumps to the entity that defines it — expanding any collapsed ancestors along the way. That makes it easy to verify the linking pattern used by most SEO plugins (Yoast, Rank Math, Next SEO), where a page's Article points at a shared Organization node rather than repeating it.
Structured data bugs are usually structural: a Review accidentally nested inside the wrong entity, an AggregateRating attached to the Organization instead of the Product, an @id typo that leaves a reference dangling. These mistakes are invisible in raw JSON and invisible in search results — the rich result just quietly fails to appear. In a tree view they jump out immediately.
It's also the fastest way to learn from competitors: fetch any page that shows stars or FAQ dropdowns in Google and study exactly how its entities are arranged. When you spot a structure worth copying, rebuild it with the schema generator and check it with the validator.
Structure. Real-world JSON-LD often nests entities four or five levels deep and links them with @id references. The tree view collapses that into scannable cards — one per entity, with its @type, a readable label, and a count of nested entities — so you can see the shape of your data at a glance.
An @graph is an array of entities that share one @context — a common pattern for pages describing several things at once (an Organization, a WebSite, and an Article, say). The visualizer renders each @graph member as its own top-level card.
@id gives an entity a stable identifier so other entities can reference it instead of duplicating it. When a property contains only an @id, it's a reference — click it and the visualizer scrolls to and expands the entity that defines it. References to entities not present in the document are marked as external.
Yes — switch to the URL tab. We fetch the page server-side, extract every JSON-LD script block, and render them all in one tree. JavaScript-injected markup won't be visible, since we read the served HTML.
TWR adds AggregateRating schema to your public review page automatically — free. Collect verified reviews inside your app and let us handle the structured data.