Person and Author Schema for E-E-A-T

Who wrote your content matters as much as what it says, and Person schema is how you make sure search engines and AI systems know exactly who that is. In an era where Google evaluates content through E-E-A-T (Experience, Expertise, Authoritativeness, and Trustworthiness) and AI systems reason about entities, a real, verifiable author behind your content is a genuine competitive advantage. Person schema is the structured-data record that turns your authors from names on a page into recognized entities with credentials, expertise, and verifiable identity.

Here's the encouraging reality: building strong author entities is entirely within your control, it directly strengthens your E-E-A-T signals, and most sites still publish under thin or generic bylines that leave all this value on the table. This guide shows you how to build author entities that establish real authority: the properties that matter, the sameAs strategy that does the heavy lifting, and how to connect your authors into your broader entity picture. Let's make your experts recognized.

Why author identity matters more than ever

Three shifts make author entities genuinely important in 2026, not just nice-to-have.

Search indexes entities, not just pages. Modern search doesn't only index your content, it identifies the entities involved, including the author. An author is a Person entity, and connecting your content to a recognized author entity is central to how Google understands and trusts it. Thin, anonymous, or ambiguous authorship means Google can't attach expertise to your content; a clear author entity means it can.

E-E-A-T runs on verifiable authorship. Google's quality framework leans heavily on whether real people with genuine expertise stand behind content. Google's own Quality Rater Guidelines explicitly direct raters to look up the authors of content when evaluating its quality. Person schema with rich, verified profile links makes that lookup unambiguous: it hands Google the evidence that a real, credentialed human wrote this. Without it, Google infers authorship from your page's HTML and often gets it wrong.

AI systems name the authors they understand. When AI answers cite or describe sources, a clearly structured author entity (with a defined role, expertise, verified links, and a body of work) gives these systems a confident, machine-readable person to name. In a world where AI is increasingly the front door to discovery, that structured clarity is how your experts get named and cited rather than overlooked.

The through-line: your authors are entities, and making them clear, verifiable entities strengthens your content's credibility everywhere it's evaluated. That's the job Person schema does.

First, clear up the confusion: Person, Organization, or ProfilePage?

Three types get muddled here, and using the right one for each situation matters. Here's the plain-terms decision:

Use Person when a real human with a public identity wrote the content. This is the right answer the vast majority of the time: a named writer with a bio and professional presence. Person is the author entity.

Use Organization when content is brand-authored with no individual byline, like a company blog post credited to "The Acme Team" or "Acme Editorial." When there's genuinely no individual author, the organization is the author.

Use ProfilePage on dedicated author bio pages specifically. ProfilePage isn't an alternative to Person, it wraps a Person entity on that person's own profile page, and adds page-level details like when the profile was created and last updated. So an author's bio page uses ProfilePage (containing their Person entity); the articles they write reference that same Person as the author.

The clean mental model: Article describes the content, Person describes the author, Organization describes the publisher, and ProfilePage is the author's own bio page. You connect them with @id references so everything is unambiguous. Mixing them up (putting ProfilePage on an article, or using Organization for a real human writer) confuses the signal. If you want to see how these fit alongside the rest of the vocabulary, our schema types library lays them out side by side.

The core Person properties

A strong author entity is built from a handful of properties. Only name is strictly required, but the recommended floor for a genuinely useful author entity is:

• name: the author's full name, matching the byline on the page exactly
• url: the author's bio page on your site
• image: a photo of the author
• jobTitle: their role ("Senior Financial Analyst," "Head Roaster")
• worksFor: the organization they work for, connected to your Organization entity
• alumniOf: educational institutions, which establish expertise
• knowsAbout: the subjects they're expert in
• description: a concise bio
• sameAs: links to their verified external profiles (the highest-leverage field, covered next)

Fill these in and you've turned a byline into a credentialed entity: a named person, with a role, an employer, an education, defined areas of expertise, and verifiable identity. That's the difference between "some words by someone" and "content by a recognized expert."

A complete author example

Here's how an author entity connects to the content they wrote, a Person referenced as the author of an Article:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to Choose a Single-Origin Coffee",
  "datePublished": "2026-08-01",
  "author": {
    "@type": "Person",
    "@id": "https://example.com/authors/maria-santos#person",
    "name": "Maria Santos",
    "url": "https://example.com/authors/maria-santos",
    "image": "https://example.com/authors/maria-santos.jpg",
    "jobTitle": "Head Roaster",
    "worksFor": { "@id": "https://example.com/#organization" },
    "knowsAbout": ["specialty coffee", "single-origin roasting"],
    "sameAs": [
      "https://www.linkedin.com/in/mariasantos",
      "https://www.wikidata.org/wiki/Q00000000"
    ]
  },
  "publisher": { "@id": "https://example.com/#organization" }
}

