Person
Behind every business and every blog post is a real person. Person schema describes them once, in one place, so every page they touch can point back to the same human.
Why people need schema too
Search engines and AI tools care a lot about who is behind content. Is this guide to letterpress paper written by someone who prints for a living, or by nobody in particular? Your about page answers that for people. Person schema answers it for machines.
There's no special Google search result for Person on its own. The value is in connections: this person works for this business, wrote these articles, and is the same person as these social profiles. Each link makes the whole picture clearer.
When to use it
- On a bio or about page for a founder, author, or team member. This is the home for the full Person block.
- As the
authorof articles and blog posts (you saw this in the Article lesson). - As the
founderinside your Organization block, if you like.
Only describe real people who appear on your site, with details they're comfortable sharing publicly. No home addresses, no personal phone numbers.
The code
Fern & Ink's about page is all about founder Maya Lund. It gets two items in one @graph: a ProfilePage for the page, and a Person for Maya.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "ProfilePage",
"@id": "https://fernandink.example/about/#webpage",
"url": "https://fernandink.example/about/",
"name": "About Maya Lund | Fern & Ink",
"dateCreated": "2025-03-10T10:00:00-05:00",
"dateModified": "2026-08-21T16:15:00-05:00",
"isPartOf": { "@id": "https://fernandink.example/#website" },
"mainEntity": { "@id": "https://fernandink.example/about/#maya" }
},
{
"@type": "Person",
"@id": "https://fernandink.example/about/#maya",
"name": "Maya Lund",
"jobTitle": "Founder and Lead Designer",
"description": "Maya Lund is a Minneapolis designer and letterpress printer who founded Fern & Ink in 2015.",
"url": "https://fernandink.example/about/",
"image": "https://fernandink.example/images/maya-lund.jpg",
"worksFor": { "@id": "https://fernandink.example/#organization" },
"knowsAbout": ["Letterpress printing", "Brand identity design", "Typography", "Wedding stationery"],
"sameAs": [
"https://social.example/@mayalund",
"https://portfolio.example/mayalund"
]
}
]
}
Line by line
For a standalone Person, Google doesn't publish a required list, so these tags are our advice. (ProfilePage is different; we'll get to it below.)
| Property | Our advice | What it does |
|---|---|---|
name | Recommended | The person's name, and only their name. No "Founder" or "MFA" in here. |
@id | Recommended | A permanent name tag. We use the about page URL plus #maya. Every other page refers to Maya by this. |
url | Recommended | The page about this person. Usually the same page that holds this block. |
jobTitle | Recommended | Their role, as shown on the page. |
worksFor | Recommended | Points at your business's #organization @id. |
image | Recommended | A real headshot that appears on the page. |
sameAs | Recommended | Links to this same person's profiles on other sites. |
description | Optional | A short bio, matching the first lines of the visible one. |
knowsAbout | Optional | A list of topics they're genuinely expert in. Keep it short and specific. |
sameAs: "this is also me"
The sameAs list says "the Maya on this page is the same person as the Maya on these other sites." In real life, those would be profiles like LinkedIn, Instagram, Behance, or a Wikipedia page if she had one. (We've used made-up .example addresses here so we don't point at real accounts.)
Only list profiles that actually belong to this person and that you'd be happy for someone to click. A dead link or someone else's account with the same name does more harm than good.
knowsAbout: honest expertise
It's tempting to list twenty keywords. Don't. Four or five real topics, backed up by what's on the page and the articles they've written, tell a much clearer story.
ProfilePage: the page about a person
ProfilePage is a WebPage type that says "this whole page is about one person (or organization)." Google's docs list an "About Me" page on a blog and an employee page on a company site as good examples. A store's homepage is not.
Google is specific about this one:
- Required
mainEntity, the Person (or Organization) the page is about, with aname. - Recommended
dateCreatedanddateModifiedon the page, plusimage,sameAs,description, and a few others on the Person.
In our example, mainEntity doesn't repeat Maya's details. It just points at #maya, and the full Person sits right next to it in the graph. Same idea as provider in the Service lesson.
Using Maya as an author everywhere
Here's the payoff. Once Maya's full profile lives on the about page, every blog post she writes can refer to her like this:
{
"author": {
"@type": "Person",
"@id": "https://fernandink.example/about/#maya",
"name": "Maya Lund",
"url": "https://fernandink.example/about/"
}
}
Why repeat name and url when the @id already points to her? Because Google's Article guidelines ask for the author's name and url right there on the article, and not every tool follows @id links across pages. Including both is the safe pattern: the @id connects the dots, and the name and url make each post understandable on its own.
The key is consistency. Use the exact same @id on every post, in every template. If one post says #maya and another says #maya-lund, you've accidentally described two people.
Common mistakes
- Titles in the name.
"name": "Maya Lund, Founder". Put "Founder" injobTitle. - Shifting
@ids. Different spellings of the same person's@idon different pages. - Stuffed
sameAs. Every directory listing you can find, or accounts that aren't theirs. - Private details. Personal emails, home addresses, or birthdays nobody agreed to publish.
Try it
Write a Person block for yourself (or a teammate) with an @id on your own about page. Include name, jobTitle, url, worksFor, and two sameAs links to profiles you actually use. Then wrap it in a @graph with a ProfilePage whose mainEntity points at your @id.
Check yourself
- My Person has a clean
name, aurl, and a stable@id. worksForpoints at my business's#organization@id.- My
sameAslinks are real profiles that belong to this person. - My about page uses ProfilePage with
mainEntitypointing at the Person. - Every article uses the same author
@id, plus name and url.
Person alongside FAQ, Event, Recipe, and Reviews: Schema Markup Explained, Part 3: FAQ, Person, Event, Recipe, and Reviews.