S SCHEMA.BIZ

Last updated:

Person Schema Generator

This person schema generator turns a name, a job title, an employer and a few profile links into Person JSON-LD as you type. Use it for an author page, a team member's profile or a personal site, then copy the script tag, or the Person object inside it, into your page.

Reference: Person schema

Person: Use on personal websites, author pages, or team member profiles to say who a person is and link their profiles elsewhere. No Google rich result uses Person on its own.

Basic Info
Professional
Social
Media

What Google shows for Person markup

Person markup has no rich result of its own; the validation panel says as much once the form is valid. Google reads a Person inside other markup instead. As the author of an article, the name and a url or sameAs link help Google tell one writer apart from another with the same name. As the mainEntity of a ProfilePage, on a forum or a site where people post their own perspectives, it helps Google show that content in its Discussions and Forums feature.

Valid Person markup on its own changes nothing you can see in a search result. Its value is in connecting a byline to a profile page and to the person's accounts elsewhere, and that only works if the details match what the page shows.

How to fill in each field

Name, website and email

Full Name is the name the byline shows, such as Maya Okafor. Google's author guidance keeps everything else out of it: no Dr., no PhD, no By, and no job title. First Name and Last Name are optional and only split the same name. Website should be a page about this person alone, such as their author page on your site or their own homepage, never a list of posts. Email is published to anyone who reads the code, so leave it empty unless the page already shows it.

Job title, employer and expertise

Job Title is the current role, such as Senior Food Editor. Employer and Employer Website become a worksFor Organization; Education becomes one alumniOf school. Expertise takes a comma-separated list, Baking, Fermentation, Food safety, and the generator writes each subject as its own knowsAbout entry. Fill these in only with what the profile or bio actually says.

Profile links

The Twitter/X, LinkedIn and GitHub fields go into one sameAs array. Paste the full address of the person's own profile, such as https://www.linkedin.com/in/maya-okafor, not a company page or a search result. To add more, such as a Wikipedia article or an ORCID record, append them to the sameAs array in the copied code.

Photo

Image URL is a headshot at a public address that search engines can fetch, the same photo the profile page uses. Use a photo the person agreed to publish, at its full size rather than a small thumbnail.

The form marks 1 field as required and 3 as recommended:

  • Full Name (required): The person's full name.
  • Website (recommended): The person's website or profile page.
  • Job Title (recommended): Current job title.
  • Image URL (recommended): A URL to an image representing this item. Google recommends images be at least 1200px wide.

Example: A staff writer's author page

This form filled in for an editor: name, profile URL, job title, employer, education, three subjects, two profile links and a photo.

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Maya Okafor",
  "givenName": "Maya",
  "familyName": "Okafor",
  "url": "https://www.example.com/authors/maya-okafor/",
  "image": "https://www.example.com/img/authors/maya-okafor.jpg",
  "jobTitle": "Senior Food Editor",
  "worksFor": {
    "@type": "Organization",
    "name": "Northfield Kitchen",
    "url": "https://www.example.com/"
  },
  "alumniOf": {
    "@type": "EducationalOrganization",
    "name": "Ashford Culinary Institute"
  },
  "knowsAbout": [
    "Baking",
    "Fermentation",
    "Food safety"
  ],
  "sameAs": [
    "https://www.linkedin.com/in/example-maya-okafor",
    "https://x.com/example_mokafor"
  ]
}

5 common mistakes

  1. Credentials in the name. Dr. Maya Okafor, RD in Full Name mixes three things. Keep the name plain and put the role in Job Title.
  2. A website that isn't about the person. The site's home page or a category of posts doesn't identify anyone. Link the page that's about this person only.
  3. Profiles that belong to someone else. A namesake's account, the employer's company page or a profile the person no longer uses sends the wrong signal. Link only accounts the person runs.
  4. A new description on every article. Describe the person fully once, on their profile page. In the copied code, add an @id such as the profile URL followed by #person, and point each article's author at that same ID.
  5. Expecting a rich result. Testing a lone Person in Google's tools shows no rich result, because there isn't one. Put the Person inside the article or profile page markup that Google does support.

How to test your Person markup

Open the code in the Schema Validator to check the types and properties: a relative URL, a property Person doesn't have or a typo in sameAs shows up there. Google's Rich Results Test only checks the results Google supports, and Person isn't one, so test the page's article or profile page markup with this Person inside it.

Frequently Asked Questions

How do I use this Person as an article's author?

Copy the object without its @context and paste it as the value of author in your article markup. If you only need the name and a profile link, the Article schema generator has its own Author Name and Author URL fields.

Can I make a profile page with it?

Yes, with one edit. Wrap the copied Person in a ProfilePage: {"@context": "https://schema.org", "@type": "ProfilePage", "mainEntity": { … }}, with the Person in place of the dots. The Schema Validator then checks it for Google's profile page requirements.

Why are there only three social fields?

They cover the profiles most people have. Every one of them ends up in the same sameAs array, so you can add any other profile URL to that array in the copied code.

Other schema generators