ProfilePage is a Schema.org WebPage subtype for pages that focus on a single person or organization. Google documented it in 2023 for sites where creators share first-hand perspectives, such as forums and social platforms, and it is also a natural fit for author bio pages on company blogs. The Person or Organization goes in mainEntity.
Markup outline
Google requires mainEntity, the Person or Organization, with a name. Recommended properties include alternateName for a handle, identifier, image, description, sameAs, agentInteractionStatistic for post counts, and interactionStatistic for followers. dateCreated and dateModified describe the profile page itself.
{
"@context": "https://schema.org",
"@type": "ProfilePage",
"mainEntity": {
"@type": "Person",
"@id": "https://www.cobbleridge.example/authors/sam-ortiz/#person",
"name": "Sam Ortiz",
"jobTitle": "Head of Data",
"image": "https://www.cobbleridge.example/img/sam.jpg",
"sameAs": ["https://www.linkedin.com/in/example-sam-ortiz"]
}
}Example
Building out author pages
Cobbleridge, a data observability SaaS, had bylines with no author pages. It creates a page per author with a real bio and links, adds ProfilePage markup, and updates the post template so author references point to each profile's Person @id.
Common mistakes
Profiles with no real content
A page with only a name and no bio describes very little. Give readers enough to judge who the author is.
Questions
Google's documentation focuses on creator platforms, but the type fits any page about one person or organization, including author bios.
