Person Schema for Authors & E-E-A-T: The Complete Guide
Understand with AI
Discuss with your preferred AI assistant
Three or more authoritative profiles give search engines the confidence to treat an author as a known entity.
Only "name" is mandatory — but the value comes from jobTitle, url, image, worksFor, and sameAs.
Fill the form, copy the script tag, paste it into your page head, and validate — done in minutes.
Search engines no longer just rank pages — they try to understand the people behind them. Who wrote this article? Are they a recognised expert? Can the author be connected to a real, verifiable identity across the web? Person schema is how you answer those questions in machine-readable terms, and it sits at the heart of Google's E-E-A-T framework (Experience, Expertise, Authoritativeness, Trustworthiness).
This guide explains what Person JSON-LD is, exactly which properties matter, how to use the sameAs array to build entity confidence, and how to add the markup to your site in minutes — all of which our free generator does for you instantly.
What Is Person Schema?
Person schema is structured data based on the schema.org/Person type. Wrapped in JSON-LD, it describes an individual — their name, job title, employer, profile photo, areas of expertise, and the other places that same person exists online. You typically add it to author bio pages, "About" pages, team pages, and the byline area of articles.
The point is disambiguation. There are thousands of people named "John Smith." Person schema, combined with sameAs links to authoritative profiles, helps Google connect your John Smith to a single, well-understood entity in its Knowledge Graph. That entity-level understanding is increasingly what powers author trust, knowledge panels, and AI Overviews.
Why Person Schema Matters for E-E-A-T
Google's quality guidelines reward content created by demonstrable experts. While schema markup is not a direct ranking factor, it is the cleanest way to declare author identity and expertise so algorithms do not have to guess. The benefits compound:
- Entity recognition — clear identity signals help Google treat the author as a known entity rather than an anonymous byline.
- Author trust — linking a name to a real job title, employer, and verified profiles supports the "who created this" question reviewers and systems ask.
- Knowledge panel eligibility — well-connected Person entities are candidates for knowledge panels and rich author treatments.
- AI search visibility — generative engines increasingly cite recognised people; structured identity makes you easier to attribute.
Key Properties of Person JSON-LD
Only name is strictly required, but a thin Person object does little. The properties that actually move the needle are:
| Property | What it does | Example |
|---|---|---|
| name | The person's full name (required). | Anil Varma |
| jobTitle | Their role — a core expertise signal. | Head of SEO |
| url | The canonical profile/author page for this person. | /about |
| image | A clear headshot, as an ImageObject. | /headshot.jpg |
| worksFor | Employer, as an Organization node. | SemlyPro |
| sameAs | Authoritative profile URLs that confirm identity. | LinkedIn, X, Wikipedia |
| knowsAbout | Topics of expertise that scope authority. | Technical SEO |
The sameAs Array Is the Most Important Field
If you only optimise one thing, optimise sameAs. It is an array of URLs pointing to other authoritative pages that represent the same person. Each link is a vote of identity: the more independent, high-trust profiles you connect, the more confident a search engine can be that this is a real, recognised individual.
Strong sameAs targets include:
- LinkedIn — the canonical professional identity for most people.
- X / Twitter — a public, verifiable handle.
- Wikipedia or Wikidata — gold-standard entity references when they exist.
- GitHub, ORCID, Google Scholar — credibility for developers, researchers, and academics.
- Crunchbase, company team pages, conference speaker bios — third-party corroboration.
Aim for at least three. One link is barely a signal; several consistent links across reputable domains build a robust entity.
How to Add Person Schema to Your Site
1. Generate the JSON-LD
Enter the name, job title, profile URL, headshot, employer, and your sameAs profiles into the generator above. It builds clean, valid JSON-LD on the fly and omits any field you leave blank, so the output never contains empty properties.
2. Paste the script tag into your page
Copy the ready-made <script type="application/ld+json"> snippet and place it in the <head> (or anywhere in the body) of the relevant author or About page. One Person block per page is the norm.
3. Validate it
Run the URL through Google's Rich Results Test and the Schema Markup Validator. Both should report a valid Person with no errors. Fix any flagged issues, then request indexing if it is a new or changed page.
4. Keep it consistent
Use the same name spelling, image, and profile URLs everywhere the person appears. Consistency across pages and across the sameAs targets is what turns scattered mentions into one confident entity.
Common Person Schema Mistakes
- Only a name — technically valid, practically useless. Add role, URL, image, and sameAs.
- No sameAs links — the single biggest missed opportunity for entity recognition.
- Inconsistent details — a different name or photo on each page fragments the entity.
- Fake or padded markup — never claim a job title, employer, or profiles that are not real; mismatches erode trust.
- Pointing url at the homepage — link to the actual author/profile page, not the site root.
Expert Tips
Lead with sameAs
Identity is everything. Link LinkedIn, X, Wikipedia, GitHub, or ORCID — the more independent, high-trust profiles you connect, the stronger the entity signal for E-E-A-T.
Always validate before you ship
Paste the snippet into your page, then run it through Google’s Rich Results Test and the Schema Markup Validator. Fix any errors and request re-indexing on changed pages.
Frequently Asked Questions
What is Person schema used for?
Person schema is JSON-LD structured data that describes an individual — their name, role, employer, photo, and verified profiles — so search engines can recognise them as a real, known entity. It is used on author bios, About pages, and team pages to support E-E-A-T and author trust.
Is Person schema required for SEO?
It is not required and is not a direct ranking factor, but it is strongly recommended. It is the clearest way to declare author identity and expertise, which supports E-E-A-T, entity recognition, and eligibility for richer author treatments in search and AI results.
What is the sameAs property in Person schema?
sameAs is an array of URLs pointing to other authoritative pages that represent the same person — for example LinkedIn, X, Wikipedia, or GitHub. It is the strongest signal that the person is real and recognised, so include three or more reputable links when you can.
Where should I put Person schema on my site?
Place it on pages that are genuinely about the person: author profile pages, the site's About page, and team pages. You can also reference a Person as the author within Article schema on blog posts. Use one Person block per page and keep the details consistent everywhere.