Person schema

Where to use it

Author bylines, about pages, team pages.

A complete example

Valid as written, with every required property and the recommended ones that carry real information.

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Acme Reference",
  "url": "https://www.seoforsolos.com/example",
  "jobTitle": "Engineer",
  "description": "A one sentence description that restates its own subject.",
  "image": "https://www.seoforsolos.com/opengraph-image",
  "sameAs": [
    "https://www.seoforsolos.com"
  ],
  "worksFor": {
    "@id": "https://www.seoforsolos.com/#organization"
  }
}

Generate a Person node with your own values in the schema generator, and lint what your page actually ships with the schema validator.

Properties

The three mistakes this type attracts

1. 01Inventing credentials, a headshot or social profiles.
2. 02A bare string byline where a Person node with a URL would resolve.
3. 03Reusing one Person @id for several different people.

Related types

• WebPage
• BreadcrumbList
• ItemList
• CollectionPage
• SiteNavigationElement
• Article

Where this appears in the playbook

• Structured data: what each type is for and which ones earned their place.
• The schema graph: composing types into one graph with stable identifiers.
• One JSON-LD script per page, holding one @graph
• Stable @id anchors that cross-reference rather than duplicate
• Optional fields are omitted, never emitted as empty strings
• Does schema markup work? What 42 types on one site actually did: which of these types measurably did anything in production.