Home › Generators › WebPage Schema Generator
Free tool · No signup required

WebPage Schema
Generator

Generate valid WebPage JSON-LD structured data. Help Google understand your page type, author, content dates, and breadcrumb trail for any page on your site.

✓
Google-approved format
⚡
Instant output
🔒
No data stored
∞
Unlimited use
Page details Step 1 of 2
Core information
The main representative image for this page
IETF language tag for the page's primary language
Dates (recommended)
When this page was first published
When this page was last significantly updated
Author (optional)
Profile photo recommended for person type
Publisher (optional)
Minimum 112×112px, square PNG or SVG preferred
Additional details (optional)
Comma-separated keywords describing the page topic
ISO 8601 duration: PT5M = 5 minutes, PT1H = 1 hour
If different from the page URL above
Breadcrumb trail (optional: adds BreadcrumbList to the output)

Add the breadcrumb path from home to this page. Each item needs a name and URL.

Paste output into your page <head>
JSON-LD Output · Ready to paste 

  







  
How to use

  

    
01
Enter page details
Fill in your page title, URL, type, dates, author, and publisher above.

    
02
Generate the code
Click "Generate Schema" to produce valid JSON-LD markup instantly.

    
03
Paste in <head>
Copy and paste the output inside the <head> tag of the specific page it describes.

    
04
Validate & publish
Test with Google's Rich Results Test or Schema.org Validator, then publish.

  







  
What is WebPage Schema Markup?

  
WebPage schema is JSON-LD structured data that describes a specific page on your website, its type, title, author, publication date, and how it fits into your site's structure. Unlike schema types that generate specific visually rich results (stars, event cards, recipe thumbnails), webpage schema works primarily as a contextual signal that helps Google better understand and categorise the content of individual pages.

  
It's particularly valuable when combined with a BreadcrumbList, which this generator also produces, telling Google exactly where a page sits in your site hierarchy. Breadcrumb trails are one of the most consistently visible rich results in Google, appearing directly in search listings as navigational links.


  
When should I use WebPage schema?

  
Use WebPage schema on pages that don't have a more specific schema type available, for example, a landing page, an About page, a Contact page, a category page, or a pillar content page. If your page is primarily a blog post, use article schema instead. If it's a product, use the product schema. webpage is the right choice when no more specific type applies.


  
What's the difference between WebPage and WebSite schema?

  
WebSite schema describes your entire website as an entity (homepage only) and enables features like the Sitelinks Search Box. WebPage schema describes a single, specific page within that site. Most sites benefit from having WebSite schema on the homepage and WebPage schema on key inner pages.


  

    One schema per page. WebPage schema should only appear once per page, describing that page specifically. Don't add the same generic webPage schema across your entire site each instance should be unique to the page it describes.
  







  
How to Validate WebPage Schema Markup

  
After generating your schema, always validate before publishing. Follow these 4 steps:

  

    

      
1

      
Generate your schema

      
Fill in your page details above, click Generate Schema, and copy the output.

    

    

      
2

      
Open Schema Markup Validator

      
Go to Schema Markup Validator and click the "Validate" tab.

    

    

      
3

      
Paste & run the test

      
Paste your JSON-LD and run the test. Google confirms whether your schema is valid and well-structured.

    

    

      
4

      
Fix errors & publish

      
Fix any errors, re-test, then paste into your page's <head> tag and publish.

    

  







  
Common WebPage Schema Mistakes to Avoid

  

    

      
❌ Same schema on every page

      
Each webPage schema instance should be unique and specific to the page it describes. Don't inject a single generic template across your whole site; the URL, title, and dates must match the actual page.

    

    

      
❌ Wrong page type

      
If a more specific schema type exists for your page (Article, Product, Recipe, Event, FAQ), use that instead of WebPage. WebPage is a fallback for pages that don't have a more specific type available.

    

    

      
❌ Stale date modified

      
If you include dateModified, keep it accurate. Google uses this date to assess content freshness. An outdated modification date on a page you've recently updated sends the wrong freshness signal to Google.

    

    

      
❌ Wrong breadcrumb order

      
Breadcrumb items must be listed in order from home to the current page, with correct position numbers. A reversed or non-sequential breadcrumb list will fail validation and won't display correctly in Google results.

    

    

      
❌ Missing publisher for editorial pages

      
For any page with authored content, always include a publisher organisation. Google uses publisher information to assess the credibility and authority of content, particularly for EEAT signals.

    

    

      
❌ URL doesn't match the page

      
The URL in your schema must exactly match the canonical URL of the page where the schema is placed. Using a wrong, redirected, or non-canonical URL in the schema undermines its effectiveness entirely.

    

  







  
Frequently Asked Questions about WebPage Schema

  

    

      
      
WebPage schema itself doesn't generate a specific visually rich result like recipe cards or star ratings. Its primary value is as a contextual entity signal — telling Google the page type, author, and dates. However, the BreadcrumbList this tool generates alongside it does produce visible breadcrumbs in Google search results, which is one of the most consistently shown rich result types.

    

    

      
      
Not necessarily, but it's a good practice for important pages. Focus first on pages that have unique author, date, and publisher information to include or pages where breadcrumb visibility in search would be valuable. Each schema instance must be unique to its page, so avoid mass-injecting a single generic template across your site.

    

    

      
      
Technically yes, Article is a subtype of a WebPage in Schema.org. However, in practice, it's redundant to include both. If your page is a blog post or article, use article schema (which inherits all WebPage properties). If it's not an article, use WebPage. There's no benefit to including both separately.

    

    

      
      
The speakable property marks sections of a page as suitable for text-to-speech (e.g., for Google Assistant). It's currently a beta feature with limited widespread impact and is primarily used by news publishers for Google News audio. For most websites it's not a priority; we've omitted it from this generator to keep it focused on the most impactful properties.

    

  







  
Related Schema Generators

  
Other free structured data tools you might need

  

    
      
🌐

      
Website Schema
Site name, sitelinks & search box

      →
    
    
      
🔗

      
Breadcrumb Schema
Show site path in Google results

      →
    
    
      
📝

      
Article Schema
Author & date metadata for blogs

      →
    
    
      
🏛️

      
Organization Schema
Brand entity & Knowledge Panel

      →
    
    
      
❓

      
FAQ Schema
Q&A rich results in Google Search

      →
    
    
      
⭐

      
Review Schema
Star ratings for products & services

      →