Person Schema and Author Entities: E-E-A-T for AI

An author entity is a recognized person, not just a name in a byline. Person schema turns that byline into a machine-readable entity with verifiable expertise and connections, which is how AI systems judge whether the content behind it is worth citing.

Why authorship matters more for AI

Google’s E-E-A-T framework, experience, expertise, authoritativeness and trustworthiness, has always rewarded content tied to credible people. AI systems raise the stakes. When a model synthesizes an answer it is implicitly deciding whose information to rely on. Content attributed to a recognizable expert, consistently, across a coherent body of work, gives it a reason to trust you. An anonymous or contradictory byline gives it none.

Be precise about the mechanism, though: Google has said author markup is not a ranking factor in itself. What it does is make the person identifiable and connectable. That identification is what feeds attribution, entity resolution, and the trust judgments that follow.

This matters disproportionately for small companies. A person is far easier to resolve uniquely than a company name, which is why founders and named authors are often the strongest distinguishing attribute a small brand has, as covered in entity disambiguation.

From byline string to Person entity

The shift is the one behind all entity SEO: move from strings to things. A plain text byline is a string. A Person entity with a stable identifier, real attributes, and verified external references is a thing the system can recognize wherever it appears.

That entity should:

• Have its own stable @id, for example https://example.com/authors/jane-doe/#person.
• Be referenced from every BlogPosting.author rather than redefined each time.
• Connect back to your Organization through worksFor, and from the Organization through founder where it applies.
• Carry a short sameAs list of authoritative profiles verifying the same individual.

The properties worth including

knowsAbout is the quietly useful one: it states the person’s subject area in machine-readable form, which helps connect an author to a topic rather than only to a company.

A complete Person example

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Person",
      "@id": "https://example.com/authors/jane-doe/#person",
      "name": "Jane Doe",
      "url": "https://example.com/authors/jane-doe/",
      "jobTitle": "Founder & Lead Strategist",
      "description": "Founder and lead strategist at Example Agency, specializing in technical SEO and generative engine optimization.",
      "worksFor": { "@id": "https://example.com/#organization" },
      "knowsAbout": [
        "Generative Engine Optimization",
        "Technical SEO",
        "Structured data"
      ],
      "image": "https://example.com/authors/jane-doe.jpg",
      "sameAs": ["https://www.linkedin.com/in/janedoe/"]
    },
    {
      "@type": "BlogPosting",
      "@id": "https://example.com/blog/post/#article",
      "headline": "A post title",
      "author": { "@id": "https://example.com/authors/jane-doe/#person" },
      "publisher": { "@id": "https://example.com/#organization" }
    }
  ]
}

The @id is what lets your connected Organization graph tie content to author to brand. Reference the person from each article’s author property and the whole thing links up.

One implementation note worth copying: emit the full Person node on article pages, not just a reference to the author page. Engines and AI systems parse each URL independently, so a page carrying only author: {"@id": "..."} leaves the author unqualified unless the author page happens to be fetched as well. That is how this site is built.

What a real author page needs

Schema declares the relationships, but the page is what engines resolve the entity to. A credible author page states:

• Who the person is and what they actually do, in plain sentences.
• Their specific expertise and how it was acquired, including the unglamorous parts.
• What they write about, with their published work listed.
• Links to the profiles named in sameAs.
• A real photo, used consistently everywhere else.

Avoid the one-line marketing bio. It gives neither readers nor machines anything to verify.

The signals that build author trust

1. Consistent identity across the web

Use the same name, title, and photo everywhere. Inconsistency splits one person into several weak entities. sameAs links to LinkedIn, a personal site, or a knowledge base let systems merge those references into one confident identity. What belongs in that list is covered in the sameAs guide.

2. A coherent body of work

Trust accrues to authors who publish repeatedly in a defined area. Scattered content across unrelated topics reads as generalist noise; a focused portfolio reads as expertise. This is the experience and expertise of E-E-A-T made visible.

3. External corroboration

Being cited, quoted, or profiled by reputable third parties verifies expertise independently. You cannot self-declare authority. You demonstrate it and let others confirm it, which is the slow work covered in digital PR for AI search.

4. Attribution on the page, not just in markup

The byline should be visible, linked to the author page, and accompanied by a real bio. Markup that asserts an author the page does not visibly credit is inconsistent, and inconsistency is what lowers confidence.

Author signals at a glance

Common mistakes

• “Admin” or “Marketing Team” as the author. No entity, no trust, no attribution.
• Redefining the person inline on every post with slightly different titles.
• A sameAs list of every social account, including abandoned ones.
• Invented credentials. Contradictions with verifiable sources cost more than the claim gains.
• An author page that is a bio and nothing else, with no listed work.
• Changing the @id when the author page URL changes, without redirecting.

Where author entities fit

Author entities are the human half of your brand entity. The organization says what the company is; the person says who stands behind the claims. AI systems weigh both, and small brands usually find the person is the easier of the two to make unambiguous.

If you want to know whether engines currently recognize your authors as entities at all, request an AI visibility audit, or see our schema markup service for the implementation.