schema.org/WebPageNo rich result

WebPage schema

A single page. Carries the page-level metadata that is not specific to a content type.

Where to use it

Any page that is not better described by a more specific type.

A complete example

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

web-page.json

{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "@id": "https://www.seoforsolos.com/#webpage",
  "url": "https://www.seoforsolos.com/example",
  "name": "Acme Reference",
  "description": "A one sentence description that restates its own subject.",
  "isPartOf": {
    "@id": "https://www.seoforsolos.com/#website"
  },
  "breadcrumb": {
    "@id": "https://www.seoforsolos.com/example#breadcrumb"
  },
  "datePublished": "2026-07-27T00:00:00.000Z",
  "dateModified": "2026-07-27T00:00:00.000Z",
  "speakable": {
    "@type": "SpeakableSpecification",
    "cssSelector": [
      ".answer"
    ]
  }
}

Properties

WebPage properties
Property	Status
`url`	Required
`name`	Required
`description`	Recommended
`isPartOf`	Recommended
`breadcrumb`	Recommended
`datePublished`	Recommended
`dateModified`	Recommended
`speakable`	Recommended

The three mistakes this type attracts

01Using WebPage where Article or Product is more specific.
02Setting dateModified to the build time rather than the content's real edit date.
03Omitting isPartOf, which orphans the page from the site entity.

Related types

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

Questions

What is the WebPage schema type for?

A single page. Carries the page-level metadata that is not specific to a content type. Use it on: any page that is not better described by a more specific type.

Which WebPage properties are required?

WebPage requires 2 properties: url, name. It also recommends 6: description, isPartOf, breadcrumb, datePublished, dateModified, speakable.

Does WebPage produce a rich result?

WebPage does not produce a Google rich result. It is still worth shipping, because its value is entity resolution and answer extraction rather than search result presentation.

What is the most common WebPage mistake?

The most common WebPage mistake is: Using WebPage where Article or Product is more specific.