Person schema markup is structured data, written in schema.org vocabulary, that tells search engines a page describes a specific human being and lists verifiable facts about them. For authors and founders, it is one of the most effective ways to help Google recognise you as a distinct entity, connect your profiles, and qualify you for rich results and Knowledge Panels. You add it as JSON-LD to the page that best represents you, usually your author or About page.
This guide covers the key properties, a working example, common mistakes, and how to validate your markup.
What Person Schema Is
Schema.org provides a shared vocabulary that search engines understand. The Person type identifies an individual and lets you declare structured facts, name, role, employer, expertise, and links to other profiles.
Without it, Google has to infer who a page is about from prose alone. With it, you state your identity explicitly and machine-readably. That clarity is the foundation of entity SEO, the practice of optimising for entities rather than keywords, which we explain in our guide on what entity SEO is.
The recommended format is JSON-LD, a block of code placed in the page’s HTML. It is easy to maintain and Google’s preferred format.
Key Properties for Authors and Founders
Not every property matters equally. For personal branding and entity building, focus on these:
name— your full name, spelled exactly as it appears everywhere else.jobTitle— your role, for example “Founder” or “SEO Consultant.”image— a URL to a high-quality, consistently used photo.worksFor— the organisation you represent, as anOrganizationobject.alumniOf— schools or universities you attended, useful for E-E-A-T.knowsAbout— topics you are an authority on; this maps you to subject areas.url— your canonical entity home.sameAs— an array of URLs to your verified profiles (LinkedIn, X, Wikidata, Crunchbase, etc.).
The sameAs property is the workhorse of identity. It tells Google that all the listed accounts refer to the same person, sharply reducing ambiguity between people with similar names.
A JSON-LD Example
Here is a compact Person schema example you can adapt. Place it inside a <script type="application/ld+json"> tag on your entity home:
{
"@context": "https://schema.org",
"@type": "Person",
"name": "Jane Doe",
"jobTitle": "Founder & SEO Consultant",
"url": "https://example.com/about/",
"image": "https://example.com/images/jane-doe.jpg",
"worksFor": {
"@type": "Organization",
"name": "Example Agency",
"url": "https://example.com"
},
"alumniOf": {
"@type": "CollegeOrUniversity",
"name": "University of Example"
},
"knowsAbout": ["Entity SEO", "Technical SEO", "Content Strategy"],
"sameAs": [
"https://www.linkedin.com/in/janedoe",
"https://x.com/janedoe",
"https://www.wikidata.org/wiki/Q000000"
]
}
Replace the placeholder values with your real, consistent data. Keep the url pointing to your single authoritative page, and make sure every sameAs link actually resolves to a profile you control or that references you.
Choosing the Right Page
Place your Person schema on your entity home, the one canonical URL Google should treat as the source of truth about you. For most authors and founders this is an author page or a detailed About page.
Do not scatter conflicting Person markup across many pages. Instead, mark up your entity home thoroughly and link to it from other pages. Our post on what an entity home is and how to build one explains how to choose and structure this page so your schema does the most good.
Common Mistakes to Avoid
Person schema is simple, but small errors undermine it. Watch for these:
- Inconsistent facts. Your
name,jobTitle, andimagemust match what appears across your site and profiles. Contradictions confuse Google. - Weak or fake
sameAslinks. Only list real, authoritative profiles. Broken or irrelevant links dilute the signal. - Marking up content that is not visible. Schema should reflect information actually present on the page, not hidden or invented claims.
- Multiple conflicting Person entities. Declaring several different
Personblocks for the same individual across pages creates ambiguity. - Forgetting to update it. When your role or company changes, update the markup so it stays accurate.
Avoiding these keeps your entity clean and trustworthy, the same disciplined approach we apply in our SEO services.
Validating With the Rich Results Test
Always test your markup before and after publishing. Use Google’s Rich Results Test:
- Enter your page URL or paste the code.
- Confirm the
Personentity is detected with no errors. - Review any warnings and fix missing recommended properties.
You can also use the Schema Markup Validator for broader schema.org checks. Validation catches syntax mistakes and confirms Google can read your structured data, an essential step before expecting any entity benefits. If you later pursue a Knowledge Panel, valid Person schema is a prerequisite, as covered in our guide on how to get a Google Knowledge Panel.
This structured-data-first method reflects how Arnab Piush Biswas, WikiSEO’s founder and the author of this guide, builds recognisable entities for authors and founders.
Frequently Asked Questions
Where should I put my Person schema?
On your entity home, the single authoritative page that best represents you, usually an author or About page. Mark up that one page thoroughly rather than spreading conflicting markup across your site.
Is Person schema enough to get a Knowledge Panel?
It helps but is not sufficient on its own. A panel also requires notability, independent references, and consistent data across the web. Person schema strengthens the identity signals that support a panel.
Which is the most important Person property?
sameAs is often the most valuable for entity SEO because it links all your verified profiles to one identity, reducing ambiguity. name, jobTitle, and knowsAbout are close behind.
How do I know my markup is working?
Validate it with Google’s Rich Results Test and Schema Markup Validator. A clean result confirms Google can read the structured data; entity benefits then build over time as Google recrawls and trusts the signals.
Want expertly implemented structured data that helps Google recognise you? Contact us to get your Person schema and entity strategy done right.
