> Person Schema JSON-LD -- Examples for Knowledge Panels and Author Markup

Copy validated Person schema JSON-LD with sameAs, jobTitle, image, and worksFor. The most-searched schema type on this site, used to claim Knowledge Panels.

published: Sep 27, 2015
modified: May 1, 2026
size: 5.9K
path: /person/

Last updated May 1, 2026 by Patrick Coombe

There are an infinite number of variations for the JSON-LD "Person" type so we did our best to include some of the more popular properties. Believe it or not the "person" type is the most searched for keyword and the most popular page on this website over the past 16 months. In the past, including the "person" schema type in JSON-LD format has yielded great success when trying to get a knowledge panel for a person.

Checkout a few of these examples and please always let us know if you spot any mistakes, have any suggestions, or have any code examples you would like to share with us.

2025 Update, this is an adaptation of my original with influence from other snippets and validated by Google Rich Results tester:

person.jsonld · 2.5K test

{
  "@context": "http://schema.org",
  "@type": "Person",
  "@id": "https://patrickcoombe.com/about-patrick",
  "name": "Patrick Coombe",
  "alternateName": "Patrick Coombe",
  "nationality": "United States",
  "birthPlace": {
    "@type": "Place",
    "address": {
      "@type": "PostalAddress",
      "addressLocality": "Boca Raton",
      "addressRegion": "FL",
      "addressCountry": "USA"
    }
  },
  "alumniOf": {
    "@type": "CollegeOrUniversity",
    "name": "McCann School of Business",
    "sameAs": "https://en.wikipedia.org/wiki/McCann_School_of_Business_%26_Technology"
  },
  "gender": "Male",
  "description": "Technologist",
  "disambiguatingDescription": "Co-founder of Elite Strategies",
  "jobTitle": "Technical Director",
  "worksFor": {
    "@type": "Organization",
    "name": "Elite Strategies",
    "sameAs": [
      "https://elite-strategies.com/",
      "https://x.com/elitestweets"
    ]
  },
  "url": "https://patrickcoombe.com",
  "image": "https://patrickcoombe.com/img/patrickCoombeProfile.jpg",
  "address": {
    "@type": "PostalAddress",
    "addressLocality": "Boca Raton",
    "addressRegion": "FL",
    "addressCountry": "USA"
  },
  "sameAs": [
    "https://github.com/patrickcoombe",
    "https://x.com/pmkoom",
    "https://www.facebook.com/patrickcoombe",
    "https://bsky.app/profile/patrickcoombe.com",
    "https://www.instagram.com/patrickcoombe/",
    "https://www.producthunt.com/@patrickcoombe",
    "https://wordpress.org/support/users/patrickfl/",
    "https://www.youtube.com/@PatrickCoombe",
    "https://www.amazon.com/stores/Patrick-Coombe/author/B014HX9RD6"
  ],
  "author": {
    "@type": "Book",
    "name": "Learn SEO: An On-Page SEO Tutorial",
    "url": "https://www.amazon.com/Learn-SEO-Page-Tutorial-ebook/dp/B014HGMBYK",
    "datePublished": "2015-08-25",
    "numberOfPages": 142,
    "inLanguage": "English",
    "bookFormat": [
      "http://schema.org/EBook",
      "http://schema.org/Paperback"
    ],
    "isbn": [
      "0692599142",
      "978-0692599143"
    ],
    "sameAs": [
      "https://www.amazon.com/Learn-SEO-Page-Tutorial-ebook/dp/B014HGMBYK",
      "https://www.amazon.com/Page-SEO-Tutorial-Patrick-Coombe/dp/0692599142",
      "https://www.goodreads.com/book/show/26202717-learn-seo"
    ],
    "author": {
      "@id": "https://patrickcoombe.com/about-patrick"
    },
    "aggregateRating": {
      "@type": "AggregateRating",
      "ratingValue": "4.75",
      "reviewCount": 12,
      "bestRating": "5",
      "worstRating": "1"
    }
  }
}

A very basic example

person.jsonld · 1.0K test

    {
      "@context": "https://schema.org",
      "@type": "Person",
      "address": {
        "@type": "PostalAddress",
        "addressLocality": "Colorado Springs",
        "addressRegion": "CO",
        "postalCode": "80840",
        "streetAddress": "100 Main Street"
      },
      "colleague": [
        "http://www.example.com/JohnColleague.html",
        "http://www.example.com/JameColleague.html"
      ],
      "email": "[email protected]",
      "image": "janedoe.jpg",
      "jobTitle": "Research Assistant",
      "name": "Jane Doe",
      "alumniOf": "Dartmouth",
      "birthPlace": "Philadelphia, PA",
      "birthDate": "1979-10-12",
      "height": "72 inches",
      "gender": "female",
      "memberOf": "Republican Party",
      "nationality": "Albanian",
      "telephone": "(123) 456-6789",
      "url": "http://www.example.com",
	    "sameAs" : [ "https://www.facebook.com/",
      "https://www.linkedin.com/",
      "http://twitter.com/",
      "http://instagram.com/",
      "https://plus.google.com/"]
    }

Here is another JSON-LD example I found courtesy of Jay Holtslander. You can check out his repo here which has some more awesome examples of JSON-LD types.

person.jsonld · 2.3K test

