Free Person Schema Generator

Generate valid Person JSON-LD structured data for author bios, team pages, and staff profiles. Add job title, employer, expertise, and social profiles, then copy the markup. Free, no sign-up required.

Build Your Person Schema

IdentityWho this person is. Match the details to what the page actually says.

The person's full name as it appears on the page. Required for valid Person markup.

A byline, pen name, or professional form of the name.

A couple of sentences. Say what they do and what they are known for.

A real headshot, at least 1200px wide where possible.

The page this markup lives on, usually their bio page.

Contact (optional)Only add details this person is happy to publish.

Employer (optional)The business or practice this person works for.

Location (optional)Where this person is based. City level is usually enough.

Expertise (optional)What this person actually knows about. One topic per row.

The school, college, or university they trained at.

Awards (optional)Real, verifiable recognition only. One per row.

Profiles (optional)Links to the same person elsewhere: LinkedIn, X, a professional register, a personal site.

Enter the person's name above and your JSON-LD will build here automatically.

Generated JSON-LD

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person"
}
</script>

How to add it to your site

  1. Copy the code above.
  2. Paste it inside the <head> section of that person's bio page. Give each person their own block on their own page.
  3. Validate it with the Google Rich Results Test or the Schema.org Validator.
  4. Deploy, then request indexing in Google Search Console to speed things up.

Build better bio pages around your schema

Structured data tells search engines who this person is. These free widgets convince the visitor reading the page.

Explore More Free Tools

Other free tools to help you optimize and grow.

How It Works

How to use this free person schema generator

No account needed, no sign-up, completely free. Fill in the bio details, and valid JSON-LD structured data builds live, ready to copy into your page.

1

Add the identity details

Enter the full name, job title, a short bio, a real headshot, and the URL of the bio page this markup will live on.

2

Add employer, expertise, and profiles

Connect the person to the business they work for, list what they genuinely know about, and link their LinkedIn or professional register profiles. Everything you type builds the markup live.

3

Copy and validate

Copy the generated JSON-LD, paste it into the head of the bio page, and confirm it with the Google Rich Results Test. No sign-up, completely free.

The Basics

What is person schema, and why does it matter?

Search engines read your team page, but structured data tells them exactly who they are looking at: which person, what role, what they know, and who they work for.

The idea

A real person's details → schema.org vocabulary → JSON-LD in your <head>

Result: a named, described individual rather than an anonymous byline

Person schema is structured data that describes an individual using the shared schema.org vocabulary. Instead of hoping Google works out from your HTML that a heading is a name and the paragraph beneath it is a bio, you state the name, role, employer, and expertise explicitly in a format built for machines to read.

The recommended format is JSON-LD: a small block of JSON placed in the head of the page. It lives separately from your visible content, so it is easy to add without touching your design. It is most useful on author bios, team pages, and profiles for named professionals whom customers choose to work with personally.

Structured data does not guarantee rankings or rich results, and Person markup is not itself a ranking factor. What it does is make the people behind your content and your service unambiguous to search engines and to the AI assistants summarizing them.

Where To Use It

Three pages that earn their Person markup

Person schema pays off wherever a real, named individual matters to the reader's decision. Here are the three cases worth doing properly.

Use caseWhat it doesWhere it goesValue
Author bioAttaches a real, described person to the content they wrote, rather than an anonymous byline.Blog posts, guides, and anything with an author.Common
Team pageDescribes each member of staff with their job title, expertise, and employer.About and team pages, one block per person page.Common
Practitioner profileIdentifies a named professional with credentials, training, and the practice they work at.Dentists, therapists, lawyers, consultants.High value

Based on the schema.org Person type and its documented properties, 2026.

What It Can Unlock

What person schema can do for you

Structured data helps search engines understand the people behind your business. Search features are never guaranteed, but the clarity is worth having.

👤

A named, described person

Explicit Person markup states who someone is, rather than leaving search engines to infer a name from a page heading.

🎓

Credentials made readable

Job title, training, and expertise become machine-readable rather than buried in a paragraph of prose.

🔗

Profiles tied together

Linking LinkedIn, X, or a professional register with sameAs helps confirm those profiles describe the same person.

🏢

Connected to the business

The worksFor property links a person to their organization, tying your team page to your business markup.

✍️

Clearer authorship signals

Pairing Person markup with Article markup makes it explicit who wrote a piece, which supports experience and expertise signals.

🤖

AI answer clarity

When an AI assistant summarizes who does what at your business, structured data makes the details easier to read and attribute.

Avoid These

Six person schema mistakes that cause problems

Structured data helps only when it is accurate and valid. Steer clear of these common errors.

