WebSite and WebPage
Organization says who you are. WebSite says "this is our site." WebPage says "this is one page on it." Together they're the frame everything else hangs on.
Two types, two jobs
It's easy to mix these up, so here's the short version:
WebSite
The whole site, as one thing. There's only one, so you describe it once, on the homepage.
WebPage
The specific page someone is looking at. Every page gets its own, pointing back to the WebSite.
WebSite: once, on the homepage
Google reads WebSite markup on your homepage as a hint for your site name, the name shown above your link in search results. Without it, Google guesses from your title tags and headings, and sometimes it guesses wrong. You might see "Fern" or "Home" where you wanted "Fern & Ink."
Google still makes the final call. But name, alternateName, and url on the homepage are your clearest way to tell it what you prefer.
{
"@context": "https://schema.org",
"@type": "WebSite",
"@id": "https://fernandink.example/#website",
"name": "Fern & Ink",
"alternateName": ["Fern and Ink", "fernandink.example"],
"url": "https://fernandink.example/",
"inLanguage": "en-US",
"publisher": { "@id": "https://fernandink.example/#organization" }
}
That publisher line is the payoff from Lesson 4. It doesn't repeat the Organization. It points at it by @id. On the homepage, you'd put this WebSite and the full Organization block in the same script, usually inside an @graph.
| Property | Status | What it means |
|---|---|---|
name | Required | Your preferred site name. Short, and consistent with how the homepage refers to itself. |
url | Required | The canonical homepage URL, with the trailing slash. |
alternateName | Recommended | Backup names in order of preference: a short form, an acronym, or your domain as a last resort. |
publisher | Optional | Who runs the site. Point to your Organization's @id. |
inLanguage | Optional | The site's main language, as a code like en-US. |
The Required and Recommended tags here come from Google's site names documentation. A few rules from that doc worth knowing: site names work per domain or subdomain (not per folder), the homepage must be crawlable, and if the site has any duplicate homepages (http and https, www and non-www) they should all carry the same markup.
What about SearchAction?Older tutorials add a potentialAction with SearchAction to get a search box under your result. Google retired that sitelinks search box in late 2024. The markup won't break anything, but it no longer gets you a feature in Google, so we leave it out.
WebPage: one per page
WebPage has no rich result in Google. Its value is clarity: it ties each page to the site, says what the page is about, and gives the breadcrumb and dates a home. Think of it as the label on a folder.
Here's Fern & Ink's About page. Notice we've used AboutPage, a more specific kind of WebPage. More on that below.
{
"@context": "https://schema.org",
"@type": "AboutPage",
"@id": "https://fernandink.example/about/#webpage",
"name": "About Fern & Ink",
"url": "https://fernandink.example/about/",
"isPartOf": { "@id": "https://fernandink.example/#website" },
"about": { "@id": "https://fernandink.example/#organization" },
"breadcrumb": { "@id": "https://fernandink.example/about/#breadcrumb" },
"primaryImageOfPage": {
"@type": "ImageObject",
"url": "https://fernandink.example/images/studio-press-room.jpg"
},
"datePublished": "2024-03-12",
"dateModified": "2026-10-02",
"inLanguage": "en-US"
}
Line by line
Because there's no Google rich result for WebPage, these tags are our advice, not Google requirements.
| Property | Status | What it means |
|---|---|---|
@id | Recommended | The page URL plus #webpage. Articles and other blocks on this page can point to it. |
name | Recommended | The page's title, close to what's in the <h1> or <title>. |
url | Recommended | The page's canonical URL. |
isPartOf | Recommended | Points to the WebSite. This is what makes the page "belong" to the site. |
about | Optional | The main thing the page describes. Here it's the Organization. On a service page, it'd be the Service. |
breadcrumb | Optional | Points to the page's BreadcrumbList. We build that block in Lesson 6. |
primaryImageOfPage | Optional | The main image people see on the page. |
datePublished / dateModified | Optional | ISO 8601 dates. Only update dateModified when the content really changes. |
Pick the most specific page type
Schema.org has a handful of WebPage subtypes. Use one when it fits, and plain WebPage when none does.
AboutPagefor your About or Our Story page.ContactPagefor the page with your contact form, phone, and address.CollectionPagefor listing pages: a blog index, a portfolio grid, a category of products.FAQPagefor a page of questions and answers. It's a WebPage too, but it has its own rules and an honest catch about rich results. That's Lesson 10.
Blog posts usually get a plain WebPage wrapped around an Article or BlogPosting, which we'll cover in Lesson 9.
Common mistakes
Don't repeat WebSite with different namesIf your homepage says "name": "Fern & Ink" and a plugin adds a second WebSite block that says "Fern & Ink Studio | Minneapolis," you've sent mixed signals. Keep one WebSite node on the homepage, and on other pages just point to it with isPartOf.
- Stuffing the site name.
nameis your name, not a keyword list. "Fern & Ink," not "Fern & Ink Minneapolis Letterpress Printing Wedding Invitations." - Copying the homepage WebPage everywhere. Each page's
@id,name, andurlmust be its own. If you use a template, make sure those values are dynamic. - Testing in the wrong tool. Google's Rich Results Test doesn't check site names. Use the Schema Markup Validator to confirm the WebSite block parses.
Try it
Write the WebSite block for your own homepage, with one alternateName. Then pick a page on your site (your contact page is a good one) and write its WebPage block using the right subtype. Make sure isPartOf points to the exact @id you used on the homepage, character for character.
Check yourself
- WebSite lives once, on the homepage, with
nameandurl. - I know WebSite markup is a hint for the site name, and Google makes the final choice.
- I'm not adding
SearchActionto chase the retired search box. - Each page has its own WebPage (or subtype) with
isPartOfpointing to the WebSite. - I know which subtype to use for About, Contact, and listing pages.
How these foundation types fit together on a real site: Schema Markup Explained, Part 1: Organization, WebSite, WebPage, and BreadcrumbList.