The AIOFacts working framework.

What it is. Stating plainly who you are, what you do, who you serve, and where, so a system reading the page does not have to infer it. An entity is the thing itself, the business, person, or product, not the page that describes it. Entity Clarity is the work of making that thing unmistakable.

Why AIOFacts includes it. A system cannot describe an entity it has not identified: separated it from similarly named others, attached it to a category, connected it to a place and to people. Ambiguity leaves the system inferring, and inference is where errors enter. Whether ambiguity changes what any given assistant says is not something we can measure from outside, but the failure mode is directly observable in wrong or merged entity descriptions.

In practice.

• A single, plain statement of identity: name, category, who you serve, and where.
• One canonical home for that identity, marked up so machines read it directly (see Structured Data).
• Clear disambiguation from others that share your name or category.

What it is. Real reviews, ratings, and reputation, published where they can be read and checked. Trust Signals are evidence produced by others, not claims an entity makes about itself.

Why AIOFacts includes it. What other parties report is harder to fabricate than self-description, and it is checkable. Whether and how much any AI system weighs third-party reputation is not published by its operator, so this is included on the reasoning that verifiable evidence is more useful than an unverifiable claim, not on a measured effect.

In practice.

• Real reviews and ratings on the platforms a system already reads.
• Consistent reputation across independent sources, not a single channel.
• Honest signals only. Fabricated proof is fragile and, when detected, costly. See the honesty principle on the methodology page.

What it is. Being named and referenced by sources an AI system can reach and read: directories, press, references, and communities.

Why AIOFacts includes it. A system retrieving material about an entity can only draw on what exists to be retrieved. Where reputable sources describe an entity in context, there is more material available and more of it corroborates. How that translates into any particular answer is not observable from outside.

In practice.

• Presence in the directories and references relevant to your category.
• Mentions in press, communities, and third-party writing that AI systems crawl.
• Context that matches your category, so each citation reinforces the same entity.

What it is. Schema.org markup and machine-readable facts, name, category, location, offerings, published per the schema.org vocabulary. Structured Data states in a format built for machines what your prose states for people.

Why AIOFacts includes it. Prose has to be interpreted; structured data is parsed. Where facts are marked up explicitly, they do not have to be inferred. This is the best-documented signal in the framework: schema.org publishes the vocabulary, and search platforms document which types they consume and how.

In practice.

• Schema.org markup for the entity type that fits you, with its key properties filled.
• Machine-readable facts that match the plain-language ones (see Semantic Consistency).
• Markup kept current, so the structured facts never drift from reality.

What it is. The same name, category, and claims across every source you control. Where sources you publish contradict each other, there is no way for a reader, human or machine, to tell which is current.

Why AIOFacts includes it. A system assembling a description reconciles many sources. Where they conflict on the name, category, location, or claims, something has to be discarded, and the entity does not control what. How AI assistants resolve such conflicts, and whether they favor a brand’s own pages or third-party sources, is an open question set out on the Editorial Method.

In practice.

• One name, one category, one description, repeated faithfully wherever you appear.
• Facts that match across your site, your markup, directories, and citations.
• Corrections propagated everywhere, so an old version does not contradict the current one.

What it is. Public, crawlable pages. A crawler cannot read what it is not served, so material behind forms, logins, or scripts it does not execute is not part of what a system has to work from.

Why AIOFacts includes it. This is the precondition for the other six: clarity, reputation, citations, and markup are only available to a system that can fetch the page carrying them. Which crawlers a site admits is set by its own robots directives and server responses, both of which are publicly checkable.

In practice.

• Your most important knowledge published on public, crawlable pages.
• Content readable without a login, a form, or a step a crawler cannot complete.
• Clean, accessible markup so systems can parse what they reach.

What it is. A distinct, well-connected entity rather than one of several similar names. In this framework Brand Recognition is the cumulative result of the other six signals holding over time.

Why AIOFacts includes it. Where an entity appears repeatedly, described consistently, and corroborated by other sources, there is less left to reconcile. This is the least measurable signal in the framework, and it is included as reasoning rather than as a documented mechanism. It should be read as an AIOFacts position.

In practice.

• A consistent brand entity that connects your knowledge, proof, and people.
• Repeated, coherent presence across the sources systems read.
• Clear association with the category you want to be recommended within.