AEO for Who Queries: Person, Author, and Founder Citation Strategies

TL;DR

• Give every named person on your site a canonical bio URL (e.g. /people/) with Schema.org Person markup.
• Open the bio with a one-paragraph extractable summary: name, role, organization, one notable fact. AI engines lift this paragraph for who-is queries.
• Cross-reference identity via sameAs: Wikipedia, Wikidata, LinkedIn, and the person's professional homepage.
• Set jobTitle, worksFor, and affiliation consistently. Drift between sources confuses AI engines and lowers citation confidence.
• Authoritative photo with structured image property reinforces entity identity for AI knowledge graphs.

Why who queries are an AEO category

"Who is X" prompts dominate ChatGPT and Perplexity for any person with public-facing visibility — founders, authors, executives, researchers. The AI cites the source it can disambiguate fastest and most confidently. That source is rarely the person's own LinkedIn (because LinkedIn is gated and not freely crawled); it is whichever public bio page has the cleanest entity graph.

The stakes are real: who-is citations drive brand impressions at the top of the funnel, and they propagate into related queries ("X's company", "X's most cited paper", "X's investors"). Owning the canonical bio is leverage.

The 7 elements of a citation-ready bio page

1. Canonical URL with the person's slug

Use a stable per-person URL like /people/jane-doe or /team/jane-doe. Avoid bundling multiple people on a shared page; AI engines need one-person-one-URL to cite confidently. Keep the slug to first-last name format, not nicknames or job titles.

2. Schema.org Person markup

Use Person JSON-LD with these required properties:

• name: the person's full name as commonly used.
• jobTitle: current role.
• worksFor: employing organization (with its own Organization markup).
• url: the canonical bio URL.
• image: link to an authoritative photo.

Add givenName and familyName separately when the name is non-Western or includes initials, so AI engines parse the components correctly.

3. sameAs cross-references

List every authoritative external profile in the sameAs array:

• Wikipedia article URL (if any).
• Wikidata entity URL (e.g. https://www.wikidata.org/wiki/Q123456).
• LinkedIn profile URL.
• Personal homepage or academic page.
• ORCID iD for researchers.
• GitHub profile for engineers.

The more authoritative cross-references, the higher the disambiguation confidence on the AI side.

4. One-paragraph extractable bio

The first paragraph below the H1 should answer "who is this person" in 2-4 sentences:

Jane Doe is the CEO of Acme Inc., a Series-B SaaS company in observability. She previously led platform engineering at Example Corp and authored Observability for Distributed Systems (O'Reilly, 2024).

AI engines lift this paragraph as the snippet for who-is queries. Lead with name + role + organization, then add one notable fact (book, talk, prior role).

5. Consistent identity across sources

Drift between your bio page, LinkedIn, Wikipedia, and Wikidata is the most common reason AI engines down-weight a citation. Audit:

• Job title matches across all three sources.
• Company name uses the canonical legal entity name.
• Photo is consistent (same headshot, not different photos per platform).
• Birth year (if public) matches Wikidata.

6. Authoritative photo with structured image property

Use a single canonical headshot. Mark it with image in JSON-LD and serve it from a stable URL. The same photo on LinkedIn, your bio page, and Wikidata reinforces entity identity.

7. Cross-link from author bylines

Every article authored by the person should link from the byline to the canonical bio URL. This builds an internal authorship graph that AI engines crawl when answering "who wrote X?".

5 worked examples

1. Author bio on a publisher site — a canonical /authors/jane-doe page with Person schema, sameAs to Wikipedia/Wikidata/LinkedIn, a 3-sentence intro paragraph, and bylines linking back to it from every article.
2. Founder page on a startup site — /team/john-smith with Person schema, jobTitle="CEO", worksFor linking to the company's Organization schema, sameAs to LinkedIn and Crunchbase.
3. Researcher page on a university site — ORCID iD in sameAs, Wikidata entity link, list of publications with Article schema cross-referencing the author.
4. Open-source maintainer — GitHub profile in sameAs, package authorship documented in SoftwareApplication schema, byline links from the project blog.
5. Executive on a public company site — Person schema with award, alumniOf, and knowsAbout properties, sameAs to Wikipedia and the SEC EDGAR filer page.

What to avoid

• Generic team-page-with-grid layouts where each person is a card without a dedicated URL.
• Inconsistent name formatting across the site (Jane Doe vs. J. Doe vs. Doe, Jane).
• Missing worksFor linkage when the person's affiliation is the central disambiguator.
• Outdated jobTitle that drifts from LinkedIn.
• Skipping Wikidata. Even a thin Wikidata entity creates a strong identity anchor.

FAQ

Q: Do I need a Wikipedia article for AI engines to cite my bio?

No, but a Wikipedia or Wikidata entry significantly improves disambiguation for common names. If a Wikipedia article is unrealistic, a thin Wikidata entity (created via wikidata.org) provides much of the same anchor effect.

Q: Should every employee have a bio page?

Not necessarily. Prioritize people who appear in external citations: founders, authors, public-facing executives, and researchers. Internal-only roles do not need AEO-grade bio pages.

Q: What if a person uses multiple names professionally?

Use the most common professional name as name, list other forms in alternateName, and let sameAs carry the canonical identity across platforms. AI engines handle the disambiguation when the entity graph is consistent.

Q: How do I handle people who change roles or companies?

Update jobTitle and worksFor same-day, bump dateModified, and refresh the one-paragraph bio. Old roles can move into a description or a brief history paragraph; do not delete them.