Entity SEO
Make your company unambiguous to machines
- Understand
Stage 2: Understand
Structured data check
Lists every JSON-LD block on a page by type and id and flags placeholder-looking values, so you can check structured data before engines read it.
Free to use. No login, nothing stored.
What it checks
Understand- All JSON-LD blocks parsed, with syntax errors reported
- Nodes listed by @type and @id, duplicates flagged
- Organization, Person, Service and Article fields present or missing
- sameAs URL format and placeholder-looking values
- Prompts to compare schema values with the visible text (name against H1, price against the page)
Method question for this stage: Do machines know what each page and brand is?
Run the check
Results
No check run yet
- Info
Five groups: blocks, graph, fields, visible content, placeholders
Each row names what was looked for and links to the documentation it comes from.
Presence checks only. For eligibility, use Google’s Rich Results Test and the Schema.org validator.
How we check
The rules this tool tests, and where they come from
A result is a check against a published rule, not a prediction. Every row shows its working.
Rules and sources
Links go to the operator's or standards body's own documentation. We do not link to third-party summaries.
Read more
Next step
Fix what it finds
This check belongs to the Understand stage of the Crawl-to-Citation Method. The service below covers the fix; the Diagnostic ranks it against everything else.
Most engagements start with the Search Visibility Diagnostic ($2,500).
It covers all six method stages, so what this tool finds is ranked against everything else before you commit to any work.
Book the diagnosticStructured data questions
What the rows check, and what they leave to the validators.
Still have questions? Book a callIs this a validator?
No. It reads every JSON-LD block, lists the graph and reports which commonly expected properties are present or missing. It does not check value formats against the schema.org vocabulary or decide eligibility for rich results. The Schema.org validator and Google’s Rich Results Test do that, and the results footer links to both.
Why compare schema values with the visible text?
Google’s structured data policies require markup to describe content that is on the page. A name, headline or price that appears only in the markup is the mismatch a manual review finds first. The prompts here flag the gap; they do not judge whether the difference is acceptable.
Why does a missing @id matter?
An @id is a stable identifier for a thing. When the Organization on the homepage and the publisher on an article share one @id, consumers can tell they are the same entity. Without it, each page describes a new, unconnected object. It is a recommendation, not a requirement, so the row is a Warning.
Last reviewed