Person schema markup (schema.org/Person) is structured data that describes a specific individual rather than a business. It is most useful on author bio pages, personal portfolio sites, and speaker or consultant profiles where you want search engines and AI systems to associate content with a named human being. If you publish content under your own name — or if clients search your name directly — this is one of the higher-value schema types you can implement.

I use Person schema on my own site and recommend it to every consultant, author, or subject-matter expert I work with. The reason is straightforward: Google's systems need to connect your name across multiple platforms — your website, LinkedIn, podcast appearances, guest posts, conference bios — into a single coherent entity. Person markup gives them the explicit map to do that.

What Person Schema Markup Does for Your Presence

A well-formed Person entity helps Google build a knowledge graph node for you as an individual. This matters in a few concrete ways. First, it increases the probability of a Knowledge Panel appearing in branded searches for your name. Second, it strengthens E-E-A-T signals: when Google can confirm that the person writing about a topic has verifiable credentials and a consistent online presence, it weighs that content differently than anonymous prose.

Third — and increasingly important — AI Overviews and LLM-based retrieval systems use structured data as a reliable input when generating answers about people. If someone asks an AI search tool "Who is [your name]?" or "Is [your name] an expert in X?", a clean Person entity is the most reliable way to ensure the answer is accurate and comes from your own data rather than aggregated web text that may be outdated or wrong.

Person schema is not a direct ranking factor. Like all structured data, it helps machines understand who is behind the content — which feeds confidence scoring, entity disambiguation, and rich result eligibility rather than directly moving keyword rankings.

Required and Recommended Properties

Schema.org defines a rich set of properties for the Person type. These are the ones that actually matter for search and AI use cases:

  • @type — Person
  • name — full name exactly as it consistently appears across all your profiles; inconsistency here creates disambiguation problems
  • jobTitle — your primary professional role; be specific ("SEO Consultant and Schema Markup Specialist" is more useful than "Consultant")
  • image — an ImageObject with your professional headshot URL; Google uses this in Knowledge Panels
  • url — the canonical URL of the page that describes you (usually your About page or homepage)
  • sameAs — links to LinkedIn, Twitter/X, Wikipedia, Wikidata, or other authoritative profile pages; this is the cross-platform identity anchor
  • worksFor — an Organization entity identifying your employer or firm
  • knowsAbout — array of topic strings or linked concepts representing your areas of expertise
  • alumniOf — educational institutions attended, if they are relevant to establishing your credentials in the field
  • award — industry awards or recognitions; useful for establishing authority in competitive niches
  • description — a concise bio matching the visible page copy

The sameAs Property: Why It Is the Most Important Field

Of all the Person properties, sameAs has the highest leverage. Without it, Google sees a name on a page but cannot confirm it is the same person mentioned on LinkedIn, cited in a podcast transcript, or referenced in a conference speaker bio. With it, Google can merge those disparate mentions into one entity node — which is what drives Knowledge Panel generation.

The most authoritative sameAs targets, roughly in order of weight: Wikipedia (if you have an article), Wikidata, LinkedIn, a verified Twitter/X profile, an About.me page, Crunchbase (for business figures), and IMDb (for media figures). You do not need all of them — two or three authoritative ones matter more than a long list of thin social accounts.

JSON-LD Example for Person Schema Markup

Place this in the <head> of your About page or personal homepage. JSON-LD is the format Google recommends; it does not require modifying visible HTML and is straightforward to maintain.

<script type='application/ld+json'>
{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Terry Samuels",
  "jobTitle": "SEO Consultant and Schema Markup Specialist",
  "description": "14-year SEO practitioner focused on technical SEO, structured data strategy, and schema markup implementation for businesses and agencies.",
  "url": "https://www.terrysamuels.com",
  "image": {
    "@type": "ImageObject",
    "url": "https://www.terrysamuels.com/images/terry-samuels.jpg",
    "width": 400,
    "height": 400
  },
  "worksFor": {
    "@type": "Organization",
    "name": "Salterra Digital Services",
    "url": "https://www.salterra.com"
  },
  "knowsAbout": [
    "SEO",
    "Schema Markup",
    "Technical SEO",
    "Structured Data",
    "JSON-LD",
    "Knowledge Graph Optimization"
  ],
  "sameAs": [
    "https://www.linkedin.com/in/terrysamuels",
    "https://twitter.com/terrysamuels",
    "https://www.crunchbase.com/person/terry-samuels"
  ]
}
</script>

How to Add Person Schema in WordPress

For a personal site or author-focused blog, the cleanest approach in WordPress is a custom JSON-LD snippet added via the wp_head action, firing on your About page only using is_page() with the page slug. This keeps the markup off internal pages and posts where it does not belong.

Yoast SEO handles basic Person schema through its Knowledge Graph settings — set your site type to "Person" and fill in the person name and social profiles. The limitation is that Yoast's Person output omits knowsAbout, description, and award fields. For a consultant or expert site where entity depth matters, I typically add a supplemental custom block rather than relying on the plugin output alone. The guide on adding schema markup covers both paths in detail.

How to Test Person Schema Markup

After implementing, run both validation tools:

  • Google Rich Results Test — paste your About page URL or the raw JSON-LD; it shows whether Google can parse the entity and flags errors that would prevent Knowledge Panel consideration
  • Schema Markup Validator at validator.schema.org — checks the markup against the schema.org vocabulary and catches property mismatches or missing recommended fields

Also check Google Search Console under Enhancements after the page is indexed. Broken image URLs and dead sameAs links are the most common silent failures — they do not always surface as errors in the Rich Results Test but do prevent Google from building a complete entity profile. See my dedicated guide on how to test schema markup for a full walkthrough.

Person Schema and the E-E-A-T Connection

E-E-A-T — Experience, Expertise, Authoritativeness, and Trustworthiness — is a quality framework Google uses in its Search Quality Rater Guidelines. Person schema does not directly set an E-E-A-T score (no such score exists as a signal), but it contributes to the evidence Google uses to evaluate authoritativeness and trustworthiness for YMYL topics.

When a named author's Person entity is structured, cross-referenced via sameAs, and connected to an organization via worksFor, Google has a stronger basis for associating that person's expertise with the content they publish. This is most important for health, finance, legal, and other high-stakes topics where content provenance matters to ranking. For a schema consultant publishing on technical SEO, it reinforces the authority signal that the content comes from someone with a verifiable track record.

Common Person Schema Mistakes

  • Adding the Person block on every page of the site rather than once on the dedicated About or author bio page. Repetition does not reinforce the signal; it introduces ambiguity about the canonical location of the entity definition.
  • Omitting sameAs entirely. Without cross-platform links, Google cannot confirm the entity and the Knowledge Panel probability drops significantly.
  • Using a headshot URL that returns a 404 after a site redesign. Broken image URLs in structured data are a quiet, easily missed failure mode — add a monitoring check for this.
  • Claiming credentials in knowsAbout or jobTitle that are not supported by visible page content. This is a direct violation of Google's structured data quality guidelines and can trigger a manual action for misrepresentation.
  • Using inconsistent name formats across properties and platforms. If your LinkedIn says "Terry Samuels" but the schema says "T. Samuels," the disambiguation confidence drops.

Getting your Person entity right is foundational work before layering on content-type markup like Article schema or broader structured data for SEO. It also connects directly to Organization schema markup through the worksFor relationship — implement both and they reinforce each other. If you want help auditing or implementing your entity setup, schema markup consulting is where I can take a look at what you have and what is missing.