S SCHEMA.BIZ
Person & Organization Extends: WebPage

Profile Page Schema (ProfilePage)

Profile page schema marks up a page about one person or organization who creates content on the site: a member's profile on a forum or social site, an author page on a news site, a blog's About Me page, an employee page. The page is a ProfilePage, and its mainEntity is the Person or Organization, with a name, a handle, a picture and counts such as followers and posts.

Last updated:

Does Google show Profile Page schema?

Yes Google reads ProfilePage markup for this feature: Profile page.

  • Profile page Active

    Details about the person or organization a profile page is about.

    Last change in Google's documentation: August 23, 2024. Google updated how profile page markup is used (Perspectives became Forums).

Last checked against Google's documentation: .

When to Use ProfilePage

Member profiles on forums and social sites Author pages on news and magazine sites About Me pages on personal blogs Employee and contributor pages

What Google requires

schema.org defines 139 properties a ProfilePage can use, counting the ones it inherits. Google reads only a few of them for each feature; the rest are valid schema.org that Google doesn't require.

Profile page: 1 required, 2 recommended Google's documentation

Property Google schema.org expects
mainEntity required Thing
dateCreated recommended Date, DateTime
dateModified recommended Date, DateTime

ProfilePage properties

The properties that matter most in practice, of the 139 schema.org defines for ProfilePage. Status is our advice for a complete description; Google's own requirements are in the table above.

Property Type Status Description
mainEntity Person or Organization required The person or organization the profile is about, with a name or alternateName.
dateCreated DateTime recommended When the profile was created, usually the account's sign-up date, in ISO 8601.
dateModified DateTime recommended When the profile was last edited, ideally by a person, not by a counter changing.
url URL optional The profile's canonical address, the one author links on posts point to.
name Text optional The page's title, such as "Priya Raman's profile". The person's name goes on mainEntity.
description Text optional A summary of the page. The person's own bio goes in mainEntity.description.
isPartOf WebSite optional The site the profile belongs to, usually by @id.
breadcrumb BreadcrumbList optional The trail to the profile, such as Members > Priya Raman.
inLanguage Text optional The page's language as a BCP 47 code: en, en-GB, de.
primaryImageOfPage ImageObject optional The page's main image, when it isn't simply the profile picture.
hasPart CreativeWork optional Posts or articles listed on the profile, when you mark them up there.

Note: Google reads these on the mainEntity (the Person or Organization), not on the ProfilePage: name, or alternateName when there's no name (required); alternateName, description, identifier, image, sameAs, interactionStatistic and agentInteractionStatistic (recommended).

JSON-LD Examples

Adapting an example? Paste your version into the schema markup validator to check its properties and what Google needs from it before you publish.

Minimal:A member profile with just a name

The least Google accepts: a ProfilePage whose mainEntity is a Person with a name. Enough to say whose page it is.

{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "mainEntity": {
    "@type": "Person",
    "name": "Priya Raman"
  }
}

Complete:A forum member's profile with handle, picture and counts

Everything Google's profile page documentation lists: the dates on the page; on the Person, the handle as alternateName, an internal identifier, a bio, a picture, links to other profiles, the followers and likes the member has received (interactionStatistic) and what the member has done (agentInteractionStatistic).

{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "url": "https://forum.example.com/members/priya-raman/",
  "dateCreated": "2019-03-14T18:22:05-07:00",
  "dateModified": "2026-09-30T08:15:40-07:00",
  "mainEntity": {
    "@type": "Person",
    "name": "Priya Raman",
    "alternateName": "priya_r",
    "identifier": "58213",
    "description": "Woodworker and furniture restorer in Portland. Moderator of the Hand Tools board.",
    "image": "https://forum.example.com/avatars/58213.jpg",
    "sameAs": [
      "https://www.youtube.com/@priyamakes.example",
      "https://priyaraman.example.org/"
    ],
    "interactionStatistic": [
      {
        "@type": "InteractionCounter",
        "interactionType": "https://schema.org/FollowAction",
        "userInteractionCount": 1204
      },
      {
        "@type": "InteractionCounter",
        "interactionType": "https://schema.org/LikeAction",
        "userInteractionCount": 8731
      }
    ],
    "agentInteractionStatistic": [
      {
        "@type": "InteractionCounter",
        "interactionType": "https://schema.org/WriteAction",
        "userInteractionCount": 2416
      },
      {
        "@type": "InteractionCounter",
        "interactionType": "https://schema.org/FollowAction",
        "userInteractionCount": 87
      }
    ]
  }
}

