Person schema identifies a named individual: an author, a founder, a team member. Attached to your content, it turns an anonymous byline into a real, checkable entity a model can weigh as a genuine authority signal instead of ignoring.
Person schema gives a named author a job title, a bio link, and sameAs links to their verified profiles, turning a plain text byline into a checkable entity. Use it for content credited to a specific individual, and reference it from Article schema’s author field, use Organization schema instead when content belongs to the business as a whole rather than one person.
- Reference a Person block from Article schema’s author field rather than repeating that person’s full details on every piece of content they are credited on.
- A customer testimonial belongs in a Review block, not Person schema, since Person implies an individual associated with your organization, not a third party leaving feedback.
- Person schema does not unlock its own rich result the way Product or Review does, it is an authority signal that supports Article and Organization schema instead.
What Person Schema Actually Does
A byline that just states a name in plain text gives a model nothing to verify. Person schema gives that name a job title, a link to a bio page, and sameAs links to the person’s own verified profiles, the same consistency check covered in our entity SEO guide. AI models weigh author authority more heavily on content where expertise genuinely matters, so this signal counts for more on some pages than others. This mirrors what Google’s own Article documentation asks for: author markup that connects a byline to a real, identifiable person, not just a text string.
The Code: A Working Example
{
"@context": "https://schema.org",
"@type": "Person",
"name": "Jamie Chen",
"jobTitle": "Head Baker",
"url": "https://riversidebakery.example/about/jamie-chen",
"worksFor": {
"@type": "Organization",
"name": "Riverside Bakery"
},
"sameAs": [
"https://www.linkedin.com/in/jamiechen"
]
}Person vs Organization: When to Use Each
Use Person schema for content written by, or representing, a specific named individual: a blog post byline, a founder’s bio, an expert quote. Use Organization schema when the content or the offering belongs to the business as a whole rather than one person. Article schema’s author field is where the two usually meet, referencing a Person object instead of a plain string name.
Where to Add It on Your Site
Add a Person block for every named author or team member you credit publicly, ideally on that person’s own bio page, then reference it from the author field of any Article schema they are credited on rather than repeating their details in full each time.
How to Validate It
Run any page featuring the Person block through Schema.org’s Validator to confirm the required name field and any nested Organization reference parse cleanly. Google’s Rich Results Test matters less here specifically, since Person schema on its own does not power a standalone rich result the way Product or Review does. Getting an author’s identity this clear is exactly the kind of groundwork a brand’s AI-search visibility depends on.
FAQ
Do I need Person schema for every blog post?
Only if the post is credited to a specific named author. If content is published under the business name with no individual byline, Organization schema alone is enough.
Should I use Person schema for customer testimonials?
No. A customer quoted in a testimonial is better represented inside a Review block, since Person schema implies an identified individual associated with your content or organization, not a third party leaving feedback.
Does Person schema help SEO directly?
Not on its own the way Product or FAQ schema does. It is an authority and trust signal that supports Article and Organization schema rather than something that unlocks its own rich result.
Related Reading
Go deeper on entity and authority schema:
Want to Be the Brand AI Recommends?
Book a call and we’ll map what it takes to get there for your business.