Paste your page URL. We'll read meta tags + favicon for publisher logo + author meta.
Basic page details
0/160 characters
Publisher / organization (optional)
Author (optional)
Breadcrumb (optional, 3 levels)
1
2
3
Item URLs auto-generated: level 1 → origin, level N → page URL, middle levels emitted name-only.
Required: Page title is required · Page URL is required
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebPage",
"breadcrumb": {
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "/"
}
]
}
}
</script>How to use
01
Pick the page type and auto-fill
Choose one of ten types from the Page type dropdown, then paste a live URL and click Auto-fill from URL. It fetches the title, description, dates, author meta, and the favicon for the logo field.
02
Complete the basics and watch the counter
Fill Page title and Page URL, both required, plus the image and date fields. The Description box shows a live character count and warns past 160, where search snippets often get cut off.
03
Attach publisher, author, and breadcrumb
Add an Organization with a logo URL, choose Person or Organization for the author, and fill up to three breadcrumb levels. Item URLs are composed from your page URL automatically. Copy script when done.
Why WebPage Schema Generator
- Generic WebPage schema with publisher + author + inline breadcrumb in one tool.
- 10 WebPage subtypes including AboutPage, FAQPage, ProductPage, CheckoutPage.
- Auto-fill from URL, pulls title, description, dates, publisher logo, and author meta.
Common questions
When is plain WebPage schema actually worth adding?
When no specific type applies and the page still has metadata worth declaring: a publisher, an author, dates, and a position in your hierarchy. Pricing pages, landing pages, and legal pages are typical cases. If Article, Product, or Event fits, use that instead; specific always beats generic.
How does the WebPage tool build the breadcrumb item URLs?
Level 1 gets your site origin, the last filled level gets the full page URL, and any middle level is emitted with a name only. That keeps the trail valid without you typing three addresses. Fill only the levels that exist in your real navigation.
Which subtypes does this webpage schema generator include?
Ten in total: WebPage, AboutPage, ContactPage, FAQPage, CollectionPage, ProductPage, ProfilePage, CheckoutPage, SearchResultsPage, and RealEstateListing. A few of those also have dedicated builders on this site with extra fields, so use those when you need the deeper options.
Does the 160 character limit on the WebPage description block my typing?
No, it's a warning, not a wall. The description property has no hard length limit in schema.org, but search snippets tend to truncate around 160 characters, so the counter turns amber past that point to nudge you toward something shorter.
Can the author in WebPage markup be a company instead of a person?
Yes. The Author type selector switches between Person and Organization, and the name and URL fields apply to either. Team-written pages, documentation, and support content often credit the company, which is perfectly valid markup.
Is WebPage schema redundant if the page already has Article markup?
Mostly, yes. Both describe the page itself, so declaring them side by side invites conflicting dates and titles. Pick the more specific type, which for a blog post is Article. WebPage earns its place on pages that would otherwise carry nothing.
Why does the WebPage output wrap my logo in an ImageObject?
Because schema.org models a logo as an image entity, not a bare string. The tool nests { "@type": "ImageObject", "url": ... } under the publisher automatically, matching the structure Google's documentation shows for publisher logos.