Real-world, nested:A news site's author page in an @graph

An author page on a news site: the ProfilePage is part of the WebSite, carries its breadcrumb, and its mainEntity is the reporter, who works for the publisher. The Person's @id is the one the site's articles use as author, so every byline points at this page.

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "ProfilePage",
      "@id": "https://news.example.com/authors/daniel-okoye/",
      "url": "https://news.example.com/authors/daniel-okoye/",
      "name": "Daniel Okoye, Transportation Reporter",
      "dateCreated": "2021-06-01T09:00:00-05:00",
      "dateModified": "2026-08-12T14:30:00-05:00",
      "inLanguage": "en-US",
      "isPartOf": {
        "@id": "https://news.example.com/#website"
      },
      "breadcrumb": {
        "@type": "BreadcrumbList",
        "itemListElement": [
          {
            "@type": "ListItem",
            "position": 1,
            "name": "Authors",
            "item": "https://news.example.com/authors/"
          },
          {
            "@type": "ListItem",
            "position": 2,
            "name": "Daniel Okoye"
          }
        ]
      },
      "mainEntity": {
        "@id": "https://news.example.com/authors/daniel-okoye/#person"
      }
    },
    {
      "@type": "Person",
      "@id": "https://news.example.com/authors/daniel-okoye/#person",
      "name": "Daniel Okoye",
      "jobTitle": "Transportation Reporter",
      "description": "Covers transit, roads and city planning in Chicago since 2021.",
      "url": "https://news.example.com/authors/daniel-okoye/",
      "image": {
        "@type": "ImageObject",
        "url": "https://news.example.com/images/authors/daniel-okoye.jpg",
        "width": 400,
        "height": 400
      },
      "sameAs": [
        "https://www.linkedin.com/in/danielokoye-example",
        "https://bsky.app/profile/dokoye.example.com"
      ],
      "worksFor": {
        "@id": "https://news.example.com/#organization"
      },
      "knowsAbout": [
        "Public transit",
        "Urban planning"
      ]
    },
    {
      "@type": "Organization",
      "@id": "https://news.example.com/#organization",
      "name": "Lakeshore Daily",
      "url": "https://news.example.com/",
      "logo": "https://news.example.com/images/logo.png",
      "sameAs": [
        "https://www.facebook.com/lakeshoredaily.example"
      ]
    },
    {
      "@type": "WebSite",
      "@id": "https://news.example.com/#website",
      "name": "Lakeshore Daily",
      "url": "https://news.example.com/",
      "publisher": {
        "@id": "https://news.example.com/#organization"
      }
    }
  ]
}

Common Profile Page schema mistakes

A mainEntity with a picture and link but no name or handle

REQ_MISSING: Google requires this property for the search feature. Without it the page isn't eligible for that rich result, although the markup is still valid schema.org.

Google accepts alternateName in place of name, which suits sites where members show only a handle.

Wrong

{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "mainEntity": {
    "@type": "Person",
    "image": "https://forum.example.com/avatars/58213.jpg",
    "url": "https://forum.example.com/members/priya-raman/"
  }
}

Right

{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "mainEntity": {
    "@type": "Person",
    "alternateName": "priya_r",
    "image": "https://forum.example.com/avatars/58213.jpg",
    "url": "https://forum.example.com/members/priya-raman/"
  }
}

Putting the member's post count on the page instead of the person

PROP_NOT_ON_TYPE: This schema.org property isn't defined for the object's type, so search engines may ignore it.

agentInteractionStatistic is a Person and Organization property. Google reads both statistics on the mainEntity.

Wrong

