Skip to content

ProfilePage Schema Generator - JSON-LD for Profile Pages

Import existing JSON-LD

Paste JSON-LD or a full <script> tag. Matching fields fill the form; properties the form doesn't cover are kept in the output as they are.

Profile Owner

Emitted as an InteractionCounter (FollowAction).

Dates

Google Search Preview
Preview not available for this type.
All Google requirements met

JSON-LD Output

What is ProfilePage schema?

ProfilePage schema is structured data that marks a web page as a profile of one person or organisation, such as a forum member page or a creator's page on a social site. It wraps a Person or Organization in the mainEntity property. Google uses it to identify who creates content on sites with user-generated posts.

The only required piece is mainEntity with a name. You can add the handle as alternateName, an internal user ID as identifier, a photo, a bio, links to other accounts in sameAs, and counts for followers and posts. dateCreated and dateModified describe when the profile was created and last changed.

ProfilePage schema example (JSON-LD)

A complete example you can adapt. Paste it into the page's HTML, or build your own with the generator above.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "dateCreated": "2021-03-08T14:22:00Z",
  "dateModified": "2026-10-30T09:05:00Z",
  "mainEntity": {
    "@type": "Person",
    "name": "Marta Kowalski",
    "alternateName": "mkowalski",
    "identifier": "48213",
    "description": "Woodworker and furniture restorer. Posting shop builds since 2021.",
    "image": "https://forum.example.com/avatars/48213.jpg",
    "sameAs": [
      "https://www.youtube.com/@martabuilds",
      "https://www.instagram.com/martabuilds"
    ],
    "interactionStatistic": {
      "@type": "InteractionCounter",
      "interactionType": "https://schema.org/FollowAction",
      "userInteractionCount": 2140
    },
    "agentInteractionStatistic": {
      "@type": "InteractionCounter",
      "interactionType": "https://schema.org/WriteAction",
      "userInteractionCount": 386
    }
  }
}
</script>

Which Google rich result does it enable?

ProfilePage does not produce a rich result of its own. Google uses it to recognise creators and connect their posts to them, which supports features that highlight first-hand content, such as the Discussions and forums section and Perspectives.

It works best together with DiscussionForumPosting markup: posts name an author with a url, and that URL leads to a page with ProfilePage markup for the same person.

Required and recommended properties

Property Status Notes
mainEntity Required A Person or Organization that the page is about.
mainEntity.name Required The display name. alternateName can stand in if the site has no display name.
dateCreated Recommended When the profile was created, ISO 8601.
dateModified Recommended When the profile was last changed, ISO 8601.
mainEntity.alternateName Recommended The username or handle, for example mkowalski.
mainEntity.identifier Recommended A stable internal ID that does not change if the user renames their account.
mainEntity.description Recommended The user's bio or tagline.
mainEntity.image Recommended Profile photo or avatar URL.
mainEntity.sameAs Recommended Links to the same person's profiles on other sites.
mainEntity.interactionStatistic Recommended Counts of actions on the user, such as followers (FollowAction) or likes.
mainEntity.agentInteractionStatistic Recommended Counts of actions by the user, such as posts written (WriteAction).

Common ProfilePage schema mistakes

  • Using ProfilePage on an About Us, team, or contact page. Those are not profiles of a content creator.
  • Adding a Person directly as the page type instead of wrapping it in ProfilePage's mainEntity.
  • Using the username as identifier. If users can rename themselves, the ID should be the stable internal number.
  • Showing follower counts in the markup that differ from the counts on the page.
  • Listing sameAs links that the user has not added to their visible profile.

Profiles on sites with user content

ProfilePage matters most on forums, Q&A sites, and social platforms where many people post. It helps Google tell the difference between a long-standing member with hundreds of posts and a brand-new account. If you run a site like that, generate this markup for each member page and make every post's author link to it. For a standalone personal website, plain Person schema on the home page is usually enough.

Related Tools

Frequently Asked Questions

Should I use ProfilePage on my company's About page?
No. Google says ProfilePage is for pages that focus on a single person or organisation that creates content on the site, such as a forum member's page or an author page on a social platform. An About Us page or a staff page is better described with Organization markup.
What is the difference between ProfilePage and Person schema?
Person describes a human. ProfilePage describes a web page whose main subject is a person or organisation. On a profile page you use both: ProfilePage at the top, with a Person or Organization as its mainEntity.
Can an author page on a news site use ProfilePage?
Yes. A page that lists an author's articles and gives their bio is a profile page in Google's sense. Use ProfilePage with the author as a Person in mainEntity, and link the same Person from your Article markup with a url that points to this page.
How do I show follower and post counts?
Use interactionStatistic on the person or organisation. Each statistic is an InteractionCounter with an interactionType, such as FollowAction for followers, and a userInteractionCount. Use agentInteractionStatistic for things the user did, such as how many posts they wrote.
Does ProfilePage create a visible rich result?
Not a distinct one. Google uses the markup to understand who created content, which helps with features like Perspectives and Discussions and forums. Do not expect a special search snippet for the profile page itself.