ProfilePage schema markup

Does Google still show a rich result for this?

Supported only through ProfilePage, not through a bare Person. There is no standalone Person rich result. It feeds the discussions and forums appearance rather than acting as a general way to show a biography in search.

When to use it

On an author page, a forum or social user profile, an about-me page or an employee page. Not on a home page.

Required properties

• mainEntity
• mainEntity.name

Recommended properties

• dateCreated
• dateModified
• alternateName
• description
• identifier
• image
• interactionStatistic
• sameAs

Example

{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "dateCreated": "2026-01-12T09:00:00+00:00",
  "mainEntity": {
    "@type": "Person",
    "name": "Jane Smith",
    "description": "Writes about technical SEO.",
    "sameAs": ["https://www.linkedin.com/in/example"]
  }
}

Common mistakes

• Using bare Person markup and expecting a result. The supported wrapper is ProfilePage.
• Putting it on a home page, which Google lists as an invalid use.
• Expecting it to surface a biography in ordinary search results. That is not what it does.

Verified against Google’s structured data documentation and its changelog on 28/07/2026. Google changes what it supports without much notice — if you are reading this long afterwards, check the current documentation before acting on it. Background on why this markup matters beyond rich results is in the answer engine optimisation guide.