All free tools

JSON-LD visualizer

Enter a page URL, or paste JSON-LD or HTML, to see which entities the markup describes, how they link and roughly how search may show them.

Input

JSON-LD is structured data in a script tag. It tells search engines and AI assistants who is behind a page and what is on it: an article, a product, a list of questions. Raw, it is a wall of nested brackets that is hard to follow.

The visualizer turns each block into a tree of entities. Nested objects open inside their parent, @graph nodes sit side by side, and every @id reference links to the entity it names. It also flags blocks that are not valid JSON, a missing @context or @type, and references that lead nowhere.

Questions

What does the JSON-LD visualizer do?

It reads every JSON-LD block on a page, or in the code you paste, and shows it as an expandable tree with a rough search preview. It also lists structural problems, such as invalid JSON or an entity without @type.

How is it different from the Schema checker?

The visualizer shows what your markup says and how its parts connect. The Schema checker runs SagBot's checks on it: whether the page has valid structured data, names the organisation or person behind the site, and marks up its FAQ.

How are nested objects and @graph shown?

Each top-level object, each item of a top-level array and each node of an @graph is a top-level entity, open by default. Nested objects open inside their parent. A value that is only an @id is a link that jumps to that entity.

Is the code I paste sent anywhere?

No. Pasted code is parsed in your browser and never sent to SagBot. In URL mode SagBot fetches the page once, as its own crawler, respects a SagBot opt-out in robots.txt and does not keep the result.

Why doesn't my rich result show in search?

Valid markup makes a page eligible for a rich result, not certain to get one. The search engine also weighs the content, the query and the site, and each result type has its own required properties. Check them in the engine's documentation.