WebPage Schema – Individual Page Markup

Everything you need to know about WebPage schema markup. Learn how to describe individual pages on your website for better search engine understanding and enhanced results.

What is WebPage Schema?

WebPage schema describes individual pages on your website. While WebSite schema gives the big picture of your entire domain, WebPage schema zooms in on specific pages, telling search engines what each page is about and how it fits into your site structure.

Why WebPage Schema Matters

Most websites implement content-specific schemas (Article, Product, etc.) but forget the foundational WebPage markup. WebPage schema provides essential page-level context that helps search engines understand your content better.

The key insight: WebPage schema is the bridge between your site's overall structure (WebSite) and specific content (Article, Product, etc.). It provides the page-level context that makes your other schemas more effective.

What WebPage Schema Includes

•Basic page info: title, description, URL

•Content relationships: main entity, navigation

•Page type classification: about, contact, FAQ

•Site navigation: breadcrumbs, related pages

SEO Benefits You Get

📄Better page understanding by search engines

🔗Enhanced internal linking context

🎯Improved content categorization

📊Better featured snippet eligibility

JSON-LD Example

Complete WebPage schema for an article page:

{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "name": "Ultimate Guide to Schema Markup",
  "url": "https://yoursite.com/ultimate-guide-to-schema-markup",
  "description": "Comprehensive guide to implementing structured data markup for better SEO and rich search results",
  "inLanguage": "en",
  "isPartOf": {
    "@type": "WebSite",
    "@id": "https://yoursite.com/#website"
  },
  "mainEntity": {
    "@type": "Article",
    "@id": "https://yoursite.com/ultimate-guide-to-schema-markup#article"
  },
  "breadcrumb": {
    "@type": "BreadcrumbList",
    "itemListElement": [
      {
        "@type": "ListItem",
        "position": 1,
        "name": "Home",
        "item": "https://yoursite.com"
      },
      {
        "@type": "ListItem",
        "position": 2,
        "name": "Guides",
        "item": "https://yoursite.com/guides"
      },
      {
        "@type": "ListItem",
        "position": 3,
        "name": "Ultimate Guide to Schema Markup",
        "item": "https://yoursite.com/ultimate-guide-to-schema-markup"
      }
    ]
  },
  "datePublished": "2026-01-10",
  "dateModified": "2026-01-10"
}

Breaking Down the Example

Core Properties:

@type: Must be "WebPage"
name: Page title
url: Page URL
description: Page description

Relationship Properties:

isPartOf: Links to WebSite schema
mainEntity: Primary content on page
breadcrumb: Navigation structure
inLanguage: Page language

Practical Use Cases

📝 Article & Blog Pages

Every blog post and article page should have WebPage schema pointing to the Article schema as the main entity. This creates a clear content hierarchy.

Example: A blog post page uses WebPage schema to establish it's part of your site, with the Article as the main content.

Impact: Search engines understand the page structure and can better feature your content in rich results.

🏢 About & Company Pages

About pages, company information, and corporate pages use WebPage schema to establish page type and relationship to your organization.

Example: Your "About Us" page uses WebPage schema with breadcrumb navigation and links to Organization schema.

Impact: Better understanding of corporate pages and improved internal linking context for search engines.

📄 Service & Landing Pages

Service pages, product category pages, and landing pages benefit from WebPage schema to establish content relationships and navigation context.

Example: A service page uses WebPage schema with breadcrumbs showing the path from home to the specific service.

Impact: Improved crawling efficiency and better representation of your site's information architecture.

Common Mistakes & How to Avoid Them

❌ Missing isPartOf Relationship

Mistake: Using WebPage schema without linking it to your WebSite schema, creating disconnected page descriptions.

Fix: Always include "isPartOf" pointing to your WebSite schema. This establishes the page-site relationship that search engines need.

❌ Wrong Main Entity References

Mistake: mainEntity pointing to non-existent or incorrect schema IDs on the same page.

Fix: Ensure mainEntity @id matches the @id of your primary content schema (Article, Product, etc.) on that page.

⚠️ Over-complicating with Unnecessary Properties

Mistake: Adding every possible WebPage property even when not applicable or useful.

Fix: Focus on relevant properties: name, url, description, isPartOf, mainEntity, and breadcrumb. Don't add properties just because they're available.

⚠️ Inconsistent Page Descriptions

Mistake: WebPage description doesn't match the actual page content or meta description.

Fix: Use the same description as your meta description or page content. Schema should accurately reflect what users see.

SEO Tip: Foundation for Rich Results

WebPage schema creates the foundation that enables rich results. It provides the page-level context that makes your content schemas more effective.

Article Schema

Blog posts and news articles

Product Schema

E-commerce product pages

FAQPage Schema

Frequently asked questions

Validate Your WebPage Schema

Test your WebPage schema implementation to ensure proper page structure and relationship definitions.

Test with SchemaValidator

Our comprehensive validation tool

Google Rich Results Test

Official Google testing tool

Related Schema Types

WebPage schema connects to these schemas to create comprehensive page descriptions and content relationships.