Author Schema and AEO: Why E-E-A-T Person Markup Matters Now

From nice-to-have to structural

Author schema (Person markup with credentials, sameAs links, jobTitle, knowsAbout) was, until recently, a small SEO nicety. Google paid lip service to E-E-A-T but did not heavily reward author markup.

That changed. AI engines weight author signals more strongly than legacy Google search did, especially Claude and AI Overviews. Pages with complete Person markup cite at measurably higher rates on questions that benefit from authoritative sources - medical, financial, legal, technical, and any niche where credentials matter.

The reason is mechanical. AI engines need to assess source authority quickly. Person markup is the cleanest machine-readable signal for "who wrote this and why should the engine trust them." Pages without it leave the engine guessing.

What to include in Person markup

A complete Person schema for a content author has six core fields plus optional extensions.

name. Full name as the author publicly uses it.

jobTitle. Current professional title with employer if relevant.

worksFor. Organization markup pointing to the employer (with its own Organization schema).

sameAs. Array of URLs to verified profiles: LinkedIn, Twitter, ORCID for academics, GitHub for technical authors, professional licensing pages where relevant. Each sameAs entry is a credibility anchor.

alumniOf. Educational background as Organization references. Engines weight this for authority-sensitive queries.

knowsAbout. Array of topics the author has demonstrated expertise on. This is the most underused field; engines use it to match author authority to query topic.

Optional extensions: award (notable recognition), hasCredential (specific certifications), description (a 1-2 sentence bio).

A complete Person schema is 200-400 lines of JSON-LD. The investment is one-time per author plus periodic updates as credentials change.

Where to surface author markup

Person markup belongs in three places.

On the article page itself. Wrapped inside the BlogPosting or Article schema's author field. This is the canonical placement engines expect.

On a dedicated /authors/[name] page. A page per author with their bio, credentials, list of articles, and full Person schema. Engines crawl these pages and reinforce the author's representational presence.

Linked from the article body. A visible byline that links to the author page. This is a UX signal and a content signal that compounds the schema effect.

A site with all three patterns gets full credit. A site with only the first (schema buried in JSON-LD with no visible byline) gets partial credit.

What engines actually do with this

Five mechanisms drive the citation lift.

Authority matching. When the engine receives a query on a credentialed topic (medical advice, legal interpretation, financial analysis), it preferentially cites sources whose authors have schema-declared expertise on that topic.

Cross-source verification. sameAs links let engines verify the author exists across the web. An author claimed in schema but absent from LinkedIn or any verifiable third-party source signals possible falsification.

Topic authority graphs. knowsAbout fields contribute to engine-side topic authority graphs. A site with 12 authors collectively claiming expertise on a focused topic builds stronger topic authority than a site with 12 anonymous bylines.

Brand reputation signals. Author authority compounds with organization authority. A respected author at a respected organization cites better than either signal alone.

Long-form citation in answers. Some engines (Perplexity especially) include author names in citations: "according to Jane Doe at Citevera." This is more useful for the cited brand than a URL-only citation because the author name carries through to the user.

Common mistakes

Three patterns appear repeatedly in audits.

Pseudonymous bylines. "By the Marketing Team" or "Editorial Staff" provides zero authority signal. If you cannot put a real name on a piece, the piece will cite worse than equivalent named content.

Outdated credentials. Person schema with 2019 jobTitle and no recent updates is treated as stale. Update author markup when authors change roles, earn new credentials, or publish significant new work.

Inconsistent author identity across the web. "Jane Doe" on your site, "Jane M Doe" on LinkedIn, "Janie Doe" on Twitter. Engines try to reconcile but lose confidence. Pick one canonical name and use it everywhere; sameAs links bind the identities.

Overstating credentials. Engines (and humans) detect inflated claims. "Expert in cloud architecture" without supporting evidence (publications, certifications, public talks) is a credibility risk. Be accurate; understate rather than overstate.

Author markup for solo founders and small teams

A small team often has one or two authors covering many topics. The pattern that works:

Build complete Person markup for each named author. List specific knowsAbout topics that are genuinely your expertise; do not list 50 topics broadly. Quality over breadth.

For content outside your declared expertise, either cite an external expert in the body (and link to their authoritative source) or do not publish. Engines penalize "expert" claiming expertise on everything.

A solo founder with deep expertise in three topics and clean Person markup outcompetes a team of generalists with anonymous bylines.

How Citevera scores this

The Citevera audit checks for Person schema completeness on every analyzed page. The author axis weighs presence, completeness, sameAs verification, and knowsAbout topical alignment with the article content.

The audit flags missing author markup, incomplete Person schema, and topical mismatches (an article on financial planning written by an author whose knowsAbout claims marketing expertise). It also surfaces opportunities: pages where adding author markup would close a measurable citation gap.

Run a free Citevera audit to check your Person markup completeness

Frequently asked questions

Do I need a real photo for the Person schema?

Yes. The image field on Person schema should point to a real photo on a stable URL. Avatars and stock photos signal lower authenticity. The photo also surfaces in some engine outputs as a credibility cue.

What if multiple authors contributed to one piece?

Use an array in the author field of the Article schema, with one Person object per author. Engines handle multi-author content correctly. List them in contribution order.

Is GitHub a useful sameAs link for non-technical authors?

For technical authors yes, for non-technical authors no. Use sameAs links that genuinely demonstrate the author's professional presence. A null GitHub link or a tumbleweed Twitter account hurts more than helps.

How often should I update Person markup?

When credentials genuinely change. Quarterly for active authors who publish often, annually for less-active authors. Stale Person markup is a smaller issue than missing or wrong markup.

Should I add author markup to landing pages and product pages?

No. Author markup is for content where authorship matters: articles, blog posts, guides, research. Product and landing pages use Organization markup instead. Mixing them creates noise.

Should I add author markup to ghostwritten content?

Use the named expert whose voice the article reflects, not the ghostwriter. The author of record should be someone whose Person markup genuinely supports the content's claims. Pseudonymous bylines or fictional 'editorial team' attributions consistently underperform real-person attribution across all AI engines.

How does Person schema interact with content from rotating authors?

Multi-author publications should maintain individual /authors/ pages for every contributor, with per-article author markup pointing to the right page. Rotating bylines without dedicated author pages signal lower author commitment and underperform. The investment per author is one-time plus periodic updates.