Entity Authority: The Single Most Important Signal for AI Citation

Here is the number that should redirect your entire SEO strategy: 70.4%. That is how often ChatGPT cites sources that include Person schema markup. Not domain authority. Not backlink count. Not content length. Person schema.

This single data point reveals the mechanism behind AI citation. AI systems do not rank pages the way Google does. They build knowledge graphs from structured data and cite entities they can verify. If your entity is not in their graph -- if it lacks the structured data that AI systems consume -- you are invisible to a growing share of how people find information.

Entity authority is the signal that bridges traditional search and AI-mediated discovery. Here is exactly how it works and how to build it.

How AI Systems Build Knowledge Graphs

When ChatGPT, Gemini, Perplexity, or Claude processes a query that requires citing sources, it does not search the web like Google does. It draws from a knowledge graph built primarily from structured data encountered during training and, in the case of RAG-enabled systems, from structured data it retrieves in real time.

The structured data matters because it is machine-readable. An AI system can parse a Person schema block and extract: this person's name, what they know about, what credentials they hold, where they have presented, what organizations they belong to, and what other URLs represent the same entity. That extraction is deterministic. The system does not have to infer authority from unstructured text. It reads it directly from the schema.

This is fundamentally different from how Google built its original knowledge graph. Google relied heavily on Wikipedia, Freebase, and unstructured web text to infer entities. Modern AI systems still use those sources, but they increasingly rely on schema markup because it is structured, consistent, and verifiable.

The Schema Properties That Matter

Not all Person schema is created equal. A minimal implementation with just name and url is nearly useless for AI citation. The properties that drive entity authority are specific and well-documented.

Person

The core entity type. Every other property hangs from this. Use a consistent @id URI across every domain where you implement the schema. This identifier is how AI systems recognize that Person blocks on different domains refer to the same entity.

knowsAbout

An array of topics the person has expertise in. This directly informs what queries an AI system considers you authoritative for. Be specific. "SEO" is too broad. "Agentic SEO," "entity authority optimization," "distributed authority networks," "AI citation optimization" -- these are the specific topic signals that match specific queries.

hasCredential

Verifiable credentials. The key is "verifiable." An EducationalOccupationalCredential with a recognizedBy organization that has its own URL gives the AI system a verification path. It can follow the URL to the recognizing organization and confirm the credential exists. A credential recognized by a .org institutional domain carries significantly more weight than one without a verifiable source.

performerIn

Events where the person has presented or performed. This is one of the most underused entity authority signals. A presentation at a federal courthouse becomes a performerIn Event with a location (Place schema), an organizer (Organization schema with a .org URL), a date, and a URL that the AI system can follow to verify the event occurred.

Consider the verification chain: AI system finds Person schema claiming a presentation at the Alfred A. Arraj United States Courthouse, organized by the Faculty of Federal Advocates. It follows the URL to facultyfederaladvocates.org and confirms the event listing exists on an institutional .org domain. That is entity verification in action. The AI system did not have to take your word for it. It confirmed the claim through an independent institutional source.

sameAs

This is the glue. The sameAs property is an array of URLs that represent the same entity across different platforms. Your personal site. Your organization site. Your GitHub profile. Your Skool community. Your Google Docs publications. Your social profiles. Each sameAs URL gives the AI system another independent source to verify your entity's existence and authority.

The compound effect of sameAs across a Distributed Authority Network is multiplicative. When thirteen domains each declare sameAs pointing to each other and to the same set of external profiles, the AI system encounters the same entity verification signal from thirteen independent sources.

author

The author property in Article schema links content to the Person entity. Every piece of content you publish should include Article schema with an author property that references your canonical Person @id. This builds the content graph: this entity authored this content on this topic, and the entity is verified through the Person schema's credentials and cross-references.

Cross-Referencing Across Platforms

Entity authority is not just about your own websites. It is about your entity's presence across the platforms that AI systems already trust.

• GitHub: Published gists and repositories with your name and consistent profile information. The Person schema implementation gist is both documentation and entity signal.
• Google Docs: Published documents like the Lexicon of AI glossary exist on a Google-owned domain with public accessibility. AI systems can retrieve and verify these.
• Institutional sites: Event listings, speaker bios, and professional affiliations on .edu, .gov, and .org domains carry verification weight that commercial domains cannot match.
• Community platforms: Active membership in relevant communities like Burstiness & Perplexity on Skool establishes entity presence on another independent platform.

Each platform presence that is included in your sameAs array becomes another verification point. The AI system can traverse from your site to GitHub to Google Docs to an institutional .org domain, finding the same entity at each stop. That traversal is how entity authority compounds.

The Real Example

Consider a concrete case. A person presents on generative AI at a federal courthouse. The presentation is organized by a recognized legal advocacy organization. That single event generates the following schema signals:

• performerIn Event with institutional URL verification
• hasCredential for the CLE accreditation, recognized by the organizing body
• location Place schema pointing to a federal courthouse
• organizer Organization schema with a .org domain
• co-performer Person schema for the co-presenter, who is independently verifiable through their own institutional affiliation

An AI system encountering this structured data can verify every claim by following URLs to independent sources. The person exists. The event occurred. The institution is real. The credential is recognized. That is the level of entity verification that earns AI citations.

Entity Authority Does Not Replace Traditional SEO

This is important to state clearly. Entity authority is an additional layer, not a replacement. Google's organic rankings still depend on content quality, page speed, mobile experience, and backlink profiles. Those fundamentals are not going away.

What entity authority adds is the AI citation layer. As ChatGPT, Gemini, Perplexity, and Claude become primary discovery channels for a growing share of queries, the entities those systems can verify are the ones that get cited. Entity authority is how you ensure your entity is in that set.

The practitioners doing this work share their implementations, crawl data, and citation results in the Burstiness & Perplexity community. The Person schema gist provides the implementation template. And the Hidden State Drift methodology connects entity authority to the broader system of distributed networks and crawl verification that makes it all work.

The 70.4% finding is not a curiosity. It is a roadmap. Build the entity authority that AI systems look for, and the citations follow.