Person schema: The most underused EEAT lever

Person schema declares who wrote a piece of content, where else they exist on the web, and what they are an authority on. Engines use it to build an author entity profile and to weight content quality.

Minimum viable Person schema

Here are the key things to understand. None of them are complicated on their own, but together they change how you approach this.

• name, image, jobTitle, worksFor.
• description (one paragraph, factual).
• sameAs array with LinkedIn, GitHub, Twitter, Crunchbase, professional bodies.
• knowsAbout array with the topics you cover.

Where to place it

On the author bio page (canonical) and embedded inside Article schema as the author property on every post. Keep both versions in sync.

Common mistakes with Person schema

Most implementations fail quietly. The schema validates fine but does not actually help because the underlying data is thin or inconsistent.

• sameAs links that point to inactive or near empty profiles.
• A different job title or name spelling between the bio page and the Article markup.
• No knowsAbout field, leaving the model to guess the author's actual expertise.
• Person schema added to a generic "team" byline instead of a real named individual.

Rolling it out across multiple authors

A site with several contributors needs a consistent process, otherwise Person schema quality varies wildly by whoever wrote the template first.

1. Create one canonical bio page per author with a stable URL.
2. Build a shared component that reads author data once and renders both the visible bio and the schema.
3. Require sameAs, jobTitle and knowsAbout as mandatory fields before a post can publish.
4. Review author pages quarterly for stale roles or dead profile links.