EntitySEO.wikiThe Entity SEO Reference

Person schema

From EntitySEO.wiki, the entity SEO reference · Published · Updated · By · Published by Local Blitz · How we research

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?

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?

PropertyUse
name, alternateNameThe name used in bylines
jobTitle, worksForRole and organization (by @id)
imageA real photo
sameAsOfficial profiles: LinkedIn, ORCID, Wikidata[3]
knowsAboutTopics the person is knowledgeable about[4]
alumniOf, hasCredentialEducation 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]

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.

References

Pages accessed September 29, 2026 unless a date is given. See all sources and our editorial policy.

  1. ^ "Article structured data". Google Search Central.
  2. ^ "ProfilePage structured data". Google Search Central.
  3. ^ "ORCID". ORCID.
  4. ^ "knowsAbout property". Schema.org.
  5. ^ "Person type". Schema.org.
  6. ^ "Creating helpful, reliable, people-first content". Google Search Central.