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.

Should every author page have this?

Yes for content sites. Marking up the byline author with a Person schema clarifies who wrote a piece, which strengthens authorship and expertise signals.

What goes in the affiliation field?

affiliation is the organization the person belongs to, modeled as a nested Organization object with a name. Use the employer, university, or company.

Does the email get exposed publicly?

Yes — anything in JSON-LD is visible in page source. Only include an email you are comfortable publishing, or leave it blank to omit it.

How do I link this to my Organization schema?

Reference the same organization name in both the Person affiliation and your Organization block so search engines connect the entities cleanly. Validate both with the Rich Results Test.

What is the JSON-LD Person Schema Builder?

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. It runs free in your browser on Gera Tools, with nothing uploaded.

JSON-LD Person Schema Builder

Name: JSON-LD Person Schema Builder
Creator: Gera Tools
License: https://creativecommons.org/licenses/by/4.0/

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.

Where Person schema fits in E-E-A-T

Google’s quality rating guidelines assess Experience, Expertise, Authoritativeness, and Trustworthiness (E-E-A-T). For content sites — especially those covering health, finance, or legal topics — clearly attributing articles to real named authors with verifiable credentials is important. Person structured data contributes to this by:

Connecting bylines to identities. The name field ties the author’s name as it appears in the byline to a machine-readable entity.
Linking to authoritative profiles. The sameAs array points search engines to LinkedIn, a university faculty page, ORCID, or other places that independently verify the person’s expertise.
Establishing credentials. jobTitle and affiliation declare the person’s professional context.

This markup alone does not guarantee better rankings, but it gives search engines the signals to understand who wrote your content.

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.

What to include and what to leave out

Field	Include when	Leave blank when
`email`	The person publicly uses this email for professional contact	It is a private address or not published elsewhere
`image`	There is a publicly hosted professional photo	No suitable image exists (empty `image` fields weaken the markup)
`jobTitle`	The person has a clear current role	Title would be misleading or out of date
`sameAs` links	The linked profile is actively maintained	The account is inactive or belongs to a different person with the same name

Unlike some schema types, Person markup is purely informational — there is no rich result visual format specific to it. Its value is as an entity signal, not a search result enhancement.