JSON-LD Person Schema Builder

Create Person structured data for author pages and knowledge panels

Outputs a valid Person JSON-LD schema with name, jobTitle, affiliation, sameAs social links, email, and image for author bios, about pages, and knowledge panel eligibility.

What is Person schema used for?

Person structured data identifies an individual such as an author, founder, or public figure. It supports Google's E-E-A-T signals and can feed a knowledge panel for notable people.

Person structured data for authors and profiles

The schema.org Person type describes a real individual — an author, founder, researcher, or public figure. Adding it to bio and author pages helps search engines attribute content to a verified person, supports authorship signals, and can make a notable individual eligible for a knowledge panel. This builder emits clean JSON-LD using only the fields you provide.

How it works

The output is a JSON-LD object with @context set to https://schema.org and @type of Person. Your name, jobTitle, email, and image map directly to top-level properties. The affiliation becomes a nested object (@type: Organization) carrying the employer name. Every non-empty line in the social box is collected into the sameAs array, which links the person to their authoritative profiles elsewhere on the web. Blank inputs are dropped so no empty properties appear in the result.

Tips and example

sameAs is the highest-value field — link to LinkedIn, X, an institutional bio, ORCID, or Wikipedia. A complete block looks like this:

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Jordan Lee",
  "jobTitle": "Lead Engineer",
  "email": "[email protected]",
  "image": "https://example.com/jordan.jpg",
  "affiliation": {
    "@type": "Organization",
    "name": "Gera Systems Ltd"
  },
  "sameAs": [
    "https://www.linkedin.com/in/jordanlee",
    "https://x.com/jordanlee"
  ]
}

Place the block on the page that is genuinely about that person — a bio, about, or author page. Keep the affiliation name identical to the one in your Organization schema so the two entities link cleanly.