Notice the structure: the Article is the content, the author is a Person with a stable @id, worksFor and publisher reference the same Organization by @id, and the author carries sameAs links to their verified profiles. That's a complete, connected picture: content, author, and publisher, all unambiguous.

sameAs: the field that does the heavy lifting

If there's one property that makes or breaks an author entity, it's sameAs, and most implementations treat it as an afterthought. It deserves real attention, because it's how Google disambiguates your author from every other person who shares their name.

Think about it: how many people share your author's name? sameAs is how you prove which one they are, by connecting their author profile to their verified representations across the web. The more authoritative profiles you point to, the stronger that disambiguation, and the more confidently Google and AI can attach the right expertise and reputation to the right person.

Not all profiles carry equal weight, so prioritize:

Wikidata is the strongest single signal. A sameAs link to a Wikidata entry often does more for entity recognition than five social links combined, because Wikidata is a structured entity database Google reads directly. If your author doesn't have a Wikidata entry, you can create one (it's open), a genuinely high-leverage move for a key author.

LinkedIn provides authoritative professional verification. LinkedIn acts as a trusted, independent source for professional credentials, so linking your author to their LinkedIn profile gives Google real-world verification of their experience and role.

Wikipedia, for established authors, is powerful but rare and requires genuine notability.

High-trust niche profiles matter in relevant fields: Muck Rack for journalists, Crunchbase for founders, IMDb for entertainment, professional registries for licensed fields.

Professional platforms like GitHub and Stack Overflow for developers, or ORCID for researchers, are solid expertise signals.

Social profiles (X, Mastodon, Bluesky) are useful but lower weight; include only actively maintained accounts.

The rule: link to real, verified, active profiles that genuinely belong to the author, and prioritize the authoritative and structured ones. A sameAs array anchored by Wikidata and LinkedIn is worth far more than a long list of dormant social links.

Define once, reference everywhere

Here's the pattern that turns individual author markup into a genuine author entity: the stable @id.

Give each author a stable @id, typically their bio page URL plus a fragment, and reference that same @id from every article they write, rather than redefining their full details on each post. This is exactly the pattern that makes your Organization one entity across your whole site, applied to people.

Why it matters so much: when fifty articles all reference the same author @id, Google understands them as fifty pieces of content by one recognized person, building that person's authority and body of work. When each article instead carries slightly different, independently-defined author details, you get fifty fuzzy, potentially-inconsistent author records instead of one strong entity. Define your author once, ideally in the ProfilePage on their bio page, and reference them everywhere else. It's the single most important structural decision for author entities.

Building real credentials: worksFor, alumniOf, knowsAbout

Three properties do the specific work of establishing expertise, and they're where author entities get genuinely strong for E-E-A-T:

worksFor ties the author to your Organization for their current role, connecting the person to the company entity. This is part of what stitches your people and your brand into one connected entity graph.

alumniOf links the author to the educational institutions they attended, establishing the foundation of their expertise by connecting them to recognized EducationalOrganization entities. For expertise-driven content, an author's credentials genuinely matter, and alumniOf makes them machine-readable.

knowsAbout declares the author's areas of expertise. As with your brand's topical authority, connecting these to recognized, disambiguated topic entities rather than loose keywords is what makes the signal strong. An author who knowsAbout a specific, recognized subject, and who has a body of content demonstrating it, is exactly the kind of expert entity these systems trust.

Together, these three build a credentialed expert: someone with a verifiable role, education, and defined expertise, all connected into the wider entity graph. That's the substance behind E-E-A-T, made structured.

ProfilePage: for author bio pages

Every editorial site should have a dedicated bio page per author, and those pages are where ProfilePage earns its place.

On an author's bio page, use ProfilePage to wrap their Person entity. ProfilePage adds page-level context (when the profile was created and last updated) that signals to Google this is the canonical, maintained profile for that person. The Person entity inside it carries all the properties above: role, employer, education, expertise, and sameAs links. Note that role-related properties like jobTitle and worksFor belong to the nested Person, not to the ProfilePage itself.

This gives you a clean architecture: the author's bio page is their canonical ProfilePage (with their full Person entity), and every article they write references that same Person by @id. The bio page is the author's home; the articles point back to it. That structure is exactly what lets Google and AI build a complete, confident picture of the author across everything they've written.

Connecting authors to your brand

Author entities don't exist in isolation. They're part of your organization's entity graph, and connecting them properly strengthens everyone.

When your authors (Person entities) connect to your brand (Organization) via worksFor and publisher, and your brand connects back to its people, you build a rich, interconnected picture: a recognized organization, staffed by credentialed experts, publishing content in their areas of expertise. That connected graph is far more powerful than isolated author records or a faceless brand.

