Add a person’s name, job title, employer, social profiles and contact details. Copy valid schema.org Person JSON-LD and paste it into the author, about or team page <head>. Free, no sign-up, and nothing leaves your browser.
Comma separated.
Add gender and birth date only if the information is public and relevant to the page.
Person schema is structured data, based on the schema.org Person type, that describes an individual: their name, role, employer, social profiles and contact details. You add it as JSON-LD to the page that is about that person.
Person markup helps search engines and AI answer engines connect a name to one consistent, verifiable identity. It suits author bio pages, founder and about pages, team profiles and speaker pages.
Google has no dedicated rich result for a standalone Person, so treat it as an entity signal. It does not guarantee a knowledge panel or any change in how your page looks in search.
{
"@context": "https://schema.org",
"@type": "Person",
"@id": "https://example.com/about/jane#person",
"name": "Jane Doe",
"url": "https://example.com/about/jane",
"image": "https://example.com/jane.jpg",
"jobTitle": "Founder and CEO",
"worksFor": {
"@type": "Organization",
"name": "Acme Corp",
"url": "https://acmecorp.com"
},
"sameAs": [
"https://www.linkedin.com/in/janedoe",
"https://x.com/janedoe"
]
}Only the name is needed for valid markup. Adding the properties that apply makes the person easier to identify.
| Property | What it describes | Priority |
|---|---|---|
name | The person’s full name, as shown on the page | Required |
url | The page or site that represents the person | Recommended |
image | A profile photo on a crawlable URL | Recommended |
jobTitle, worksFor | Role and the Organization they work for | Recommended |
sameAs | Official profiles such as LinkedIn, X or Wikipedia | Recommended |
description, knowsAbout | A short bio and areas of expertise | Recommended |
email, telephone, address | Public contact details | Optional |
alternateName, gender, birthDate | Other names and public personal details | Optional |
They use the same Person type in two different places. Most sites use both.
Goes on the person’s own page: an author bio, about page or team profile. It carries the full profile with employer, social links and contact details. Use this generator.
A small Person object, usually just a name and URL, inside an Article or BlogPosting author property. It covers byline attribution. Use the Article Schema Generator for that.
sameAs links a person to their profiles elsewhere, such as LinkedIn, X, GitHub or Wikipedia. These links help search engines and AI systems tell one “Jane Doe” from another and treat the profiles and the page as one real-world entity.
It matters most for authors and experts, where a clear identity supports how content is attributed. Only list profiles the person controls, and keep the name and job title consistent with them.
"sameAs": [ "https://www.linkedin.com/in/janedoe", "https://x.com/janedoe", "https://github.com/janedoe", "https://en.wikipedia.org/wiki/Jane_Doe" ]
The generator does the writing. These four steps take you from a blank form to tested markup.
Enter the full name, then the profile URL and a photo.
Add the job title and the company they work for.
Add the official profiles, plus an optional bio and contact details.
Paste the script into the person’s page head, then run the Rich Results Test.
Add one Person block on the person’s own page rather than on every page that mentions them. SEO plugins often output author markup already, so check your page source first and avoid duplicates.
Short answers on properties, placement and what the markup can do.
Person schema describes an individual: name, role, employer, social profiles and contact details. It helps search engines and AI systems connect a name to one consistent, verifiable identity across the web.
Only a name is needed for valid markup. Job title, employer, social profiles, bio, contact details and address are optional, but they make the person easier to identify.
They are the same Person type used in two places. A small Person nested in an Article’s author property covers the byline. Standalone Person schema on the person’s own page carries the fuller profile.
sameAs lists the URLs of a person’s other profiles, such as LinkedIn, X, GitHub or Wikipedia. It helps search engines confirm that those profiles and your page describe the same person.
Only if the information is public and relevant to the page. Skip both on most professional or author bio pages, where they add little value.
Not on its own. Knowledge panels come from many signals across the web. Person schema with strong sameAs links can support them, but it does not guarantee a panel.
Google says AI features need no special markup. Clear names, roles and profiles in both the page and the schema make a person easier to attribute accurately, though they do not guarantee inclusion.
Yes. It is completely free, with no sign-up and no limit. Everything runs in your browser, so the details you enter are never uploaded to a server.
Person markup works best with the organization and article markup around it.
Search Savvy’s technical SEO team implements and monitors schema across every template, and fixes the technical issues that hold your site back.