Person schema
Person schema describes an individual in JSON-LD: name, job title, employer, image, profiles (sameAs), expertise (knowsAbout) and credentials. It is most useful on an author or founder profile page marked up as a ProfilePage, and when articles link their author to that profile with author.url, as Google’s Article documentation recommends.
When should you use Person markup?
- Author bylines on articles, as the
authorof an Article.[1] - Profile pages for authors, founders and experts, as the
mainEntityof a ProfilePage.[2] - Founders and staff linked from Organization markup.
What does Google recommend for authors?
Google’s Article guidance says to include all authors shown on the page, use the Person type for people (not Thing or Organization), put only the name in author.name, and use author.url to link to a page that uniquely identifies the author, such as a bio page.[1] Officially documented
Which properties matter?
| Property | Use |
|---|---|
name, alternateName | The name used in bylines |
jobTitle, worksFor | Role and organization (by @id) |
image | A real photo |
sameAs | Official profiles: LinkedIn, ORCID, Wikidata[3] |
knowsAbout | Topics the person is knowledgeable about[4] |
alumniOf, hasCredential | Education and qualifications[5] |
What does an example look like?
{
"@context": "https://schema.org",
"@type": "ProfilePage",
"mainEntity": {
"@type": "Person",
"@id": "https://www.example.com/about/jane-doe#person",
"name": "Jane Doe",
"jobTitle": "Co-founder",
"worksFor": {"@id": "https://www.example.com/#organization"},
"knowsAbout": ["Local SEO", "Structured data"],
"sameAs": ["https://www.linkedin.com/in/janedoe-example"]
}
}
How does this support E-E-A-T?
Google’s helpful content guidance asks whether it is clear who created content, for example through bylines linking to author information.[6] Markup does not create expertise, but it connects real credentials to the content. See E-E-A-T and author entities.
Author markup rules from Google’s Article documentation
Google’s Article documentation has a dedicated list of author markup practices.[1]
- Include every author shown on the page, each as its own entry in the
authorarray. Do not merge several people into one name field. - Use
@typeplusurl(orsameAs), with valid URLs. For a person, link to a page about them; for an organization author, link to its home page. author.urlshould be “a link to a web page that uniquely identifies the author”, such as a social media page, an “about me” page or a bio page. If it is an internal profile page, Google recommends marking that author up with ProfilePage.- Put only the name in
author.name: not the publisher, a job title (usejobTitle), an honorific (usehonorificPrefixorhonorificSuffix) or introductory words like “posted by”.
Schema.org’s Person type has the properties these pages use, including jobTitle, worksFor, alumniOf, hasCredential and knowsAbout.[5]
ProfilePage requirements
Google’s ProfilePage guidance says the primary focus of the page “must be a single person or organization that is affiliated with the overall website”.[2] Its valid examples are a user profile on a forum or social site, an author page on a news site, an “About Me” page on a blog and an employee page on a company website. Its invalid examples are a store’s main home page (it contains too much non-profile information) and an organization review site (the organization is not associated with the website).[2]
The only required property is mainEntity, a Person or Organization; use the correct type if known, otherwise Google says to default to Person. dateCreated and dateModified are recommended.[2] The guide’s layout for a profile that lists recent work is a ProfilePage whose mainEntity is the Person (identified with an @id), with hasPart Articles whose author points back to that @id.[2] This site’s author page is a ProfilePage on the same pattern (view source to compare).
Frequently asked questions
Should every article have Person author markup?
If a person wrote it, yes: name the author in visible text and markup, and link to their profile page.
Can I use Organization as the author?
Yes, when an organization is the author. Google asks you to use the correct type: Person for people, Organization for organizations.
See also
References
Pages accessed September 29, 2026 unless a date is given. See all sources and our editorial policy.
- ^ "Article structured data". Google Search Central.
- ^ "ProfilePage structured data". Google Search Central.
- ^ "ORCID". ORCID.
- ^ "knowsAbout property". Schema.org.
- ^ "Person type". Schema.org.
- ^ "Creating helpful, reliable, people-first content". Google Search Central.