Eleven Person properties for your own page, and what each one is for
. Compiled by the Person Engine Optimization desk from the sources listed at the end of this page.
Schema.org defines name, alternateName, description, image, url, sameAs, jobTitle, worksFor, knowsAbout, alumniOf and award for a person. Google's profile page documentation requires name and recommends alternateName, description, image and sameAs, among others. Neither source says any property earns a knowledge panel. Checked on 12 November 2026.
The eleven properties
| No. | Property | What schema.org says it is | Named by Google's profile page | What it is for on your page |
|---|---|---|---|---|
| 1 | name | The name of the item | Required | The one spelling of your name that every other property hangs from. Use the same form everywhere. |
| 2 | alternateName | An alias for the item | Recommended | A second public identifier, such as a handle or a shorter form of your name. |
| 3 | description | A description of the item | Recommended | A plain byline or statement of your credentials, in the words you use elsewhere. |
| 4 | image | An image of the item, as a URL or an ImageObject | Recommended | One profile photo, the same file used across your profiles. Google says not to use placeholder images. |
| 5 | url | URL of the item | Not named | The address of the page that is about you. |
| 6 | sameAs | URL of a reference web page that unambiguously indicates the item's identity | Recommended | Links to your other profiles and reference pages, so the same person is recognised across them. |
| 7 | jobTitle | The job title of the person | Not named | What you do, written the way your employer or clients write it. |
| 8 | worksFor | Organizations that the person works for | Not named | The organisation you work for or run, linked to its own page. |
| 9 | knowsAbout | A topic that is known about, suggesting possible expertise without implying it | Not named | The subjects you write and speak on. Keep it to what your published work shows. |
| 10 | alumniOf | An organization that the person is an alumni of | Not named | Schools or programmes you attended, only if you want them public. |
| 11 | award | An award won by or for this item | Not named | Awards that can be checked on the awarding body's own page. |
What the two sources are, and are not
Schema.org is the shared vocabulary that structured data uses. Its Person page lists the properties a person can carry. Google's profile page documentation is a separate page that tells website owners which properties Google reads when a page is about a creator in an online community. It states that the markup helps Google understand the creators who post in a community.
Neither page says that adding properties produces a knowledge panel. Google's help page on panels says panels are generated automatically from sources across the web, so markup is one of many inputs and is not a request form.
Why identity properties come first
Properties one to six exist to answer a single question: is this the same person as the one named elsewhere? A name that changes spelling between pages, a different photo on each profile or a sameAs list that points at abandoned accounts weakens that answer. Fixing those is cheap and sits entirely in your hands.
The credential properties need restraint
JobTitle, worksFor, knowsAbout, alumniOf and award describe claims about you. Schema.org describes knowsAbout as suggesting possible expertise without implying it, which is the right way to think about all five. Write only what a public page can back up, because other sources will be read against what your page says.
How to use the list
- Pick the one spelling of your name and use it in property one on every page.
- Fill properties one to six first and check each link opens.
- Add the credential properties that you can support with a public page.
- Run your page through a structured data validator and fix errors.
- Update the markup on the same day you change a profile.
Where a build fits
Markup is part of the work on the references a panel draws on. Our build costs $3,000 and runs 60 to 90 days. A panel tends to appear on the bare name 6 to 12 months after, and nobody can guarantee a panel.
What this list cannot tell you
This list cannot tell you whether your markup is read, or whether a panel will follow. Google's profile page documentation is written for online community creators, and Google can change its pages at any time.
Questions people ask
What properties should a Person schema include?
Schema.org defines name, alternateName, description, image, url, sameAs, jobTitle, worksFor, knowsAbout, alumniOf and award for a person. Google's profile page documentation requires name and recommends alternateName, description, image and sameAs, among others.
Does Person schema get you a Google Knowledge Panel?
Neither schema.org nor Google's pages say so. Google says knowledge panels are generated automatically from sources across the web. Structured data helps describe you but is not a way to ask for a panel.
What does sameAs do on a personal page?
Schema.org defines it as a URL of a reference web page that unambiguously indicates the item's identity. In practice it lists your other profiles and reference pages so each can be matched to the same person.
Should I put my date of birth in my schema?
Schema.org has a birthDate property, but this list leaves it out. Google's help page lets owners ask for date of birth to be left off a panel, so think before publishing it.
Read next
- Getting your knowledge panel verified
- My knowledge panel is wrong
- Build my knowledge panel
- Knowledge panel versus Wikipedia