Person schema declares an individual — an author, founder, or expert — as a formal entity, with the name, credentials, and profile links that let Google connect content to a real, identifiable person. As E-E-A-T and entity recognition grow more important, Person schema is how you make authorship machine-readable: it ties an author to their work, their organization, and their reputation across the web, which increasingly influences both rankings and AI citations.
What Person Schema Does
It identifies a human entity and makes claims about them machine-readable — who they are, what they do, and where else they exist online — so Google can attribute content and assess expertise.
Most often it marks up an article author or an About/team page. Paired with Article schema, it answers “who wrote this,” and paired with Organization schema it answers “who do they work for.” That chain — person → article → publisher — is exactly the authorship signal search engines and AI systems use to weigh credibility.
Key Properties
The essentials are name and url; the value-adding ones are jobTitle, worksFor, sameAs (profiles), image, description, and knowsAbout for topical expertise.
sameAs is as important here as it is for organizations — link the person’s authoritative profiles (LinkedIn, a personal site, an ORCID or Wikipedia page where applicable). knowsAbout lets you declare areas of expertise, and worksFor connects the person to your Organization entity. Include only verifiable facts; inflated credentials are both a trust and a policy risk, a point the validation guide reinforces.
Linking Person to Organization
Use worksFor on the Person and reference your Organization entity, so Google understands the author is affiliated with the publisher — completing the entity graph rather than leaving a floating person.
A connected graph (Person worksFor Organization; Article author Person; Article publisher Organization) is far stronger than three unrelated blocks. Where your platform already emits Organization, reference it by its @id rather than redefining it, to avoid the duplicate-entity problem. This mirrors the author-identity approach the site uses, where the byline links a named author to the brand publisher.
Person Schema and E-E-A-T
Person schema does not create expertise, but it makes existing expertise legible — connecting an author’s credentials, body of work, and off-site reputation into a coherent entity Google and AI can evaluate.
It works best alongside real author pages, consistent bylines, and genuine off-site presence; markup on a thin or anonymous author adds little. For the strategy of building author authority that this markup then expresses, see the Content Strategy pillar and the entity work in GEO & AEO.
Example Markup
A compact Person block in JSON-LD (shown as code):
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Person",
"name": "Jane Doe",
"url": "https://example.com/about/",
"jobTitle": "SEO Manager",
"worksFor": { "@type": "Organization", "name": "Example Co" },
"knowsAbout": ["SEO", "AI search"],
"sameAs": ["https://www.linkedin.com/in/janedoe"]
}
</script>
Many SEO plugins can generate author Person schema from user profiles — prefer that to hand-coding, and see JSON-LD vs Microdata for the format rationale.
- Person schema makes an author or individual a machine-readable entity for attribution and E-E-A-T.
- Essentials: name, url. High-value: jobTitle, worksFor, sameAs, knowsAbout, image, description.
- Link Person to your Organization via worksFor, referencing the existing entity by @id to avoid duplicates.
- It expresses expertise, it does not manufacture it — pair with real author pages and off-site presence.
- Only include verifiable credentials; inflated claims are a trust and policy risk.
Frequently Asked Questions
Does Person schema help rankings?
Not as a direct ranking factor, but it strengthens authorship and E-E-A-T signals by making an author a clear entity Google can evaluate. Its value grows when the person has genuine, verifiable expertise and off-site presence to connect to.
Should every author have Person schema?
Ideally yes for real, bylined authors with a profile page — it ties their work together. It adds little for anonymous or one-off contributors, and marking up a person with no verifiable background provides no benefit.
What is the difference between author and Person?
“author” is a property (of Article) whose value can be a Person entity. So you use Person schema to describe the individual, then reference that Person as the article’s author — the two work together rather than competing.
Can my SEO plugin generate Person schema?
Many can, from WordPress user profiles or author settings — populate the profile fields and let the plugin emit it. That keeps a single copy and links it correctly to your Organization, avoiding hand-coded duplicates.
The Bottom Line
Person schema turns a byline into an entity — connecting an author to their work, their employer, and their reputation in a form machines trust. Use it for real authors, wire it to your Organization, and keep it honest, and it reinforces the credibility signals that the rest of the schema cluster and the wider site depend on.
Further reading & sources
- Person — Schema.org
- Article structured data (author) — Google Search Central
See how your site actually shows up in AI search. An AI visibility audit maps where you’re cited, where you’re invisible, and what to fix first — in plain English.
Get your AI visibility auditTry the free SEO tools →
Prefer self-serve? The interactive checklists turn guides like this one into a working to-do list.
Keep reading in Schema Markup
Get one email when something genuinely changes
AI search moves fast and most of it is noise. We send one short email when a real shift is worth your time. Unsubscribe anytime.
Published by Plain Intelligence — practical AI SEO, GEO, and technical SEO, documented in plain English. About Plain Intelligence →
↑ Back to Schema Markup · Explore all articles · Free tools & resources · Glossary