People & Org · High

Person schema — what it does & how to ship it

Short answer

Person marks up an author or public figure with name, image, jobTitle, sameAs and alumniOf — the primary E-E-A-T signal Google uses to attribute expertise to an author.

What it does

Person carries name, url, image, jobTitle, description, sameAs (LinkedIn, Twitter, GitHub), worksFor, alumniOf and knowsAbout. It's what makes an author eligible for an author Knowledge Panel.

SERP / AI benefit

E-E-A-T (Experience/Expertise/Authoritativeness/Trust) signal, author Knowledge Panel eligibility, and increased citation weight in LLM answers on the author's domain of expertise.

Where to use it

About page, author byline pages, contributor pages, team pages.

JSON-LD example

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Usman Jatoi",
  "url": "https://wbpomniseo.com/about",
  "jobTitle": "Founder, WBP Omni SEO Pro",
  "sameAs": ["https://www.linkedin.com/in/usmanjatoi", "https://twitter.com/usmanjatoi"],
  "knowsAbout": ["SEO", "GEO", "AEO", "WordPress"]
}

Copy, edit for your site, and drop into your page head inside a<script type="application/ld+json">block. Validate with Google's Rich Results Test.

In WBP Omni SEO Pro

Full Person schema live on /about (Usman Jatoi) with credentials, alumniOf, knowsAbout and every relevant sameAs link.

Ship Person without touching code

Frequently asked

Person vs ProfilePage?›

Person is the author entity; ProfilePage marks the page itself as a profile page. Use them together on your /about.

How does Person help with E-E-A-T?›

It gives Google a structured way to attribute expertise to a real human, which is the core of the E in E-E-A-T.

Should every blog author have Person schema?›

Yes — link the Article.author to a Person node with a real URL, not just a name string.