How to Create Person Schema for Authors in 2026

Chapter 1. Before you start

Person schema is the structured-data anchor for authorship. Google's Quality Rater Guidelines explicitly tie E-E-A-T to identifiable, qualified authors; AI engines use the same signal to disambiguate the person who wrote a piece from same-named writers on unrelated sites. Without Person schema, both have to infer the author from page HTML and often get it wrong.

• Gather author basics for every byline on the site: full name, role/title, headshot URL, one-sentence bio, and at least one canonical profile (LinkedIn at minimum).
• Decide where author profile pages live. Convention is /about/ or /team/. Each author gets a dedicated URL the Person @id can resolve to.
• Audit existing bylines for "Editorial Team" attributions. Google QRG flags these as Low quality. Replace with named authors before shipping schema.
• Confirm sameAs profile URLs are still accurate. Outdated LinkedIn URLs or sunsetted Twitter handles break the entity reference.

Chapter 2. What does Person schema actually do for SEO + AI search?

Three things, in descending order of importance.

1. E-E-A-T author identification for Google. The Quality Rater Guidelines explicitly direct raters to look up authors when evaluating page quality. Person schema with sameAs links makes that lookup unambiguous.
2. Entity disambiguation for AI engines. ChatGPT, Perplexity, and Gemini ingest Person schema to associate a name with a specific real-world identity. Without it, "Jane Doe" on your site might get conflated with other Jane Does on unrelated topics.
3. Knowledge Graph entity candidacy. Person entries with rich sameAs links (Wikipedia, Wikidata, LinkedIn, professional registries) are candidates for inclusion in Google's Knowledge Graph - which produces Knowledge Panels for the author across all their work.

What Person schema does not do: directly boost rankings of the articles the author writes. The benefit is indirect, through E-E-A-T evaluation and entity matching. Google has stated repeatedly that E-E-A-T isn't a "specific ranking factor"; it's the framework the actual ranking signals try to approximate. Person schema feeds those signals.

Chapter 3. Required and recommended properties

Per Schema.org, Person requires only name. The recommended floor for E-E-A-T purposes is well beyond that:

{
  "@context": "https://schema.org",
  "@type": "Person",
  "@id": "https://www.example.com/about#jane-doe",
  "name": "Jane Doe",
  "alternateName": "J. Doe",
  "jobTitle": "Senior Editor, Example Brand",
  "url": "https://www.example.com/about#jane-doe",
  "image": "https://www.example.com/brand/jane-avatar.jpg",
  "description": "Jane covers analytics and measurement for the Example Brand audience.",
  "knowsAbout": ["GA4", "Google Tag Manager", "Server-side analytics"],
  "alumniOf": {
    "@type": "EducationalOrganization",
    "name": "University of Example"
  },
  "worksFor": { "@id": "https://www.example.com/#organization" },
  "sameAs": [
    "https://www.linkedin.com/in/janedoe",
    "https://x.com/janedoe",
    "https://en.wikipedia.org/wiki/Jane_Doe",
    "https://www.wikidata.org/wiki/Q12345678",
    "https://orcid.org/0000-0000-0000-0000"
  ]
}

Each field above contributes to a specific E-E-A-T dimension: jobTitle + worksFor establish Authoritativeness; alumniOf and knowsAbout establish Expertise; sameAs establishes verifiable identity (Trust). Skip any of these and the corresponding signal weakens.

Chapter 4. The sameAs entity-disambiguation strategy

sameAs is the single most important Person field after name. Every URL you list tightens the entity disambiguation - Google and AI engines can verify that the Jane Doe on your byline is the same Jane Doe with a LinkedIn, an ORCID, a Wikipedia article, and a Wikidata QID.

For YMYL topics (health, finance, legal), the author's professional credentials in sameAs become load-bearing. A medical author with their state medical license verifiable URL in sameAs has substantially higher E-E-A-T than the same author without it.

Chapter 5. ProfilePage pairing

When you have a dedicated author bio URL (recommended for every editorial site), ProfilePage wraps the Person schema and adds page-level metadata. Google's ProfilePage documentation covers the requirements.

{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "dateCreated": "2024-01-15T12:00:00-05:00",
  "dateModified": "2026-05-20T08:00:00-05:00",
  "mainEntity": {
    "@type": "Person",
    "@id": "https://www.example.com/about#jane-doe",
    "name": "Jane Doe",
    "jobTitle": "Senior Editor, Example Brand",
    "image": "https://www.example.com/brand/jane-avatar.jpg",
    "description": "...",
    "sameAs": ["https://www.linkedin.com/in/janedoe", "..."]
  }
}

ProfilePage is appropriate for any page whose primary focus is a single person: forum user profiles, news site author pages, "About Me" pages on personal blogs, employee pages on company sites. It's not appropriate for general About-Us pages (those use AboutPage with an embedded Organization).

Chapter 6. Where do you place Person schema on the site?

Two locations. Both serve different purposes.

The pattern: ship full Person details once on the canonical profile page, then reference by @id from every Article that author wrote. This centralizes truth and means you only update Person details once when something changes (new role, new sameAs link, updated bio).

Don't ship Person schema in isolation on Article pages without a @id reference to a canonical profile URL. Inline-only Person records create orphan entities that AI engines can't link back to a sustained identity. See post #7, the Article schema guide, for the author @id reference pattern in BlogPosting.

Chapter 7. The breakages we see most often

Ranked by frequency across 47 content audits over the past 24 months:

• No Person schema on author bylines: Google has to infer author from HTML. 28 of 47 audited sites.
• Person schema with only name (no sameAs, no jobTitle, no image): entity disambiguation effectively zero. 22 of 47.
• sameAs contains plain handles like "@janedoe" instead of full URLs: not a valid sameAs value. 19 of 47.
• No @id on Person, so multiple Articles by the same author look like different entities. 14 of 47.
• "Editorial Team" or anonymous bylines: QRG Low-quality flag. 11 of 47.
• worksFor as string instead of Organization @id reference: breaks the Person-to-Organization entity graph. 9 of 47.
• Outdated sameAs URLs (LinkedIn redirects, deleted Twitter accounts): dead-end entity references. 7 of 47.

We track Person schema integrity through our Sentry product; the structured-data rule set catches every breakage above on running sites.