Person Schema for AI Citations

TL;DR

Mark up every author byline with Person and include sameAs URLs to verifiable profiles, jobTitle, affiliation, knowsAbout, and hasCredential. Pair with Article schema's author property so the AI engine can connect content to its creator. Authority signals from a well-formed Person graph drive E-E-A-T scoring across AI surfaces.

Definition

Person is a schema.org type defined at schema.org/Person. It represents an individual human. The most cited Person properties for AI search are sameAs, jobTitle, affiliation, knowsAbout, alumniOf, and hasCredential. Person can be referenced as the author of Article, BlogPosting, MedicalScholarlyArticle, Course, and many other types.

Why Person Schema Matters for AI Citations

AI engines do not cite anonymous content for high-stakes queries. Health, legal, financial, and safety topics surface with author attribution because the engine ranks authority through the author's identity graph.

sameAs is the most important property. Each sameAs URL points the AI engine at a third-party profile that confirms the author's identity. Linking to Wikidata or Wikipedia tells the engine the person is a recognized entity. Linking to ORCID or Google Scholar adds publication-record authority. Linking to LinkedIn confirms current role. The combined graph drives E-E-A-T ranking and influences whether the AI engine cites this author over a less-attributed source.

Required and Recommended Properties

Working JSON-LD Example

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Dr. Jane Doe",
  "url": "https://example.com/authors/jane-doe",
  "image": "https://example.com/authors/jane-doe.jpg",
  "jobTitle": "Principal Researcher, AI Search",
  "affiliation": {
    "@type": "Organization",
    "name": "Example Research Institute",
    "url": "https://example-research.org"
  },
  "knowsAbout": [
    "AI search",
    "information retrieval",
    "large language models"
  ],
  "alumniOf": {
    "@type": "CollegeOrUniversity",
    "name": "University of Example"
  },
  "hasCredential": {
    "@type": "EducationalOccupationalCredential",
    "credentialCategory": "degree",
    "educationalLevel": "PhD"
  },
  "sameAs": [
    "https://www.wikidata.org/wiki/Q00000",
    "https://en.wikipedia.org/wiki/Jane_Doe",
    "https://www.linkedin.com/in/janedoe",
    "https://orcid.org/0000-0000-0000-0000",
    "https://scholar.google.com/citations?user=AAAAAAA"
  ],
  "description": "Researcher and author focused on AI search retrieval and citation grounding."
}

How AI Engines Resolve Person Entities

When an AI engine encounters a Person reference, it attempts entity resolution: matching the markup to a canonical entity in its knowledge graph. The resolution pipeline:

1. Read name plus sameAs from the markup.
2. Cross-reference sameAs URLs against the engine's known entity sources (Wikidata, Wikipedia, ORCID).
3. If matched, attach the author's authority signals (publication count, citation count, third-party recognition) to the cited content.
4. If unmatched, treat the author as anonymous; citation eligibility for high-authority queries drops.

A Person without sameAs to at least one authoritative profile is functionally anonymous to AI engines, even when name and jobTitle are present.

Integration with Article Bylines

The Person object should be referenced from the article's author property:

{
  "@type": "Article",
  "headline": "How AI Engines Rank Authors",
  "author": {
    "@type": "Person",
    "name": "Dr. Jane Doe",
    "url": "https://example.com/authors/jane-doe"
  }
}

Use @id plus sameAs so multiple articles share the same Person identity:

{
  "@type": "Person",
  "@id": "https://example.com/authors/jane-doe#person",
  "name": "Dr. Jane Doe",
  "sameAs": ["https://www.wikidata.org/wiki/Q00000"]
}

Reference by @id from each article reduces duplication and makes the identity graph easier to maintain.

Validation

1. Google Rich Results Test for parseability.
2. Schema.org Validator.
3. CI assertions:
4. name matches the visible byline.
5. At least one sameAs URL is present and resolves to HTTP 200.
6. affiliation.name matches the visible affiliation when shown on the page.

Common Mistakes

• Missing sameAs. The single biggest authority signal. Without it, the author is anonymous to AI engines.
• Generic credentials. Listing hasCredential without credentialCategory or educationalLevel provides little signal.
• Inconsistent identity. Different Person @id values across articles by the same author fragment the identity graph.
• Stale affiliation. Outdated worksFor reduces credibility scoring for time-sensitive topics.
• Fabricated profiles. Linking to a non-existent LinkedIn or ORCID is detected and damages trust scoring.

FAQ

Q: How many sameAs URLs should a Person have?

Three to five well-chosen URLs are typical: a primary identity source (Wikidata or LinkedIn), a publication record (ORCID or Google Scholar), and the author's homepage. Adding ten low-value profiles dilutes the signal.

Q: Do AI engines accept LinkedIn-only as authority?

LinkedIn is a strong signal but stronger when paired with Wikidata or an ORCID identifier. For technical and academic topics, ORCID and Google Scholar add the most value.

Q: Should I add Person schema for guest authors?

Yes. The same rules apply. Guest authors without Person schema reduce the credibility of articles they contribute to.

Q: Does Person schema help with author panels in search results?

It can, but the bigger benefit for AI search is entity resolution, which improves citation quality across all AI surfaces, not only Google panels.