Person Schema Markup
Person markup identifies individuals and their attributes. It's essential for author pages, team directories, and personal websites — and increasingly important for Google's E-E-A-T assessment of content authority.
Google Search Features
- Profile page Person appears inside this feature's markup. Details about the person or organization a profile page is about.
When to Use Person
Properties
| Property | Type | Status | Description |
|---|---|---|---|
| name | Text | required | The person's full name. |
| url | URL | recommended | Personal website or profile URL. |
| image | URL | recommended | Photo of the person. |
| jobTitle | Text | recommended | Current job title or role. |
| worksFor | Organization | optional | Employer organization. |
| sameAs | URL (array) | recommended | Links to social profiles. |
| alumniOf | EducationalOrganization | optional | School(s) attended. |
| knowsAbout | Text or Thing | optional | Areas of expertise. |
| Text | optional | Contact email. | |
| givenName | Text | optional | First name. |
| familyName | Text | optional | Last name. |
JSON-LD Examples
Author Profile
A blog author with expertise and social links.
{
"@context": "https://schema.org",
"@type": "Person",
"name": "Dr. Emily Chen",
"url": "https://emilychen.dev",
"image": "https://emilychen.dev/photo.jpg",
"jobTitle": "Staff Software Engineer",
"worksFor": {
"@type": "Organization",
"name": "Google"
},
"knowsAbout": [
"Machine Learning",
"Natural Language Processing",
"Python"
],
"sameAs": [
"https://twitter.com/emilychen",
"https://github.com/emilychen",
"https://linkedin.com/in/emilychen"
]
}Common Mistakes
Not linking the Person to their authored articles — use the same Person identifier in Article.author.
Omitting sameAs links to social profiles — these help Google establish identity.
Complete Guide to Person Schema Markup
Person markup describes a real individual: an author, an expert quoted on a site, a team member, the owner of a personal site. Google reads it in two places. As the author of an Article, a Person with a name and a url or sameAs link helps Google understand who wrote the content. As the mainEntity of a ProfilePage, it's the subject of Google's profile page feature, which Google designed for sites where creators share first-hand perspectives: an author page on a news site, an "About Me" page on a blog, an employee page on a company website.
The most useful single page for a person is their profile page on your site. Give it ProfilePage markup with the Person as mainEntity: name, image, jobTitle, worksFor, a description, and sameAs links to their profiles elsewhere, such as LinkedIn or a Wikipedia article. Then give that Person an @id, such as https://example.com/authors/jane-smith/#person, and use the same @id as the author of every article they wrote.
That consistency is what the markup is for. Three spellings of one author's name across three articles, or an author object with no url, give search engines several people where there is one. Google's article documentation asks for each author in a separate author entry, never several names in one string, and for a url or sameAs that identifies the person.
Person markup must describe what the page shows. Credentials, awards or job titles in the JSON-LD that the page doesn't state don't make an author more credible; they make the markup inaccurate. E-E-A-T, Google's shorthand for experience, expertise, authoritativeness and trust, is something its quality raters judge from the content and the site, not a property you can set.
For the people's organization, use worksFor with the Organization's @id, and alumniOf for the schools they attended, so the entities link up across your markup.
Related Types
Ready to Create Person Markup?
Use our free generator to create valid Person JSON-LD markup with a visual form. No coding required.
Open Generator