Classification: Optional · Last updated: April 2026

WebPage Schema for Shopify: The Complete Guide

WebPage schema is the most generic page-level structured data type. It describes a single web page — its name, URL, description, the website it belongs to, and the date it was last modified. While Google doesn't offer specific rich results for WebPage, it's a useful structural annotation that connects your pages to your broader site entity graph.

What Is WebPage Schema?

WebPage (schema.org/WebPage) is a JSON-LD structured data type that describes an individual web page. It's the base type for more specific page types like CollectionPage, FAQPage, AboutPage, ContactPage, and CheckoutPage. When no more specific type applies, WebPage is the general-purpose option.

Google processes WebPage markup as supplementary metadata. It helps Google understand page relationships (which site a page belongs to, when it was updated) but doesn't trigger any specific rich result feature.

Why WebPage Schema Is Optional

Google does not offer specific rich results for generic WebPage markup
Google already understands basic page metadata from your HTML — <title>, <meta description>, <link rel="canonical">
The information WebPage provides (URL, name, description) is largely redundant with what's already in your HTML
More specific schema types (Product, Article, CollectionPage) provide better signals for their respective page types

WebPage schema is most useful when combined with other structured data as part of an entity-linked graph. For example, an Article's mainEntityOfPage references a WebPage, creating a clean relationship between the content entity and the page entity.

WebPage Subtypes

schema.org defines several WebPage subtypes that you can use for more specific pages:

CollectionPage — Category or collection listing pages
FAQPage — Pages containing FAQ content
AboutPage — Your "About Us" page
ContactPage — Your "Contact Us" page
CheckoutPage — Your checkout page
SearchResultsPage — Your internal search results page
ItemPage — A page about a single item (can be used alongside Product)

Using the most specific subtype is always preferable to the generic WebPage when applicable.

Properties

@type — "WebPage" (or a specific subtype)
@id — Unique identifier for this page entity (typically the page URL with a fragment)
name — The page title
description — A brief description of the page content
url — The canonical URL of the page
isPartOf — Reference to your WebSite entity via @id
datePublished — When the page was first published
dateModified — When the page was last modified
breadcrumb — Reference to a BreadcrumbList for this page
inLanguage — The language of the page content

JSON-LD Example for Shopify

{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "@id": "https://yourstore.com/pages/about-us/#webpage",
  "name": "About Us",
  "description": "Learn about our story, our team, and our commitment to quality.",
  "url": "https://yourstore.com/pages/about-us",
  "isPartOf": {
    "@id": "https://yourstore.com/#website"
  },
  "dateModified": "2026-03-15",
  "inLanguage": "en-GB"
}

When WebPage Is Most Useful

WebPage schema adds the most value when:

Used as part of entity linking — other schema types reference the WebPage via mainEntityOfPage
Applied to pages that don't have a more specific type (About, Contact, static information pages)
Combined with BreadcrumbList references to create a navigational context
You're building a comprehensive entity graph and want every page to have a structured identity

How Schema Clinic Handles WebPage

Schema Clinic detects WebPage and its subtypes on all page types. It does not flag missing WebPage schema as an issue since it's classified as Optional. When present, the audit validates property correctness and checks that @id references are consistent with other schema blocks on the same page.

← Back to all guides