{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "agentInteractionStatistic": {
    "@type": "InteractionCounter",
    "interactionType": "https://schema.org/WriteAction",
    "userInteractionCount": 2416
  },
  "mainEntity": {
    "@type": "Person",
    "name": "Priya Raman"
  }
}

Right

{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "mainEntity": {
    "@type": "Person",
    "name": "Priya Raman",
    "agentInteractionStatistic": {
      "@type": "InteractionCounter",
      "interactionType": "https://schema.org/WriteAction",
      "userInteractionCount": 2416
    }
  }
}

Listing other profiles in sameAs without https://

VALUE_URL: This property expects an absolute URL, including https://. Relative paths can't be resolved reliably.

Wrong

{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "mainEntity": {
    "@type": "Person",
    "name": "Priya Raman",
    "sameAs": "youtube.com/@priyamakes.example"
  }
}

Right

{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "mainEntity": {
    "@type": "Person",
    "name": "Priya Raman",
    "sameAs": "https://www.youtube.com/@priyamakes.example"
  }
}

Follower counts without the InteractionCounter type

TYPE_MISSING_NESTED: Nested objects should say what they are too. Without an @type, search engines have to guess, and Google's features may not recognise the object.

The count itself must be a whole number too: 1204, not "1.2K".

Wrong

{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "mainEntity": {
    "@type": "Person",
    "name": "Priya Raman",
    "interactionStatistic": {
      "interactionType": "https://schema.org/FollowAction",
      "userInteractionCount": 1204
    }
  }
}

Right

{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "mainEntity": {
    "@type": "Person",
    "name": "Priya Raman",
    "interactionStatistic": {
      "@type": "InteractionCounter",
      "interactionType": "https://schema.org/FollowAction",
      "userInteractionCount": 1204
    }
  }
}

Copying "Member since March 2019" into dateCreated

VALUE_DATE: Dates and times must be ISO 8601: 2026-03-14 for a date, 09:00 for a time of day (24-hour), 2026-03-14T09:00:00-04:00 for a date and time. Other formats, and dates that don't exist, can't be read reliably.

Use the account's stored creation timestamp, not the text the template prints.

Wrong

{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "dateCreated": "March 2019",
  "mainEntity": {
    "@type": "Person",
    "name": "Priya Raman"
  }
}

Right

{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "dateCreated": "2019-03-14T18:22:05-07:00",
  "mainEntity": {
    "@type": "Person",
    "name": "Priya Raman"
  }
}

Also watch for

  • Using ProfilePage on a page that isn't mainly about one person or organization affiliated with the site, such as a store's home page or a review site's page about a company it has no link to. Google lists both as invalid.

  • Filling image with the default avatar for members who never uploaded one. Google says to leave image out rather than use a placeholder or icon.

  • Counting followers from other platforms in interactionStatistic. Google wants statistics from the site hosting the profile only; other platforms belong in sameAs.

  • Bumping dateModified every time a counter changes. Google prefers it to reflect edits a person made to the profile.

Which pages are profile pages

Google's rule is that the page's main focus must be a single person or organization affiliated with the site. Its own examples of valid pages are a member's 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 site. Its examples of invalid ones are a store's home page and a review site's page about an organization that isn't associated with the site.

The common thread is that the person or organization creates content on the site, and the page is where that content and its creator meet. A list of all authors is a CollectionPage, not a ProfilePage; a company's About page describing the business is an AboutPage with the Organization as its subject. A team page with twenty staff isn't a profile either; each staff member's own page can be.

The mainEntity can be an Organization: a brand's account on a community site, a publisher's page on an aggregator, a company that posts on a forum. The same properties apply, with the organization's name, logo or image, and its follower counts.

Followers, posts and likes: two statistics properties

Profile markup has two properties for counts, and they point in opposite directions. interactionStatistic counts what others did to the person: followers (FollowAction), likes they received (LikeAction), mutual connections (BefriendAction). agentInteractionStatistic counts what the person did: posts written (WriteAction), accounts followed (FollowAction), likes given (LikeAction), reshares (ShareAction). Each is an InteractionCounter with an interactionType and a whole-number userInteractionCount.

