WebPage and AboutPage JSON-LD Template

What this describes

Use WebPage for an individual page and a more specific subtype when the page clearly has that role. The example uses AboutPage and identifies the organization that the page is primarily about. For an ordinary page, change @type to WebPage and remove about when no single entity is the subject.

Copyable template

{
  "@context": "https://schema.org",
  "@type": "AboutPage",
  "@id": "https://www.example.com/about/#webpage",
  "url": "https://www.example.com/about/",
  "name": "About Example Organization",
  "description": "A description that matches the page.",
  "inLanguage": "en-US",
  "isPartOf": {
    "@id": "https://www.example.com/#website"
  },
  "about": {
    "@id": "https://www.example.com/#organization"
  },
  "breadcrumb": {
    "@id": "https://www.example.com/about/#breadcrumb"
  }
}

Customize it

• Select the most accurate page subtype, such as ContactPage, CollectionPage, ItemPage, or ProfilePage.
• Keep the page @id distinct from the entity described by the page.
• Match url, name, description, and language to the canonical visible page.
• Remove any reference whose target entity is not defined.
• Use mainEntity when a page’s primary subject is better expressed that way; do not add both properties without a clear reason.

Validate it

Use the live-page JSON-LD validation tutorial and test the rendered page with Schema.org Validator. Confirm that the subtype matches the page’s visible purpose and that every referenced @id is defined consistently. Supply the referenced WebSite, Organization, and BreadcrumbList in a graph the intended consumer can receive; do not assume it resolves a remote identifier.

Official references

• Schema.org: WebPage
• Schema.org: AboutPage