BYTETOOLS

ProfilePage Schema Generator

Build ProfilePage JSON-LD for a creator, author or forum profile, with a Person or Organization mainEntity, sameAs links and follower and post counts.

Profile page
Person (mainEntity)
Interaction counts (optional)

ProfilePage JSON-LD

ProfilePage markup describes a page dedicated to one person or organisation — a creator profile, an author page or a forum member page. Only mark up counts that are genuinely visible to a visitor on that page; inflated or invisible statistics are a structured data policy violation.

What is the ProfilePage Schema Generator?

The ProfilePage Schema Generator builds the structured data that describes a page dedicated to one person or one organisation — a creator profile, an author bio page, a forum member page or a company profile.

  • Person or Organization mainEntity with one switch
  • Handle written as alternateName, account ID as identifier
  • Followers on interactionStatistic, posts on agentInteractionStatistic
  • sameAs list built from one URL per line
  • Blank fields are left out entirely, never emitted as empty strings
  • Copy as a script tag or download the raw JSON

How to use the ProfilePage Schema Generator

  1. 1

    Enter the profile page URL and choose whether the profile belongs to a Person or an Organization.

  2. 2

    Add the display name, handle, bio and avatar URL for the account.

  3. 3

    Paste any other profiles for the same person or brand into the sameAs box, one URL per line.

  4. 4

    Fill in follower, following and post counts if those numbers appear on the page.

  5. 5

    Copy the script block, or tick the raw JSON option and download the .json file.

About the ProfilePage Schema Generator

The ProfilePage Schema Generator builds the structured data that describes a page dedicated to one person or one organisation — a creator profile, an author bio page, a forum member page or a company profile. You fill in the fields and the JSON-LD appears immediately, ready to paste into the page's head.

It wraps a Person or Organization node as the page's mainEntity, carries the handle as alternateName, the account ID as identifier, and links out to the same account elsewhere with sameAs. Follower counts go on interactionStatistic, while posts written and accounts followed go on agentInteractionStatistic, each as an InteractionCounter.

Everything is generated locally in your browser — nothing you type is uploaded, logged or sent anywhere. Only mark up counts a visitor can actually see on the page; inflated or hidden statistics breach search engine structured data policies.

Frequently asked questions

What is ProfilePage schema used for?

ProfilePage marks a page as being about one specific person or organisation rather than a general article. Search engines use it to attribute creator profiles, forum member pages and author bios to the right entity, and to show the handle, avatar and follower counts alongside discussion and profile results.

What is the difference between interactionStatistic and agentInteractionStatistic?

interactionStatistic counts interactions with the profile itself, so a FollowAction counter there means followers. agentInteractionStatistic counts actions the profile performed, so a WriteAction counter is posts written and a FollowAction counter is accounts the profile follows. This generator writes each one to the correct property.

Do I need ProfilePage schema if I already have Person schema?

They do different jobs. Person describes the individual, while ProfilePage tells search engines that this particular URL is that person's profile page. Nesting the Person as the mainEntity of a ProfilePage, which this generator does, gives you both at once.

Can I use ProfilePage for a company account?

Yes. Switch the profile subject to Organization and the mainEntity becomes an Organization node with the same name, handle, description, image and sameAs properties. Use it for brand profiles, publisher pages and company member listings.

Should I include follower counts I cannot verify?

No. Structured data has to match what a visitor sees on the page, so only mark up counts that are genuinely displayed. Inflated or invisible numbers are a policy violation and can cost you rich results across the whole site.

Related tools