The same action can appear in both. A FollowAction in interactionStatistic is the follower count; in agentInteractionStatistic it's the following count. Mixing them up is easy in a template, so name the variables after the property they feed.

Only count activity on your own site. A member's YouTube subscribers or LinkedIn connections aren't statistics of your platform; link those profiles in sameAs instead. If a count isn't shown on the page, or the site has no followers feature, leave the counter out rather than sending zero.

Handles, IDs and links between profiles and posts

Use name for the name the person shows and alternateName for the handle, such as "priya_r". On sites where members only have handles, the handle alone in alternateName meets Google's requirement. identifier is your own internal ID for the account (a user number from your database), which stays the same when a member changes their handle.

Give the Person an @id built from the profile URL, such as https://forum.example.com/members/priya-raman/#person, and use it everywhere that person appears. On a forum, each DiscussionForumPosting and Comment has an author with the member's name and a url pointing to this profile page; Google's forum documentation recommends author.url for exactly that link. On a news site, every NewsArticle's author refers to the reporter's @id. The profile page then holds the full description once, and posts and articles carry a short reference.

Keep sameAs to profiles the person controls or that are about them: their own site, their accounts elsewhere. Let members add these themselves in their settings, and validate that each value is an absolute URL before it reaches the template.

Dates, deleted accounts and testing

dateCreated is when the profile came into being, usually the account's sign-up time; dateModified is when the profile was last edited. Both are ISO 8601 date-times with a time zone. Read them from the stored timestamps, not from the "Member since" text the page prints. If the profile has never been edited, leave out dateModified or set it to the creation time.

Profiles change state. When a member deletes their account, remove the profile's markup along with the page, or replace the page with a plain notice and no ProfilePage. For suspended or private profiles that are hidden from visitors, don't mark up anything visitors can't see. Paginated profiles that list a member's posts across several pages should carry the same ProfilePage and Person on each, with the same @id. Each profile page gets exactly one ProfilePage; if a site-wide template already outputs a generic WebPage, replace it on profile URLs rather than adding a second page object beside it.

To test a profile template, paste its output into the Validator at /markup/validator/, which checks the mainEntity's name or alternateName and the statistics' structure. Test both a complete profile and a sparse one (a new member with no picture and no posts), since that's where templates send empty values. Google's Rich Results Test reads the live page.

Complete Guide to Profile Page Schema

Google's profile page markup tells it who a profile page is about, together with the details a profile shows: the name and handle, the picture, the bio, and counts such as followers and posts. Google's documentation describes the markup for sites where creators, people or organizations, share first-hand perspectives. In August 2024, when its Perspectives feature was renamed Forums, Google clarified how profile page and discussion forum markup are used, which is why the two are usually implemented together on community sites.

The page type is a WebPage subtype, so a ProfilePage can carry everything a WebPage can: breadcrumb, isPartOf the WebSite, inLanguage. What Google reads, though, sits on the mainEntity. That split matters in templates: the page's name is the page title, the Person's name is the person's, and putting the bio, picture or counters on the page instead of the person is a frequent mistake.

A ProfilePage is different from an AboutPage. An AboutPage describes the site or the organization behind it; a ProfilePage describes one of the site's creators. A personal blog whose About Me page is about its single author fits ProfilePage, with that author as the Person; a company's About Us page describing the business is an AboutPage.

For a news or magazine site, author pages are the natural home of each journalist's Person markup: jobTitle, worksFor the publisher, sameAs links and a photo. Articles then refer to the author by @id, and Google's Article documentation recommends an author.url that leads to a page like this one.

Where ProfilePage sits in schema.org

"Web page type: Profile page."

Path from Thing: Thing CreativeWork WebPage ProfilePage

Parent type
WebPage
More specific types
None: ProfilePage has no subtypes in schema.org.

Related Types

Ready to Create ProfilePage Markup?

Use our free generator to create valid ProfilePage JSON-LD markup with a visual form. No coding required.

Open Generator