WebPage Schema Markup
WebPage is a generic type for individual web pages. While most pages don't need explicit WebPage markup (Google infers it), it can be useful for specifying page-level metadata like last reviewed date or primary topic.
Google Search Features
- Speakable Sections of an article that Google can read aloud on Google Home devices. Beta. Only for English content and Google Home users in the U.S.
- Subscription and paywalled content Tells Google which content is behind a paywall, so it isn't treated as cloaking.
When to Use WebPage
Properties
| Property | Type | Status | Description |
|---|---|---|---|
| name | Text | recommended | Page title. |
| url | URL | recommended | Canonical URL. |
| description | Text | optional | Page description. |
| lastReviewed | Date | optional | When the page was last reviewed for accuracy. |
| mainEntity | Thing | optional | The primary entity described by this page. |
| breadcrumb | BreadcrumbList | optional | Page breadcrumb navigation. |
| speakable | SpeakableSpecification | optional | Sections suitable for text-to-speech. |
JSON-LD Examples
About Page
A simple about page.
{
"@context": "https://schema.org",
"@type": "WebPage",
"name": "About Us",
"url": "https://example.com/about",
"description": "Learn about our company and mission.",
"lastReviewed": "2024-03-01"
}Common Mistakes
Adding WebPage markup unnecessarily — Google infers it automatically for most pages.
Complete Guide to WebPage Schema Markup
WebPage describes a single page, as opposed to the thing the page is about. Google treats every URL as a web page whether or not it's marked up, so a bare WebPage adds little. It earns its place when it carries page-level facts that nothing else in the markup can hold, and when it connects the page's other objects.
The properties that do that are few. breadcrumb holds the page's BreadcrumbList, mainEntity names the primary thing the page describes (an Article, a Product, a Person), isPartOf links the page to the site's WebSite, and lastReviewed and reviewedBy record when and by whom the content was checked, which matters for medical or legal pages. This site's own pages work that way: each type reference page, including this one, has a WebPage with its breadcrumb nested inside and isPartOf pointing at the site's WebSite by @id.
Two Google features use WebPage markup directly. Subscription and paywalled content requires isAccessibleForFree, set to false for a paywalled page, with hasPart marking the paywalled sections by CSS selector, so Google can tell a paywall from cloaking. Speakable marks the parts of a page suited to text-to-speech; it's a beta feature, only for English content and Google Home devices in the U.S.
For most pages, a more specific subtype says more. schema.org defines eleven, including AboutPage, ContactPage, CollectionPage, ItemPage, ProfilePage, QAPage, FAQPage, SearchResultsPage and MedicalWebPage. Google reads ProfilePage and QAPage for their own features; FAQPage no longer earns a rich result.
The common mistake is describing the same page twice: a WebPage with one name and URL in one block and a subtype with another in a second. Use one page object per URL, with the most specific type that fits, and put the page's subject in mainEntity rather than in the page itself.
Related Types
Check Your WebPage Markup
The generator doesn't have a WebPage form yet. Paste your markup into the validator to check its types, properties and values, and what Google needs from it.
Open Validator