Component 01
Entity integrity
Can a machine tell exactly who you are, and trust what you say about yourself?
Why it matters
An engine has to resolve a name to one entity before it can recommend it. Ambiguity means omission, or being merged with a namesake. The newer risk is narrative capture: in Ahrefs’ testing, most AI tools repeated false brand claims that had been planted online [Ahrefs]. An undefined entity gets defined by whoever publishes about it.
What to do
- Write one canonical description, fact set and naming convention, and use it everywhere: site, social bios, retailer storefronts, press kit.
- Ship Organization and Product schema with stable
@idvalues andsameAslinks to every profile you control, plus Wikidata where you qualify. - Give proprietary products, methods and frameworks their own pages and identifiers, so they exist as entities rather than phrases.
- Make experts real entities: named authors with credentials and consistent profiles.
- Ask the major engines monthly what they believe about you, and correct wrong facts at the sources they cite.
For agents: stable identifiers (schema @id, GTINs, SKUs, merchant IDs) let parallel sub-agents confirm they’re all looking at the same product.
Failure mode: systems can’t safely reuse information they can’t attribute.