ProfilePage schema

A WebPage representing a profile for a person or organization.

• The page is dedicated to one visible profile
• The mainEntity identifies the represented person or organization

• @id
• name
• url
• mainEntity
• isPartOf
• breadcrumb

{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "@id": "https://example.com/people/example/#webpage",
  "name": "Example Person",
  "url": "https://example.com/people/example/",
  "mainEntity": {
    "@id": "https://example.com/people/example/#person"
  }
}

• Selecting the type only because a search feature is desired.
• Publishing facts that are not visible or supported by the site.
• Creating conflicting copies of the same entity instead of using a stable @id.
• Failing to update markup when the visible page or source data changes.

Schema.org defines the vocabulary. Search platforms publish separate documentation for the structured-data features they currently support.

Use ProfilePage only when the page visibly represents the corresponding entity or relationship. Begin with the page purpose and the entity graph, then select the most specific supported type. Do not let the available vocabulary dictate claims the page does not make.

• Syntax validation, type/property validation, consumer testing, and post-deployment inspection.
• Record the page template, generator, source fields, responsible owner, and release reference.
• Avoid publishing properties that are unsupported, hidden, stale, or inconsistent with visible content.
• Parse the deployed json-ld, validate the graph, compare it with visible content, and test any target consumer requirements.
• Schedule review when visible content, offers, ownership, locations, products, or consumer documentation changes.