The Person schema is used to indicate data relating to yourself on the main page of your personal site. It tells search engines who you are, what you do and which official profiles belong to you, so your name is not confused with someone else’s.
How to use the Person schema generator
The tool above works in a desktop browser and requires a free account. The process takes a few minutes:
- Type your name the way you use it publicly, and add alternate names if you publish under more than one.
- Add your personal website address and a clear portrait photo that is already online.
- Fill in your job title and a short biography written in the third person.
- Add the URLs of your official profiles in sameAs, such as LinkedIn, X, a Wikidata entry or an author page.
- If you run a company, link it with the Organization schema instead of retyping its details.
- Generate the code, validate it and paste it into the head section of your home or About page.
Which Person properties are worth filling in
- name and alternateName: the public identity of the person.
- jobTitle and worksFor: the professional role and the organization.
- image: a clear photo of the person, hosted on your site.
- sameAs: profiles that confirm the identity across the web.
- knowsAbout: topics you are known for, if relevant.
Include only information you are happy to make public. Leave out birth dates, home addresses and phone numbers unless they are already published and you want them to be.
Example of Person JSON-LD
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Person",
"@id": "https://www.example.com/#person",
"name": "Jane Example",
"jobTitle": "Brand consultant",
"url": "https://www.example.com/about/",
"image": "https://www.example.com/images/jane-example.jpg",
"description": "Jane Example helps small companies manage their online reputation.",
"worksFor": { "@id": "https://www.example.com/#organization" },
"sameAs": [
"https://www.linkedin.com/in/jane-example",
"https://x.com/janeexample"
]
}
</script>Common mistakes to avoid
- Writing a Person schema about someone else without their agreement.
- Copying the same biography on every page of the site.
- Listing profiles in sameAs that show a different name or a different person.
- Placing the markup on pages where the person is not the subject.
Frequently asked questions
Where should the Person schema go?
On the page that is about the person, usually the home page of a personal site or an About page. The concept of the main page for an entity is explained in what is a Google entity home.
Can a Person schema create a knowledge panel?
It helps Google understand who you are, but it is not enough alone. If you cannot find a panel for your name, read why you may not have a knowledge panel.
How do I connect it to my company?
Generate an Organization schema and reference its identifier in worksFor. The linked schemas option of the generator builds the relationship for you.