formatdesk

Person Schema Generator

Fields

The name as shown on the page.
Another commonly used name or acronym.
A short description that matches the visible text.
Absolute, crawlable image URLs. Google recommends 16:9, 4:3 and 1:1 versions of at least 50,000 pixels.
The canonical URL of the page.
Include the country code, e.g. +1-212-555-0100.
Only if it is public on the page.

Work and education

Works for
The name as shown on the page.
The canonical URL of the page.
Topics the person is known for.

Profiles (sameAs)

Official profiles that identify the same entity: Wikipedia, Wikidata, LinkedIn, GitHub, social networks.

Location

Location
Two-letter ISO 3166-1 code, e.g. US, DE.

Profile page

For a page about this person (author or creator profile): Google profile page rich result.

JSON-LD

Checking… ·

Files never leave your browserHow?

Person markup for authors, experts and creators

This person schema generator creates Person JSON-LD for an author bio, an about page or a creator profile. Add names, job, employer and profile links, wrap it in ProfilePage if the page is about this person, and copy the block.

Last updated:

How it works

  1. Who the person is

    Full name, username, job title, photo, a short description and the personal page.

  2. Connections

    Employer, education, topics of expertise and profiles on other sites – one per line.

  3. Profile page or not

    On a dedicated profile page tick ProfilePage to add creation and modification dates around the Person; then copy the block.

Features

  • ProfilePage for author pages

    Wraps the Person in the ProfilePage type that Google documents for profile pages of people and organizations, with dateCreated and dateModified.

  • sameAs that identifies

    LinkedIn, GitHub, Mastodon, Wikipedia or Wikidata URLs connect the person with the same entity elsewhere.

  • Expertise and education

    knowsAbout lists topics, alumniOf writes each school or university as an EducationalOrganization.

  • Reuse as article author

    The same Person JSON can be referenced from Article markup; the import accepts both bare Person and ProfilePage blocks.

Limits & privacy

Imported JSON-LD or HTML can be up to 1 MB. One employer and one location are supported in the form; add more in the JSON if needed.

Person markup says who someone is; it does not prove expertise. Google evaluates authors from the content and the wider web, so keep the profile consistent with what other sites say.

Validation uses the schema.org vocabulary (© schema.org sponsors, CC BY-SA 3.0, see licenses). Personal details stay in your browser – see the privacy page.

FAQ

Does Google show a rich result for Person markup?

Not for Person alone. Google uses ProfilePage markup on profile pages, and Person inside Article markup to understand authors.

What does ProfilePage require?

A mainEntity that is a Person or Organization with a name. dateCreated, dateModified, description, image and sameAs are recommended.

Should I add my birth date or phone number?

Only details that are public on the page. Structured data repeats the page; it should not publish anything new.

Can I use it for a fictional character or a pen name?

Use the name readers know, and alternateName for usernames. The markup must describe what the page shows.

Where should author markup go?

On the author page itself, and as the author of each article, ideally with a url pointing to that author page.

Related tools