SCHEMA IS A GRAPH, NOT A BADGE

See the identity story machines receive.

We turn JSON-LD into a relationship map, then check whether its people, organisations, pages and services stay connected, consistent and visible.

ORGWEBPERSONPAGESERVICEpublisherauthormainEntityprovidersameAs

START AN AUDIT

Map one page—or sample the site.

Raw public HTML is inspected. The sample follows same-origin links breadth-first so repeated identity definitions can be compared.

Page sample

Five free audits per day · public pages only · frozen HTML and JSON reports

WHAT IT SEPARATES

Markup present is not identity resolved.

Stable IDs
Whether the same entity can be referenced without redefining it.
Connectivity
Whether page, author, publisher, provider and subject relationships form a usable graph.
Conflicts
Whether one @id changes name or type across sampled pages.
Visible alignment
Whether material schema names are corroborated in user-visible copy.
Identity bridges
Whether official external profiles clarify—not merely decorate—the primary entity.
Limits
Schema can express a claim; it cannot prove that claim is true.
Read the full methodology →