Person Schema Generator

Build Person JSON-LD for an author or a profile. Google has no Person rich result of its own. It does ask for a name and an identifying URL when a person writes an article.

Google has no standalone Person rich result. It uses Person for article authors and asks for a name plus a URL that identifies that person.

JSON-LD

Rich Results Test ↗

Google does not list required properties for this type. Recommended fields still make the markup easier to understand.

Recommended fields still open

  • Add the person's name. Google has no Person rich result, and a Person without a name does not identify anyone.
  • Add a URL that identifies this person, such as a bio or profile page.
  • Add a photo URL.
  • Add a job title if the page shows one. Keep it out of the name field.
  • Add profile URLs (sameAs) for the same person on other sites.
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person"
}
</script>

Paste the script into the page HTML, in the head or before </body>. Then open Google's Rich Results Test, choose the code tab, and paste it again.

Person on schema.org · Google's documentation

Want the marketing handled too?

SEOchat publishes pages about your business, keeps your Google listing active, and reports results every week. Starter is $99/month. Growth is $179/month. Cancel anytime.

A business name and website you already typed are carried into checkout. They do not change the price.

A person, identified

schema.org Person describes a person. The properties that matter are the name, a URL that is clearly theirs, a photo, a job title, and links to the same person elsewhere. Google's author best practices, on the Article documentation, say to use the Person type for a person and Organization for an organization, and to give each author a separate object.

This generator does not wrap the person in ProfilePage. Google's profile-page feature has its own rules, and inventing that wrapper without those fields would be less accurate than a plain Person.

How to add this markup

  1. Use the page that is about this person.
  2. Enter the name as it appears, then the job title in its own field.
  3. Add the profile URL and any sameAs links that are the same person, not a company page unless they are the company.
  4. There is no Google required list. Fill the recommended lines that the page actually shows.
  5. Copy the script into that profile page and test it in Google's Rich Results Test.

If the person wrote an article, connect them from the article schema generator. Their employer can have organization markup. A brand they own can use the brand schema generator.

Questions

Does Person schema create a knowledge panel?

No. There is no Person rich result in Google's structured data gallery that this markup unlocks. Knowledge panels for people come from many sources. The markup still gives machines a clean name, job title, and profile URL.

What should the name field contain?

Only the name. Google's author guidance says to leave out the job title, honorifics, and words like “posted by.” Put the job title in jobTitle.

Why does the form ask for a URL?

Google recommends a URL that identifies the author: a bio page, an about page, or a profile. sameAs can point at other sites that are clearly the same person. A name with no URL is much easier to confuse with someone else.

Is this the author block on an article?

It can be. The article generator writes one author inside the article. Use this page when the subject of the URL is the person, such as a staff profile. Do not put a full biography only in the article markup if the bio page is a different URL.

What about email and phone?

Add them only if the page shows them and you want them public. They are not required, and they will be in the HTML source of any page that includes the script.

More free tools

See all tools