WebPage is the Schema.org type for a single page. It has subtypes for common page kinds: AboutPage, ContactPage, CollectionPage, ItemPage, FAQPage, QAPage, ProfilePage, SearchResultsPage and more. Google does not use plain WebPage for a rich result, but WebPage markup is widely used by SEO plugins to tie the page to its website, breadcrumb and main entity.
Useful properties
The properties that matter most describe relationships. isPartOf points to the WebSite. mainEntity names the thing the page is mostly about, such as an Article or a SoftwareApplication. breadcrumb points to the BreadcrumbList. datePublished and dateModified describe the page itself, and primaryImageOfPage names its lead image.
Subtypes and their weight
Some subtypes matter for Google features. FAQPage, QAPage and ProfilePage have their own documentation and requirements. Others, such as AboutPage or CollectionPage, have no Google feature and simply describe the page more precisely. Using a subtype that does not fit the page, such as FAQPage on a page with one question, is a common error.
Is it worth adding?
If your CMS or plugin already outputs it, keep it accurate. If you are hand-building markup, prioritize types with clear uses (Organization, Article, BreadcrumbList, product types) and add WebPage as the connecting node when you build a full graph. There is no documented Google benefit from WebPage markup alone.
Example
Connecting a product page
A CRM vendor, Ashgrove Lane, marks its product page as a WebPage that isPartOf its WebSite, with mainEntity pointing to a SoftwareApplication node and breadcrumb pointing to a BreadcrumbList. Each node has its own @id, so a validator shows one clear tree.
Common mistakes
Choosing subtypes for hoped-for features
Labeling pages FAQPage or QAPage when they are not changes nothing useful and can breach Google's guidelines for those types.
Questions
No. It is optional. It helps connect other entities but has no Google rich result of its own.
Sources
