Profile Page Schema Generator

Mark up author and creator profile pages with ProfilePage JSON-LD, naming the Person or Organization the page is about.

Runs in your browser — nothing you enter is uploaded Free · no sign-up

Validate a live page

    

Paste the code into the page’s <head> or <body>. Valid markup makes a page eligible; Google decides whether to show a rich result. Mark up only content visible on the page. Fields are saved in your browser.

About the Profile Page Schema Generator

ProfilePage markup tells Google that a page is mainly about one person or organization, such as an author bio on a news site, a member profile on a forum or a creator page on a community platform. Google documents it to help identify creators and their details in Search, especially for features that show forum and social content. The required property is mainEntity, a Person or Organization with a name; recommended ones include alternateName for a handle, identifier, image, description, sameAs and dateCreated.

This profile page schema generator builds the JSON-LD in your browser, so profile details stay on your device. Use it only on pages whose main purpose is the profile, not on a homepage or article. Keep the name and handle identical to what appears on the page, and link this profile from the author field of that creator's posts.

How to use it

  1. Choose whether the profile is for a Person or an Organization.
  2. Enter the name, handle, image and short description shown on the page.
  3. Add sameAs links and creation or update dates if available.
  4. Copy the JSON-LD to the profile page and test it.

Frequently asked questions

When should I use ProfilePage markup?

Use it on pages whose main focus is a single person or organization that creates content on your site, such as author pages, contributor bios or user profiles on forums and community platforms. Do not use it on homepages, product pages or articles where the profile is not the main topic.

What are the required properties for ProfilePage?

Google requires mainEntity, which must be a Person or Organization, and that entity needs a name. Recommended properties include alternateName for a username or handle, identifier, description, image, sameAs links and interaction statistics such as follower counts where you show them.

Does ProfilePage replace Person schema?

No, it wraps it. ProfilePage describes the page; the Person or Organization inside mainEntity describes who the page is about. Using both together gives search engines a clear statement that this URL is the profile of that specific creator. Keep the details identical in both.