Entity clarity and sameAs
Entity clarity is how unambiguously an engine can tell who or what a page is about and connect it to a known real-world entity. The sameAs property is the main tool: it links your Organization or Person schema to authoritative profiles such as Wikipedia, Wikidata and LinkedIn, so an engine can resolve you to one confident identity rather than guessing between similar names.
- →Entity clarity is how confidently an engine can resolve who a page is about and attribute a quote to you.
- →sameAs links your Organization or Person schema to authoritative profiles, connecting your site to a known entity.
- →Consistency across the web, plus valid Organization and Person schema, is the Known pillar's core.
What is entity clarity?
Entity clarity is how confidently an AI engine can resolve the person or organisation behind a page and connect it to one known entity. An engine that cannot tell who published a page will use the information and leave you unnamed, because it will not attribute a quote to a source it cannot identify. Clear entities also protect you from being confused with a similarly named company or person. Entity clarity is the heart of the Known pillar: discovery and attribution both depend on the engine knowing who you are. See what-is-ai-citability for why attribution is the goal.
What is sameAs and why does it matter?
sameAs is a Schema.org property that points from your Organization or Person schema to other authoritative pages describing the same entity. It matters because it turns scattered mentions into one resolvable identity: the engine learns that your site, your Wikidata item, your LinkedIn page and your Crunchbase profile all describe a single entity. That lets it merge the signals about you and cite you with confidence. Here is Person schema with sameAs.
{
"@context": "https://schema.org",
"@type": "Person",
"name": "Chris McCarron",
"jobTitle": "Founder",
"worksFor": { "@type": "Organization", "name": "GoGoChimp" },
"url": "https://gogochimp.com/about",
"sameAs": [
"https://www.linkedin.com/in/chrismccarron",
"https://www.wikidata.org/wiki/Q139585911"
]
}Which profiles should you link with sameAs?
Link the authoritative, stable profiles that already describe the same entity. The goal is confident resolution, so choose quality over quantity.
- Wikipedia and Wikidata if you have them; these feed many knowledge graphs directly.
- LinkedIn company or personal profiles.
- Crunchbase for an organisation.
- Official social accounts you control (for example your verified X, YouTube or GitHub).
- Industry or professional registries that are widely trusted in your field.
Do not pad the array with thin directory listings. A short list of trusted, consistent profiles resolves an entity better than a long list of weak ones.
Why consistency across the web matters
Consistency across the web matters because an engine builds its picture of an entity from many mentions, and contradictions weaken it. Use the same legal name, the same logo, the same founding details and the same canonical URL everywhere, and make the entity on your site match the entity on the profiles you link with sameAs. If your LinkedIn says one name and your schema says another, you give the engine a reason to hesitate. Pick one canonical entity and keep every reference aligned.
How Rubric checks entity clarity
Rubric checks entity clarity under the Known pillar. It looks for Organization and Person schema with sameAs, content-type schema, schema completeness and validity, canonical tags, internal links, entity density in the prose, and unique titles and meta. The highest-leverage fix on most sites is adding Organization and Person schema with sameAs in the shared head, so it covers every page at once. For the schema types in full see schema-markup-for-ai-search, and for the step-by-step see adding-organization-schema.