1 · See it
The agent view
The answer an agent receives about any domain, rendered for a person: each action’s decision and the reason.
Entity map validator: does your entitymap.json parse, and does every claim in it resolve?
In one sentence
An entity map validator fetches /entitymap.json, checks that it parses, that every entity in it also exists in the page's JSON-LD and vice versa, and that each sameAs profile it cites links back — an unreciprocated profile is a claim, not corroboration.
Type a domain. The scan fetches /entitymap.json, parses it, and checks its entities against the JSON-LD on the page and against the sameAs targets it cites - a profile you claim is only corroboration if that profile links back.
Measured
What the scan measures for this
Entity map parity
Every entity in the map should exist in the page's JSON-LD and vice versa. A map that names three locations while the page declares one is a disagreement an engine has to resolve by trusting neither.
Shown on a report when the site publishes an entity map.
Corroboration
Each sameAs target is fetched. Reciprocated links count; a directory profile that never mentions the site does not.
The JSON-LD it mirrors
Parse, @id collisions, identity nodes, the one LocalBusiness that appears twice because it was parsed twice - the map inherits every defect the page has.
The triples
Named entities, dangling references and the graph an answer engine can actually walk from your homepage.
For agents
What an agent is told about the same site
An agent does not read the report. It asks one endpoint before it reads, cites, connects or transacts, and gets a signed answer built from the same measurement.
2 · Call it
One endpoint
GET /api/v1/resolve?domain= returns the signed answer; preflight returns a decision and a receipt for one action.
3 · Check it
Without trusting us
Every answer is Ed25519-signed and logged; it verifies offline with the published key.
Workflow
The workflow
- Scan the domainThe entity map, the page's JSON-LD and every cited sameAs URL are fetched in one pass.
- Read Entity map parity and CorroborationEach row names the entity or link that fails and shows the bytes that decide it.
- Generate or repair the mapIf the site has no map, the free generator below builds one from its own JSON-LD. If it has one, the fix list names the entities that disagree.
- Publish, purge, re-scanThe second scan proves parity. On a watched domain the map is re-read twice a day and a change receipt records any drift.
Free
Free tools for this
Each one is a single request to the domain you name, answered as text or a download. Put the domain on the end of the URL, or use the form on the tools page.
Generate an entitymap.json from your JSON-LDBuilt from the identity nodes the page already declares, so it cannot disagree with them on the day it is made.Can a machine read your files?Confirms the map, once published, is served as JSON and not from a stale cache.
Reading
Read next
- Two nodes with the same @id are one node parsed twice
- Entity map, sameAs and corroboration, defined with their limits
- How to read a CrawlCheck report
Start from what you are checking
llms.txt auditdoes yours resolve, parse and match the site it describes?robots.txt for AI crawlerswhat yours actually permitsSEO audit toolthe technical checks, plus what AI crawlers actually receiveTechnical SEO auditcrawl access, sitemap, hosts, links and speed, checked in one scanLocal SEO auditdoes your site say who you are, where, and does every listing agree?SEO audit reports for agenciesyour name on the report, the proof still attachedWhat is a website auditWhat is a website audit? What it checks, what it costs, and how to run one freeWhat is an SEO auditWhat is an SEO audit? The checks that matter, in the order to fix themAEO auditcan ChatGPT, Claude, Perplexity and Google reach, read and quote your site?
You cannot pay to improve a score. A licence adds the lists behind the counts and the record over time - never a better grade.
Questions about this page
QWhat is an entity map?
A JSON file at /entitymap.json that lists the entities a site is about — the business, its people, locations, services — with stable ids and links to the profiles that corroborate them. It is read alongside the page's JSON-LD, so the two must agree.
QWhy does parity matter?
An engine reading a map that names three locations and a page that declares one has to resolve the disagreement by trusting neither. Parity means the map and the page describe the same entities with the same ids.
QWhat counts as corroboration?
A sameAs target that, when fetched, refers back to the site. A directory profile that never mentions the domain is not corroboration and is not counted, however authoritative the directory.
QCan the scan build one for me?
Yes. The free generator builds an entitymap.json from the identity nodes already in your JSON-LD, so on the day it is made it cannot disagree with the page. Publish it, purge the cache and re-scan.