Person schema is structured data that tells search engines who a person is, what they do, and where else they appear online. Adding it to an author or about page helps Google connect your content to a real entity, which supports E-E-A-T and your place in the knowledge graph. Here is what to include and how to generate it.
What Person schema describes
Person JSON-LD captures the core facts about an individual in a format search engines can read directly. The fields that matter most are:
- name: the person’s full name.
- url: their canonical profile or about page.
- image: a headshot or avatar URL.
- jobTitle: their role, like “Editor” or “Lead Developer.”
- worksFor: the Organization they belong to, nested as its own object.
- sameAs: an array of links to official profiles, such as LinkedIn, X, GitHub, or a personal site.
The sameAs array is the part that does the heavy lifting for entity building. Each link is a vote that ties your author to a known identity across the web.
Why it matters for E-E-A-T
Google rewards content that demonstrates experience, expertise, authoritativeness, and trust. Person schema makes the author behind that content machine-readable. When you mark up an author page and reference the same person in your article markup, you give search engines a consistent entity to attach reputation to. Over time that entity can earn a knowledge panel and stronger trust signals for everything that person writes.
Generate Person schema in four steps
- Open the Person Schema Generator and enter the person’s name and profile URL.
- Add the jobTitle and the worksFor organization name and URL.
- Paste each official profile link into the sameAs list, one per line.
- Copy the generated JSON-LD and drop it into a
<script type="application/ld+json">block in the page head.
Everything runs in your browser, so the names and links you enter never leave your device.
Tie it to your article author field
Person schema is most powerful when it lines up with your article markup. Use the same name and URL in your Article schema’s author field that you used in the standalone Person object. That consistency tells search engines the byline, the about page, and the linked profiles all describe one entity. Once your markup is live, run it through Google’s Rich Results Test to confirm there are no errors before you ship it sitewide. Generate the markup once with the Person Schema Generator, then reuse it across every page that person owns.
Related tools
- Article Schema Generator: mark up the articles your person authors and reuse the same author identity.
- FAQ Schema Generator: add FAQ structured data to the same pages for richer search results.
- Favicon Checker: confirm your brand icon is set so your entity looks complete in search.
Fill in the name, role, and profile links, copy the JSON-LD, and give Google a real person to trust.