Technical SEOPublished26.05.2026

WebPage schema

WebPage is a base Schema.org type for describing web pages. It includes common properties: name, description, author, date modified. Used as the base for more specific types: Article, FAQPage, ItemPage.

In brief

WebPage schema is a Schema.org markup type for web pages that describes basic document properties: name, description, URL, author, creation and modification dates. It is the parent type for ArticlePage, ContactPage, FAQPage, and other specialized types.

What is WebPage schema

WebPage is a base Schema.org markup type for describing web pages. It is the parent class for most specialized page types and contains common properties characteristic of any web page.

WebPage markup helps Google understand the page context: what kind of document it is, who its author is, when it was created and updated, and what its topic is. This improves crawler processing and can influence how the page appears in search results.

WebPage is not the most common type for direct use. More often its subtypes are used (Article, FAQPage, ItemPage), which automatically inherit WebPage's properties.

WebPage subtypes

ArticlePage: A page with an article or news piece. Commonly used for blogs.
FAQPage: A page with questions and answers. Enables FAQ rich results in search.
ItemPage: A page describing a specific item — used in catalogs and marketplaces.
ContactPage: A page with company contact information.
AboutPage: An 'About Us' or 'About the Company' page.
CheckoutPage: An order checkout page in an online store.
SearchResultsPage: A site search results page.

Key WebPage schema properties

name: Page title. Usually matches the title tag.
description: Brief description of the page. Can match the meta description.
url: Canonical URL of the page.
author: Content author — a Person or Organization object.
datePublished: Publication date in ISO 8601 format.
dateModified: Date of last modification. Helps Google understand content freshness.
inLanguage: Page language in BCP 47 format (e.g., 'en', 'de').
breadcrumb: Breadcrumb navigation — a nested BreadcrumbList object.

When to use WebPage schema

For pages that don't fit any specialized subtype (Article, Product, FAQPage, etc.)
As a base markup for the entire site when subtypes aren't implemented
In combination with other types: WebPage + BreadcrumbList, WebPage + Organization
For 'About' and 'Contact' pages — using AboutPage and ContactPage respectively
For site search pages — SearchResultsPage

Basic WebPage markup example

Minimal WebPage JSON-LD example: { "@context": "https://schema.org", "@type": "WebPage", "name": "Page Title", "description": "Page description", "url": "https://example.com/page", "dateModified": "2026-05-26", "inLanguage": "en" }. For most pages, it's recommended to use a more specific subtype.

FAQ

Common questions

The base WebPage type itself does not produce specific rich results. But its subtypes (FAQPage, Article, BreadcrumbList) do. Use the most appropriate subtype instead of the base WebPage.

Not required, but recommended for important pages. Markup helps Google better understand page structure and context. For CMS platforms, plugins often add it automatically.

Yes. WebPage is often combined with Organization (for an 'About' page), BreadcrumbList (breadcrumbs), Person (author). Use the 'isPartOf' property to link the page to the site via WebSite schema.

WebSite describes the entire site as a resource (name, URL, site search). WebPage describes a specific page. Both can coexist: WebPage links to WebSite through the 'isPartOf' property.

Direct contacts

Discuss your project?

Share your goals and website context — I will suggest a practical next step.

[email protected]@pavelbarushka LinkedIn