Skip to content

Person Schema Generator - JSON-LD for Knowledge Panel

Import existing JSON-LD

Paste JSON-LD or a full <script> tag. Matching fields fill the form; properties the form doesn't cover are kept in the output as they are.

Personal Information

Contact

Social Profiles

Google Search Preview
Person Name
All Google requirements met

JSON-LD Output

What is Person schema?

Person schema is structured data that describes a real individual: their name, photo, job title, employer, and the profiles that belong to them. You add it to a page as a JSON-LD block using the schema.org Person type. Search engines use it to tie a name on your site to one specific person instead of everyone else who shares it.

Person markup rarely stands alone. It is most useful nested inside other types, such as the author of an Article, the mainEntity of a ProfilePage, or the founder of an Organization. The generator above builds a standalone block you can use on an about page or paste into those larger objects.

Person schema example (JSON-LD)

A complete example you can adapt. Paste it into the page's HTML, or build your own with the generator above.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Priya Raman",
  "image": "https://priyaraman.dev/images/priya-raman.jpg",
  "url": "https://priyaraman.dev/",
  "jobTitle": "Principal Data Engineer",
  "worksFor": {
    "@type": "Organization",
    "name": "Northwind Analytics",
    "url": "https://northwind-analytics.com/"
  },
  "alumniOf": {
    "@type": "CollegeOrUniversity",
    "name": "University of Toronto"
  },
  "sameAs": [
    "https://www.linkedin.com/in/priyaraman",
    "https://github.com/priyaraman",
    "https://mastodon.social/@priyaraman"
  ]
}
</script>

Which Google rich result does it enable?

None on its own. Google has no Person rich result, so a standalone Person block will not change how a page looks in search. What it does is feed Google's understanding of who someone is. That understanding shows up in author details on articles, in Knowledge Panels, and in profile results for forum and social sites.

If you run a site with user or staff profile pages, wrap the Person in ProfilePage markup, which Google does document and support. For bylines, nest Person as the author of your Article schema and include a url pointing to the author's bio page.

Required and recommended properties

Property Status Notes
name Required The person's full name as it appears on the page. Google has no Person-specific docs, but every feature that consumes Person (author, ProfilePage) needs a name.
url Recommended A page that uniquely identifies the person, such as their bio or personal site. Google's article guidance asks for this on authors.
image Recommended A crawlable photo URL. Use the same headshot you use elsewhere.
jobTitle Recommended Their current role, in plain words.
worksFor Recommended An Organization object with at least a name.
sameAs Recommended URLs of profiles the person controls: LinkedIn, GitHub, Wikipedia, Wikidata, and so on.

Common Person schema mistakes

  • Expecting stars or a special snippet. Person markup has no visual rich result in Google; judge it by whether author and entity details are correct, not by how the result looks.
  • Putting Person markup about someone else on your page, for example a celebrity you wrote about. Mark up people the page is actually about or who wrote it.
  • Using a different spelling of the name than the byline and social profiles. Priya Raman on the page and P. Raman in the markup makes matching harder.
  • Listing dead or unrelated profiles in sameAs. Every URL should be an active account that clearly belongs to this person.
  • Writing worksFor as a bare string. The generator wraps it in an Organization object, which is what schema.org expects.
  • Adding email or telephone you would not want scraped. Anything in JSON-LD is as public as the page itself.

Where to put Person markup

Add a standalone Person block to your own homepage or about page. On articles, nest it inside the Article as the author rather than adding a second top-level block. On a team page, each staff member can have their own Person object, ideally linked to a dedicated bio page through url. Keep one canonical bio page per person and point every byline at it.

Related Tools

Frequently Asked Questions

Which fields does Google need for Person schema?
Google has no Person rich result, so there is no official required list. Start with name, then add url, image, jobTitle, worksFor and sameAs so the person can be matched to their other profiles.
Will Person schema get me a Knowledge Panel?
Not on its own. Knowledge Panels come from what Google finds about a person across the web, such as Wikipedia, news coverage and consistent profiles. Person markup on your own site confirms details Google may already have.
Person or ProfilePage?
Use ProfilePage for a page whose main subject is one person, such as an author bio page or a forum member page, with the Person inside mainEntity. Use plain Person when the person is part of something else, like the author of an article or the founder of an organisation.
Should I include email and phone?
Only if they are already on the page and you are happy for them to be scraped. Neither helps search results, and JSON-LD is as public as the page.
Can I add Person schema for someone else?
Mark up the people the page is about or who wrote it: yourself, staff, authors. Don't add Person markup for a celebrity you mention in an article.