What Is WebPage Schema? The Complete Guide (2026)

Saar Twito8 min read
Saar Twito
Saar TwitoFounder & SEO Engineer

Hi, I'm Saar - a software engineer, SEO specialist, and lecturer who loves building tools and teaching tech.

View author profile →

What Is WebPage Schema?

WebPage schema is a type of structured data — defined in the Schema.org WebPage vocabulary — that describes a specific page on your website. Unlike content-focused schemas (Article, Product, Recipe), WebPage schema describes the page itself: its canonical URL, its language, what content it contains, and how it fits into the broader site structure. It is a foundational building block of the semantic web entity graph.

TL;DR

Greadme errors when url is missing or invalid on a WebPage schema. Key recommended properties are @id (for graph linking), isPartOf (linking to the WebSite schema), mainEntity (linking to the primary content entity), about (the topic of the page), name, description, inLanguage, and primaryImageOfPage. Use the most specific subtype — AboutPage, ContactPage, FAQPage, etc. — rather than the generic WebPage.

Why WebPage Schema Matters for SEO and AI Visibility

WebPage schema serves a different purpose from content schemas: it helps Google and AI systems build a machine-readable graph of your site's structure. When your WebPage schema correctly references your WebSite via isPartOf, and links to your primary content entity via mainEntity, you create a coherent knowledge graph that AI systems can traverse and cite.

Pages with well-structured entity graphs — WebSite → WebPage → Article/Product/etc. — give AI systems a coherent picture of your content, its context, and its authority. The WebPage schema is the glue that connects your page to the broader entity graph.

Valid WebPage Subtypes

Always use the most specific WebPage subtype that matches your content. Greadme recognizes the following valid subtypes:

SubtypeUse for
WebPageGeneric fallback when no more specific type fits
AboutPageAbout Us page describing your organization
CheckoutPageE-commerce checkout flow pages
CollectionPagePages listing collections of items (category pages, galleries)
ContactPageContact information pages
FAQPagePages with curated Q&A content (also activates FAQPage rich results)
ItemPagePages describing a single item (product detail pages)
MedicalWebPageHealthcare and medical information pages
ProfilePageUser profile pages on platforms
QAPageUser-submitted question and answer pages
RealEstateListingProperty listing pages
SearchResultsPageInternal site search results pages

Greadme Required Property

Schema.org does not define any required properties for WebPage. However, Greadme enforces one property as required because a WebPage schema without it is meaningless for entity graph linking:

PropertyGreadme rule
urlGreadme errors if missing or not a valid absolute URL (−20 pts). Must be the canonical URL of the page

Recommended Properties

PropertyNotes
@idA stable IRI for this page entity, typically the URL with a fragment (e.g., https://example.com/about#webpage). Used for graph linking. Greadme warns if missing
isPartOfLinks to your WebSite schema using {"@id": "https://example.com#website"}. Critical for entity graph coherence
mainEntityLinks to the primary content entity on the page (Article, Product, Person, etc.)
aboutLinks to the topic or subject this page is about — distinct from mainEntity, which links to the primary content entity. Both can be used together
nameThe page title. Typically matches the <title> tag content
descriptionPage summary. Typically matches the meta description
inLanguageBCP 47 language code (e.g., "en-US"). Helps answer engines understand content language
primaryImageOfPageA representative image for the page (ImageObject with url)
breadcrumbLinks to a BreadcrumbList using {"@id": "#breadcrumb"}

WebPage Schema Code Example

A complete WebPage schema for an About page, with full graph linking:

{
  "@context": "https://schema.org",
  "@type": "AboutPage",
  "@id": "https://example.com/about#webpage",
  "url": "https://example.com/about",
  "name": "About Us | Acme Corp",
  "description": "Learn about Acme Corp, our mission, and our team.",
  "inLanguage": "en-US",
  "isPartOf": {
    "@id": "https://example.com#website"
  },
  "mainEntity": {
    "@id": "https://example.com#organization"
  },
  "primaryImageOfPage": {
    "@type": "ImageObject",
    "url": "https://example.com/about-hero.jpg"
  }
}

Building the Entity Graph: WebSite → WebPage → Content

The most powerful use of WebPage schema is as a node in an entity graph. A complete graph linking chain looks like this:

  1. WebSite schema with @id: "https://example.com#website" — placed on the homepage, describes the overall site.
  2. WebPage schema with @id: "https://example.com/page#webpage" and isPartOf: {"@id": "https://example.com#website"} — links this page to the site.
  3. Content schema (Article, Product, etc.) with @id: "https://example.com/page#article" — linked from the WebPage via mainEntity.

When all three nodes are correctly linked via @id references, Google and AI systems can traverse the entire graph to understand context, authority, and content type simultaneously.

Common Mistakes to Avoid

  • Missing url: Greadme treats this as an error (−20 pts). A WebPage schema without a valid url is effectively useless for entity graph linking.
  • Using a relative URL: The url must be an absolute URL (starting with https://). Relative paths like /about cause an error.
  • Missing isPartOf: Without this link, the WebPage exists in isolation and provides no graph value. Greadme warns and deducts 8 points.
  • No mainEntity or about: Without linking to primary content, the WebPage schema describes a page but not what the page is about. Greadme warns and deducts 8 points.
  • Using a generic WebPage when a subtype fits: If your About page uses "@type": "WebPage" instead of "AboutPage", Greadme warns with a recommendation to use the more specific subtype.

How Greadme Validates WebPage Schema

Greadme checks both required and recommended WebPage properties. The score starts at 100 with the following key deductions:

IssuePoints lost
Missing url−20
Invalid url format−15
Missing @id−5
Missing isPartOf−8
Missing mainEntity and about−8
Missing name−5
Missing description−5
Missing inLanguage−5
Missing primaryImageOfPage or image−5
Case-sensitive property name error−8 per field

Frequently Asked Questions

Does every page on my site need WebPage schema?

It is not required, but it is beneficial for important pages — especially those you want to appear in AI answer responses. At minimum, add WebPage schema to your homepage (as WebPage or CollectionPage), About page (as AboutPage), Contact page (as ContactPage), and key content pages. You do not need to add it to every URL in a large e-commerce catalog.

What is the difference between WebPage schema and Article schema?

WebPage schema describes the page container — its URL, language, and site membership. Article schema describes the content published on that page — its headline, author, and publication date. The two are complementary: use WebPage schema with mainEntity pointing to the Article entity for the most complete structured data.

Can I use multiple @type values on a WebPage schema?

Yes. You can use an array like "@type": ["WebPage", "FAQPage"] to indicate that a page is both a generic web page and a FAQ page. However, using a single, most-specific subtype is generally cleaner and equally effective.