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.
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.
The school, college, or university they trained at.
Enter the person's name above and your JSON-LD will build here automatically.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Person"
}
</script><head> section of that person's bio page. Give each person their own block on their own page.Structured data tells search engines who this person is. These free widgets convince the visitor reading the page.
Put client praise right next to the bio. Words from real customers do more for credibility than any self-description.
Pull your latest posts onto the page so visitors see current work, not a bio written two years ago.
Let people reach the right person directly, without hunting for an email address.
Show a portfolio, case studies, or headshots in a clean gallery that loads fast on any device.
Other free tools to help you optimize and grow.
Generate LocalBusiness JSON-LD with address, opening hours, and service area.
Use Tool →Generate Service JSON-LD for each service you offer, with provider and service area.
Use Tool →Generate Article, BlogPosting, and NewsArticle JSON-LD structured data for your posts.
Use Tool →Generate Organization, WebSite, and LocalBusiness JSON-LD structured data for your whole site.
Use Tool →Generate valid FAQ Page JSON-LD structured data to earn FAQ rich results.
Use Tool →Generate title, description, and social meta tags for any page in seconds.
Use Tool →How It Works
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.
Enter the full name, job title, a short bio, a real headshot, and the URL of the bio page this markup will live on.
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.
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
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
Person schema pays off wherever a real, named individual matters to the reader's decision. Here are the three cases worth doing properly.
| Use case | What it does | Where it goes | Value |
|---|---|---|---|
| Author bio | Attaches a real, described person to the content they wrote, rather than an anonymous byline. | Blog posts, guides, and anything with an author. | Common |
| Team page | Describes each member of staff with their job title, expertise, and employer. | About and team pages, one block per person page. | Common |
| Practitioner profile | Identifies 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
Structured data helps search engines understand the people behind your business. Search features are never guaranteed, but the clarity is worth having.
Explicit Person markup states who someone is, rather than leaving search engines to infer a name from a page heading.
Job title, training, and expertise become machine-readable rather than buried in a paragraph of prose.
Linking LinkedIn, X, or a professional register with sameAs helps confirm those profiles describe the same person.
The worksFor property links a person to their organization, tying your team page to your business markup.
Pairing Person markup with Article markup makes it explicit who wrote a piece, which supports experience and expertise signals.
When an AI assistant summarizes who does what at your business, structured data makes the details easier to read and attribute.
Avoid These
Structured data helps only when it is accurate and valid. Steer clear of these common errors.
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 blockOnly 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 trueThe image should be the actual person. A stock portrait attached to a named professional misrepresents who visitors will deal with.
Use a real photoOnly link profiles that genuinely belong to this person. A company LinkedIn page is not the same entity as an employee.
Link the right profilesEmail and phone in markup are public. Ask the person before adding them, and leave them out if there is any doubt.
Ask before publishingAlways 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 shipGet More From It
Practical ways to make your schema work harder. All CommonNinja widgets mentioned are free to start.
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.
On a blog post, reference the author as a Person inside your Article markup. It connects the content to a real, described writer.
Schema states the credentials; testimonials prove them. Put real client words on the same page as the bio.
Try the Testimonials widget →Pediatric nutrition says far more than health. Narrow topics in knowsAbout describe a specialist; broad ones describe nobody in particular.
For regulated professions, a link to the official register or licensing body is one of the strongest sameAs links you can add.
When someone changes role or leaves, update or remove the markup. Stale team data is a slow, quiet credibility leak.
Glossary
A quick reference for the properties behind person markup.
| Field | Definition | Example | When It Matters |
|---|---|---|---|
| name | The person’s full name, matching what the page shows. This is the anchor for everything else. | Jane Doe | Every person you mark up |
| jobTitle | What they do, stated as a role rather than a description of duties. | Registered Dietitian | Team, staff, and author pages |
| worksFor | The organization employing them, as a nested Organization. Ties a person to your business markup. | Organization + name | Anyone employed by the business |
| knowsAbout | Subjects this person genuinely has expertise in. Be specific: narrow topics say more than broad ones. | Pediatric nutrition | Specialists and authors |
| alumniOf | Where they trained, as an EducationalOrganization. Useful for regulated and credentialed professions. | University of Toronto | Practitioners with formal training |
| sameAs | Links to the same person elsewhere, which helps confirm those profiles are all the same individual. | LinkedIn profile URL | Anyone with public profiles |
| image | A real photograph of the person, ideally a proper headshot rather than a stock portrait. | https://.../jane.jpg | Every person you mark up |
From the Blog
Go deeper on building credibility and making your content easier for search engines to understand.
In this article, we are going to discuss SEO, explain why it’s important to the success of a website, and suggest ways...
Read article →In this article, we are going to explain how to create a Sports Teams website.
Read article →In this article, we will look at some important SEO factors to consider when building a website, for the purpose of...
Read article →In this article, we delve into the round-robin format, commonly used in sports and competitions.
Read article →Common Ninja partners with Durable, merging AI website building with dynamic widgets. A transformative web design era...
Read article →In this article, we discuss the importance of readability in SEO, highlighting its impact on search engine rankings,...
Read article →