Entity consistency
If an engine cannot tie your site to a known entity, it treats you as an unknown source and cites someone it recognises instead.
Organization schema
The base identity record. Without it an engine has to infer who you are from page text, which it will do badly.
Thin sameAs
sameAs is how you tell an engine which Wikipedia, Wikidata, LinkedIn, Crunchbase and social profiles are yours. A thin or absent sameAs leaves your identity unanchored.
Name, address and phone across profiles
Where you have connected a Google Business Profile, Facebook or Instagram account, we compare the name, address and phone on each against your site and report mismatches per profile. Profiles you have not connected are reported as gaps, not as failures.
Questions
What if we have no physical address?
Then NAP consistency does not apply to you and it will not be reported as a failure. The check only runs where there is something to compare.
More in Can AI engines read you?
AI crawler access
We check robots.txt against fifteen named AI crawlers, including OAI-SearchBot, PerplexityBot and Claude-SearchBot, and name the ones you block.
Read moreRendering gate
We fetch your page as raw HTML and again in a real browser, then compare. Content that exists only after JavaScript runs is content most AI crawlers never see.
Read moreStructured data values
Most schema validators tell you the markup parses. We check whether the fields inside it actually contain anything an answer engine can quote.
Read moreCitation drivers
Three things make a page quotable to an answer engine: a concrete number, a date it can trust, and language that commits. We check all three.
Read more
Run it against your own site.
No signup, no card. It reports what it could not check as well as what it found.