Person Structured Data: Fields and Validation

Person markup describes person entity grounding in the pinned Atlas registry. Its recorded status is limited, which is a documentation and validation boundary rather than a promise of a particular search presentation.

Use Person schema only when the visible page actually contains and owns the entity or content being described. The reviewed page contexts are about, profile, article, blog, other. A type can be valid vocabulary while remaining irrelevant, ineligible, misleading, or unsupported for a specific page.

Structured data should make an existing page easier to interpret. It should not introduce hidden reviews, ratings, products, people, events, jobs, services, questions, steps, or other facts that users cannot verify in the visible content.

The Atlas record lists these required fields for Person: name. Required means the registry expects the property for the reviewed feature or vocabulary contract; it does not override stricter current documentation or page-specific policy.

Recommended fields are jobTitle, sameAs, url. Add them only when the page owns accurate values. Visibility requirements are name, and the broader rule remains that material structured claims must match visible content.

• Confirm the page purpose is one of the reviewed contexts: about, profile, article, blog, other.
• Inventory the required properties: name.
• Compare visibility requirements with the page: name.

Implement Person schema from the same content record that renders the page whenever possible. That ownership prevents a detached JSON-LD template from retaining an old title, entity, price, date, author, rating, location, or availability after visible content changes.

Use stable canonical identifiers for recurring entities, absolute URLs for public references, and correctly shaped values for dates, numbers, lists, and nested objects. Keep route-specific markup out of global shells that can duplicate it across unrelated pages.

• Add page-owned values for the required Person properties before optional enrichment.
• Review recommended properties without inventing absent facts: jobTitle, sameAs, url.
• Keep JSON-LD values consistent with the visible page and the current primary documentation.

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Visible name value",
  "jobTitle": "Visible jobTitle value",
  "sameAs": "https://example.com/"
}

Validate Person schema in the final deployed HTML. First parse the JSON, then check Schema.org vocabulary shape, then review feature-specific required properties and policy, and finally compare every material value with what a user can see on the canonical page.

The source record was reviewed on 2026-06-23. Recheck the primary documentation before a release when the feature, status, or Search presentation could have changed since that date.

• Parse the final deployed JSON-LD rather than a detached editor snippet.
• Review the Person record against its official documentation and Atlas status limited.
• Check that no hidden, misleading, expired, or unsupported values survive the render path.

A parser success does not establish feature eligibility or rich-result selection.

Person can be valid Schema.org vocabulary while having limited or no special Google Search presentation.

Do not mark a reference page like this one as Person merely because it discusses the type. This page is an Article about Person schema; its JSON-LD must describe the visible article, not impersonate the subject of the guide.

Claim boundary: Person has a limited or vocabulary-level role in this registry. Valid markup does not establish a special Google Search presentation.

1. Person structured data documentationSchema.org / checked 2026-06-23

   Primary documentation referenced by the Atlas Person registry record.