The Ultimate Person
Schema Generator
Build an individual's presence in the Knowledge Graph — job title, affiliations, and social profiles — essential for author bios, team pages, and personal brands.
Magic Build
Paste your URL below and our AI will automatically fill the Person fields for you.
Configuration
Live GeneratorWhy use Person?
Build an individual's presence in the Knowledge Graph — job title, affiliations, and social profiles — essential for author bios, team pages, and personal brands.This type is officially supported by major search engines for enhancing search listing appearance.
Output Panel
Want to automate this?
Connect your site to SchemaGen and our AI will automatically extract and deploy schemas for you. No manual coding required.
Launch AI GeneratorWhat is Person Schema?
Build an individual's presence in the Knowledge Graph — job title, affiliations, and social profiles — essential for author bios, team pages, and personal brands.
Google uses Person structured data to understand the content and context of your pages. When correctly implemented, this schema can unlock rich results in Google Search — enhancing your listing with additional information that dramatically improves visibility and click-through rates.
Why Add Person Structured Data?
Appear in Rich Results
Structured data helps Google show enhanced results for your pages in search — including stars, prices, FAQs, and more.
Boost Click-Through Rate
Rich snippets can increase CTR by up to 30% compared to plain search results — more clicks with the same ranking.
Feed AI Search Engines
AI answer engines like Perplexity and Google SGE use structured data to verify and cite facts from your content.
How to Implement Person JSON-LD
Generate
Use the form above to fill in your details and generate valid Person JSON-LD markup in seconds.
Copy
Copy the generated JSON-LD output code with one click — it's already formatted and ready to deploy.
Deploy
Paste the code into your <head> tag, or use SchemaGen's SDK to deploy without touching code.
Want to skip steps 2 & 3? Connect SchemaGen's SDK to deploy directly from the dashboard.
Properties You Can Include
Person schema supports the following schema.org properties. Required fields are the minimum Google needs to consider your markup valid; recommended fields unlock richer search result appearances.
| Property | Description | Expected Type | Status |
|---|---|---|---|
| additionalName | An additional name for a Person, can be used for a middle name. | Text | Optional |
| additionalType | An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. This is a relationship between something and a class that the thing is in. Typically the value is a URI-identified RDF class, and in this case corresponds to the use of rdf:type in RDF. Text values can be used sparingly, for cases where useful information can be added without their being an appropriate schema to reference. In the case of text values, the class label should follow the schema.org style guide. | Text, URL | Optional |
| address | Physical address of the item. | PostalAddress, Text | Optional |
| affiliation | An organization that this person is affiliated with. For example, a school/university, a club, or a team. | Organization | Optional |
| agentInteractionStatistic | The number of completed interactions for this entity, in a particular role (the 'agent'), in a particular action (indicated in the statistic), and in a particular context (i.e. interactionService). | InteractionCounter | Optional |
| alternateName | An alias for the item. | Text | Optional |
| alumniOf | An organization that the person is an alumni of. | EducationalOrganization, Organization | Optional |
| award | An award won by or for this item. | Text | Optional |
| awards | Awards won by or for this item. | Text | Optional |
| birthDate | Date of birth. | Date | Optional |
| birthPlace | The place where the person was born. | Place | Optional |
| brand | The brand(s) associated with a product or service, or the brand(s) maintained by an organization or business person. | Brand, Organization | Optional |
| callSign | A [callsign](https://en.wikipedia.org/wiki/Call_sign), as used in broadcasting and radio communications to identify people, radio and TV stations, or vehicles. | Text | Optional |
| children | A child of the person. | Person | Optional |
| colleague | A colleague of the person. | Person, URL | Optional |
| colleagues | A colleague of the person. | Person | Optional |
| contactPoint | A contact point for a person or organization. | ContactPoint | Optional |
| contactPoints | A contact point for a person or organization. | ContactPoint | Optional |
| deathDate | Date of death. | Date | Optional |
| deathPlace | The place where the person died. | Place | Optional |
Example Person JSON-LD
Here's what valid Person structured data looks like with sample values filled in. Use the generator above to replace these with your own data.
{
"@context": "https://schema.org",
"@type": "Person",
"name": "Example Person",
"image": "https://example.com/images/example.jpg",
"url": "https://example.com/page",
"additionalName": "Example additionalName",
"additionalType": "Example additionalType",
"address": {
"@type": "PostalAddress",
"name": "Example PostalAddress",
"image": "https://example.com/images/example.jpg",
"url": "https://example.com/page"
},
"affiliation": {
"@type": "Organization",
"name": "Example Organization",
"image": "https://example.com/images/example.jpg",
"url": "https://example.com/page"
},
"agentInteractionStatistic": {
"@type": "InteractionCounter",
"name": "Example InteractionCounter",
"image": "https://example.com/images/example.jpg",
"url": "https://example.com/page"
}
}Validate Your Person Schema
Once deployed, validate your schema is working correctly with our free audit tool. Paste your URL and we'll check for errors, missing properties, and Google Rich Result eligibility.
Check your Person schema for errors and Rich Result eligibility