Structured Data Inspector
See what machines understand your page to be
Structured data is how you tell search engines and AI systems what your page is about - not just what words it contains. Paste your JSON-LD below (or a whole HTML page - the ld+json blocks are extracted automatically) and get an instant map of the entities you're declaring, plus plain-English checks against what Google documents and what answer engines reward.
What good structured data buys you
Two audiences read your JSON-LD, and they reward different things. Search engines use it to qualify pages for supported rich results - stars, breadcrumbs, product panels - and each rich result type has documented required properties. Miss one and the markup is simply ignored; nothing warns you. (FAQ markup is the cautionary tale: Google restricted FAQ rich results to authoritative government and health sites in 2023, then retired them entirely in 2026 - the markup is still valid schema, but it no longer earns a Google rich result.)
AI answer engines are the newer audience, and here honesty matters: Google states outright that its AI features need no special markup, and no answer engine documents JSON-LD as a privileged source of answers. Our view - and it is a view - is that structured data remains the most explicit, standardised description of what your business is that a machine can read, and a clean entity graph - one organisation, clearly named, linked to its site and profiles via @id and sameAs - can only help systems interpret and connect that information. What it cannot do is guarantee inclusion, citation or use in AI-generated answers.
This inspector checks both layers: the property completeness that rich results demand, and the graph hygiene - stable identifiers, resolved references, consistent naming - that makes an entity unambiguous to any machine reading it.
JSON-LD habits that pay off
Give entities stable @ids
An @id like https://site.com/#organization turns a blob of properties into a referenceable entity. Other blocks can then point at it instead of repeating it, and machines can tell "the same business mentioned twice" from "two businesses".
Absolute URLs, ISO dates
Use absolute https URLs for url, image and logo where possible. JSON-LD can resolve relative URLs against the page's own URL, but absolute ones are unambiguous and match what Google's examples use. Dates belong in ISO 8601 (2026-08-01), not "1st August 2026".
Only mark up what's on the page
Google's policy is blunt: structured data must describe content visible on the page it sits on. FAQ markup for questions the page never shows, or review stars with no reviews, is how sites earn manual actions.
sameAs is cheap identity insurance
Linking your organisation to its LinkedIn, Companies House record or other profiles helps every system - search or AI - confirm that this entity is that company. Disambiguation is most of the battle in entity SEO.
Where this fits
This tool is the quick, local first pass: it catches structural mistakes and missing properties in the time it takes to paste. For the final word on rich result eligibility, run the winner through Google's own Rich Results Test - it tests against the live pipeline, which no third-party tool can fully mirror.
And it completes a set: check crawler access with the Robots.txt Tester, preview your snippet with the SERP Snippet Preview, and analyse the whole results page with the free RankRecon extension.