Works best on an About page, homepage, or author page, wherever a Person or Organization would actually be marked up.

Questions people ask

What is this actually checking?
Whether your site has Person or Organization structured data (JSON-LD), and if it does, whether it's complete: a name, a description, an image, a canonical URL, and sameAs links tying it to your other real profiles (LinkedIn, Wikidata, etc.). This is the same signal AI models and Google's Knowledge Graph use to resolve who or what a page is actually about.
What if it finds nothing?
That means your page has no Person or Organization schema at all, the most common finding, and the most fixable one. Without it, an AI model has to guess who you are from unstructured text, and a common name makes that guess more likely to go wrong. See what is entity consistency for what to add.
Why does sameAs matter so much?
sameAs is the explicit list of "this is the same entity as these other profiles": LinkedIn, a company site, Wikidata, GitHub. It's the single strongest disambiguation signal you control directly, especially if your name or brand isn't unique.
Does a good score here guarantee AI gets me right?
No. It's necessary, not sufficient. Complete entity markup makes correct resolution far more likely; it doesn't override a genuine name collision or a training-data-sourced error. See what to do when AI gets your brand wrong for what happens after markup is already correct.

This checks structured data. It doesn't check whether the underlying facts are correct, or whether a name collision exists elsewhere. That's the deeper work in an entity audit in under an hour. One of a small suite of free tools, built by Karthik Ramachandiran.

A good place to start

Your competitor is the answer
every AI gives your buyers.

A $497 Shortlist Scan tells you for certain in three days: real buying-stage prompts, run cold, three times each across ChatGPT, Perplexity, Gemini, and Claude.