Structured data analyser
See what Schema.org a page publishes, and what it is missing for a model to know who it is talking about.
What markup solves, and what it does not
No model promises to cite you more for carrying JSON-LD, and this tool is not going to imply otherwise. What markup solves is something smaller and more real: entity ambiguity.
When a model runs into your company name it has to decide whether that is you, another company with the same name, or just a word. An Organization with sameAs pointing at Wikidata or LinkedIn turns that decision into a lookup. Without it, it is a guess, and guesses get shared out among everyone who has your name.
Why there is no score out of 100
Because a number invites you to raise it, and that number goes up by declaring types that describe nothing. You see pages with eight Schema.org types, zero sameAs, and an entity that is still unidentified.
What moves the needle is one single thing, and it does not average with the rest. So you get a list ordered by severity instead of a scoreboard.
What this tool cannot see
It only reads JSON-LD. Microdata and RDFa are detected so we do not tell you that you have no markup when you do, but they are not analysed.
It also does not run JavaScript. If a browser script injects your markup, it will not show up here, and that is worth knowing because several crawlers are in the same position.
This tells you whether they can read you. Not whether they name you.
The three checks here rule things out: they tell you whether something is stopping you from appearing in an answer. Whether you actually appear, and who appears instead of you, has to be measured by asking the models. The scanner does that free in about a minute.