📄

One shared block for the whole team

A single Person block cannot describe five people. Give each person their own page and their own markup, or the data describes nobody accurately.

One person per block
🎭

Inflating job titles or expertise

Only list credentials, awards, and expertise the person genuinely has. Inflated claims are a guidelines problem, and they are easy to check.

Claim only what is true
🖼️

A stock photo headshot

The image should be the actual person. A stock portrait attached to a named professional misrepresents who visitors will deal with.

Use a real photo
🔗

sameAs links that are not theirs

Only link profiles that genuinely belong to this person. A company LinkedIn page is not the same entity as an employee.

Link the right profiles
📵

Publishing contact details without consent

Email and phone in markup are public. Ask the person before adding them, and leave them out if there is any doubt.

Ask before publishing

Never validating

Always run your markup through the Rich Results Test and the Schema.org Validator. A single syntax slip can invalidate the whole block.

Validate before you ship

Get More From It

6 tips for effective person markup

Practical ways to make your schema work harder. All CommonNinja widgets mentioned are free to start.

01

Give every person their own page

Person markup works best on a dedicated bio page. If your whole team shares one page, the markup can only really describe one of them.

02

Pair it with Article markup for authors

On a blog post, reference the author as a Person inside your Article markup. It connects the content to a real, described writer.

03

Let clients vouch for the person

Schema states the credentials; testimonials prove them. Put real client words on the same page as the bio.

Try the Testimonials widget
04

Be specific with expertise

Pediatric nutrition says far more than health. Narrow topics in knowsAbout describe a specialist; broad ones describe nobody in particular.

05

Link the professional register

For regulated professions, a link to the official register or licensing body is one of the strongest sameAs links you can add.

06

Keep bios current

When someone changes role or leaves, update or remove the markup. Stale team data is a slow, quiet credibility leak.

Glossary

Key person schema fields

A quick reference for the properties behind person markup.

FieldDefinitionExampleWhen It Matters
nameThe person’s full name, matching what the page shows. This is the anchor for everything else.Jane DoeEvery person you mark up
jobTitleWhat they do, stated as a role rather than a description of duties.Registered DietitianTeam, staff, and author pages
worksForThe organization employing them, as a nested Organization. Ties a person to your business markup.Organization + nameAnyone employed by the business
knowsAboutSubjects this person genuinely has expertise in. Be specific: narrow topics say more than broad ones.Pediatric nutritionSpecialists and authors
alumniOfWhere they trained, as an EducationalOrganization. Useful for regulated and credentialed professions.University of TorontoPractitioners with formal training
sameAsLinks to the same person elsewhere, which helps confirm those profiles are all the same individual.LinkedIn profile URLAnyone with public profiles
imageA real photograph of the person, ideally a proper headshot rather than a stock portrait.https://.../jane.jpgEvery person you mark up

FAQ

Person schema markup is structured data that describes an individual using the schema.org vocabulary. It states their name, job title, employer, expertise, and profile links in a machine-readable format, rather than leaving search engines to infer them from a heading and a paragraph. This generator creates valid Person JSON-LD you can copy straight into your page.
It works best on pages about one specific individual: an author bio, a team member page, or the profile of a named professional such as a dentist, therapist, or consultant. It is also used inside Article markup to identify who wrote a post. If a page is about a business rather than a person, use LocalBusiness or Organization markup instead.
No, a Person block describes one individual. If your whole team shares a single page, that page cannot carry accurate markup for everyone on it. The better pattern is a page per person, each with its own Person block, linked from a team index page.
knowsAbout lists the subjects the person genuinely has expertise in. Be specific. Pediatric nutrition or commercial lease disputes describes a specialist; health or law describes nobody in particular. Only list topics they can actually back up, since inflated expertise claims are a guidelines problem.
Only with that person’s consent. Anything in your markup is public and machine-readable, so it can be scraped. Many teams publish a role-based address or a contact form instead of a personal one. If there is any doubt, leave the contact fields out entirely.
It helps make authorship and credentials explicit, which supports the signals Google’s quality guidance describes, but there is no direct schema-to-ranking mechanism. Structured data is not a shortcut for experience or expertise. It just means the credentials you genuinely have are stated in a form machines can read.
The worksFor property links a person to an Organization, so your team markup and your business markup describe a connected set of entities rather than unrelated pages. If you also publish LocalBusiness markup for your location, using the same organization name in both keeps them consistent.
Paste your page URL or the generated code into the Google Rich Results Test or the Schema.org Validator. Both are free and show errors and warnings. Validate after adding the markup, and again whenever someone changes role, so your team data does not quietly go stale.

Trusted by