This is the same entity thinking that underpins your whole brand entity profile, and your people are one of its most important dimensions. A brand whose expertise is embodied in named, credentialed, verifiable people is more trustworthy to both Google and AI than an anonymous one. Your authors are part of your entity, and modeling them as connected Person entities is how you make that real. (The Organization schema guide covers the brand side of this connection.)

A special note on YMYL content

If you publish content in "Your Money or Your Life" areas (health, finance, legal, safety), author credentials aren't just helpful, they're central to how your content is evaluated.

For these fields, make your authors' credentials verifiable through sameAs. A medical author with a link to their verifiable state medical license, or a financial author linked to their professional registration, has substantially stronger E-E-A-T than the same author without those verifications. Google evaluates YMYL content especially rigorously on the expertise and trustworthiness of who's behind it, so linking to professional registries, license verifications, and credential databases in your authors' sameAs arrays is genuinely important. For YMYL, an unverified expert and a verified one are treated very differently, so make yours verifiable.

Common mistakes to avoid

The errors that most weaken author entities:

Generic or anonymous bylines. "By Admin" or "By The Team" on content genuinely written by a real expert wastes the E-E-A-T opportunity. Use real, named authors with full entities where a real person wrote the content.

Name mismatches. If your page says "Jane Doe, Editor at X" but your schema says "Jane D., Writer at Y," Google flags inconsistent markup and may ignore it entirely. The schema must match the visible byline and bio exactly.

Thin sameAs. Missing the disambiguation opportunity, or listing only dormant social links. Anchor it with Wikidata and LinkedIn, and use real, active, authoritative profiles.

Redefining authors per article instead of using a stable @id. This creates many fuzzy records instead of one strong entity. Define once, reference everywhere.

Broken @id references. Inconsistent or mistyped @id values break the connections between your Article, Person, and Organization, undoing the entity graph you're building.

Using ProfilePage on articles. ProfilePage belongs on bio pages; articles use Person as the author. Mixing them confuses the structure.

Unverifiable credential claims. Claiming expertise or credentials the author doesn't have, or that can't be verified, undermines trust rather than building it. Keep it real and verifiable.

Implementing it on WordPress

Author markup is one of the most valuable and most under-implemented things on WordPress sites, and your approach should make it consistent and maintainable.

Check what your theme or SEO plugin outputs for authors. Many produce minimal author markup, often just a name, missing the sameAs, credentials, and @id connections that make an author a genuine entity.

The challenge is consistency and connection. Doing this well means each author defined once with a full entity, referenced by stable @id across all their articles, connected to your Organization, with rich sameAs and credentials, and kept accurate as roles and profiles change. Hand-maintaining that across a multi-author site with a growing content library is exactly where it breaks down.

Generating from your author and content data is what makes it consistent. AI Schema Gen builds connected author entities from your content: Person entities with sameAs, credentials, and expertise, referenced consistently across every article and connected to your Organization. It also weaves your authors into your broader entity profile, which is where their E-E-A-T value compounds. Because it generates from your live content, author details stay consistent and accurate as they change. Whatever route you take, the tests are: is each author a full entity (not just a name); is each defined once and referenced by @id; are they connected to your brand; and does the markup match the visible bylines and bios.

Person schema and AI search

To bring it together: as AI becomes how people discover and evaluate content, the authors AI systems can understand are the authors they can name. A clearly structured author entity, with a defined role, verified links, established expertise, and a connection to a recognized organization, gives AI systems a confident entity to cite and describe. An anonymous or ambiguous author gives them nothing to hold onto.

This compounds over time. Every article connected to a strong author entity reinforces that person's authority; every credential and verified link makes them more trustworthy to the systems evaluating your content. The result is authors who get named and cited rather than overlooked, and content that carries the credibility of recognized experts. That structured clarity, the same principle behind appearing in AI Overviews, is how your expertise gets recognized in an AI-driven search world.

Validating your author schema

Google's Rich Results Test validates your author markup as part of Article eligibility and flags errors like missing or mismatched fields.

The Schema Markup Validator at validator.schema.org checks your Person and ProfilePage syntax generally.

Check your connections. Author @id values should be consistent across articles, worksFor and publisher should resolve to your Organization, and every sameAs link should work and point to the right person.

Confirm the match. Your schema author details should exactly match the visible byline and bio on the page. Mismatches are the most common cause of author markup being ignored.

Publishing content by real experts? AI Schema Gen builds connected author entities from your content: Person entities with verified profiles, credentials, and expertise, referenced consistently and woven into your brand's entity profile, so your authors get recognized for the authority they have. Start free at aischemagen.com.