{
"@context": "http://www.schema.org",
"@type": "Person",
"@id": "https://jay.holtslander.ca/#person",
"name": "Jay Holtslander",
"alternateName": "Jason Holtslander",
"nationality": "Canadian",
"birthPlace" : {
	"@type": "Place",
    "address": {
  		"@type": "PostalAddress",
		"addressLocality": "Vancouver",
		"addressRegion": "BC",
        "addressCountry": "Canada"
	}
},
"affiliation": [
	{
		"@type": "Organization",
		"name": "Futurpreneur",
		"sameAs": [
			"https://twitter.com/futurpreneur",
			"https://www.facebook.com/futurpreneur/",
			"https://www.linkedin.com/company-beta/100369/",
			"https://www.youtube.com/user/CYBF"
		]
  	}
],
"alumniOf": [
	{
	 "@type": "CollegeOrUniversity",
	 "name": "Vancouver Film School",
	 "sameAs": "https://en.wikipedia.org/wiki/Vancouver_Film_School"
	},
	{
	 "@type": "CollegeOrUniversity",
	 "name": "CodeCore Bootcamp"
	}
],
"gender": "Male",
"Description": "Technologist",
"disambiguatingDescription": "Co-founder of CodeCore Bootcamp",
"jobTitle": "Technical Director",
"worksFor": [
	{
		"@type": "Organization",
		"name": "Skunkworks Creative Group Inc.",
		"sameAs": [
			"https://twitter.com/skunkworks_ca",
			"https://www.facebook.com/skunkworks.ca",
			"https://www.linkedin.com/company/skunkworks-creative-group-inc-",
			"https://plus.google.com/+SkunkworksCa"
		]
	}
],
"url": "https://jay.holtslander.ca",
"image": "https://s.gravatar.com/avatar/961997eb7fd5c22b3e12fb3c8ca14e11?s=512&r=g",
"address": {
	"@type": "PostalAddress",
	"addressLocality": "Vancouver",
	"addressRegion": "BC",
	"addressCountry": "Canada"
},
"sameAs": [
	"https://twitter.com/j_holtslander",
	"https://pinterest.com/j_holtslander",
	"https://instagram.com/j_holtslander",
	"https://www.facebook.com/jay.holtslander",
	"https://ca.linkedin.com/in/holtslander/en",
	"https://plus.google.com/+JayHoltslander",
	"https://www.youtube.com/user/jasonh1234",
	"https://github.com/JayHoltslander",
	"https://profiles.wordpress.org/jasonh1234",
	"https://angel.co/j_holtslander",
	"https://www.foursquare.com/user/184843",
	"https://jholtslander.yelp.ca",
	"https://codepen.io/j_holtslander/",
	"https://stackoverflow.com/users/751570/jay",
	"https://dribbble.com/j_holtslander",
	"http://jasonh1234.deviantart.com/",
	"https://www.behance.net/j_holtslander",
	"https://www.flickr.com/people/jasonh1234/",
	"https://medium.com/@j_holtslander"
	]
}

Another example taken from schema.org you might like:

person.jsonld · 565B test

{
  "@context": "https://schema.org",
  "@type": "Person",
  "address": {
    "@type": "PostalAddress",
    "addressLocality": "Seattle",
    "addressRegion": "WA",
    "postalCode": "98052",
    "streetAddress": "20341 Whitworth Institute 405 N. Whitworth"
  },
  "colleague": [
    "http://www.xyz.edu/students/alicejones.html",
    "http://www.xyz.edu/students/bobsmith.html"
  ],
  "email": "mailto:[email protected]",
  "image": "janedoe.jpg",
  "jobTitle": "Professor",
  "name": "Jane Doe",
  "telephone": "(425) 123-4567",
  "url": "http://www.janedoe.com"
}

If you are looking for a JSON-LD code snippet of a person with organization, here is another one from schema.org

person.jsonld · 225B test

{
  "@context": "https://schema.org/",
  "@type": "Person",
  "name": "Peter Venkman",
  "hasOccupation": {
    "@type": "Occupation",
    "name": "Parapsychologist",
    "educationRequirements": "PhD in parapsychology"
  }
}

Results

As with any type of structured data, there are no guaranteed results. If you are dedicated in your efforts and have a good amount of authority Google may produce a Knowledge panel.

Google retrieves answer boxes and featured snippets from a variety of sources including websites with structured (and unstructured) data, Wikipedia, Wikidata, Freebase and a number of other public data sources.

matt cutts

There are other results that may or may not be produced as a result of JSON-LD schema markup for a person such as a person's height, birthday, place of birth, and much more.

jsonld

json ld birth place

google serp knowledge graph wife

A more recent example from 2024

Person as author (the most common use case)

Eight times out of ten, what you actually want is Person nested inside an Article or BlogPosting as the author. Google uses this to attribute content for E-E-A-T and to power author bylines in the SERP. Here is the canonical pattern:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to deploy an Astro site to Cloudflare Pages",
  "datePublished": "2026-04-15T09:00:00Z",
  "author": {
    "@type": "Person",
    "@id": "https://example.com/#patrick",
    "name": "Patrick Coombe",
    "url": "https://example.com/about",
    "image": "https://example.com/headshot.jpg",
    "jobTitle": "SEO Consultant",
    "worksFor": { "@type": "Organization", "name": "Elite Strategies" },
    "sameAs": [
      "https://x.com/pmkoom",
      "https://www.linkedin.com/in/patrickcoombe"
    ]
  }
}

Two things that matter:

Use a stable @id for the Person node. Reuse the same @id across every article they author so Google merges them into one entity.
Always include sameAs with at least one canonical profile (LinkedIn, Wikidata, X, the author's personal site). This is what Google uses to confirm the person is real and disambiguate them from other people with the same name.

Author schema vs Author byline

The Person markup above feeds the byline Google may show under your article in the SERP. It does not, on its own, create an author profile page or a knowledge panel -- those come from the standalone Person snippets at the top of this page, paired with strong external signals (Wikipedia, Wikidata, press mentions).

Need a generator? The Person schema generator has fields for jobTitle, worksFor, and sameAs already wired up.