The Framework · by Source of You
When someone asks an assistant about a name, a few sources get named and the rest are invisible. That outcome is not random, and it is not yours to command. What you control is what the engines find: whether a clear, structured, corroborated account of you exists where they read. This is the framework for that.
Most audits conflate the two. Keeping them apart is the whole point, and the honest line of the category.
Readiness
How well your foundations support being read and cited, scored 0 to 100 across the four signals below, from your live pages. This is what you control, and what Source of You builds. You can run it free.
The answer
Whether an assistant names you when someone asks. That is probabilistic, it varies run to run, and nobody controls it. We will never promise it. We make the truth easy to find, read, and cite, and let the answer follow.
The gap between them is the work, and it is almost entirely earned off a page you own.
Each signal is scored 0 to 25 into a single 0-100 readiness number, read straight from your live pages, with a documented, versioned weight. No black box.
Whether a clear, current page you own names you and states who you are.
Give an engine no source it controls and it answers from scraps: a stale profile, someone else with your name, a guess stated with confidence. A page you own exists to answer exactly one question, who you are.
Close it
Stand up a page you own that names you and states who you are, so your name resolves to something you control.
Whether machine-readable identity data is present, not just prose.
Person and ProfilePage schema tell an engine exactly who a page is about instead of leaving it to infer from paragraphs. It is the difference between being parsed and being skimmed.
Close it
Add Person and ProfilePage structured data plus a canonical link, so engines read your identity instead of guessing it.
Whether more than one credible source tells the same story about you.
Engines cross-check. A claim only you assert reads as marketing; a claim a stranger can verify on a page you do not control reads as fact. This is, consistently, the signal that separates a recognized identity from an unknown one.
Close it
Link out to profiles and proof you do not fully control (a sameAs graph), and give more than one page that names you.
Whether the pages that name you can actually be read by the AI engines.
If a crawler is blocked, or the content only appears after heavy scripting, none of the other signals matter, because the engine never sees them. Legibility is the floor everything else stands on.
Close it
Make sure the pages that name you are crawlable by the AI engines, and add FAQ answer-fuel they can quote.
Every Source of You page ships the machine-readable pieces engines read. We promise what we serve, because you can fetch and check every one of these, never what an engine then decides.
Person + ProfilePage schema
Structured identity data in every source page, so engines read who it is about.
FAQPage answer-fuel
Real questions and answers marked up so an engine can quote them verbatim.
One canonical URL
A single address of record for AI and search to cite, at your handle.
An llms.txt index
A plain-text map telling AI systems what your pages contain and who they speak for.
An open crawler policy
A robots.txt that explicitly names the answer engines' crawlers, so what we publish is a fact anyone can fetch.
A sitemap
An index map so crawlers find your load-bearing pages without link-walking.
Served to the engines that answer for you
GPTBot · ClaudeBot · PerplexityBot · Google-Extended
and 6 more crawler classes, named explicitly in a robots.txt anyone can fetch.
You should distrust anyone who promises to. What you can do is make the truth easy to find, read, and cite. So that is all we promise, and all we build toward.
It runs the other way too. When Source of You generates a surface, it reads against your record and drops any figure or claim it cannot find there, rather than publishing it. Honesty is enforced here, not just promised: a page that names things you never did would fail the one job the record exists to do.
The four signals are not six separate projects. You build one structured record, and every surface is generated from it: a canonical source page with the schema and answer-fuel engines read, a resume, a LinkedIn summary, a bio, an AI-visibility audit. Change the record once and every render updates. The framework is the reason the product is a record, not a page builder.
Looking ahead
The same framework applies to a team, a firm, or a brand: one record, structured and corroborated, that answer engines can read. We are extending Source of You in that direction. If that is you, tell us what you would need.
Start the conversationScore your four signals from your live pages, free and with no account. Then build the one record every surface is generated from.