WebSite Schema
WebSite Schema identifies your website as a distinct digital property and helps search engines understand its name, URL, publisher, and search functionality.
Your business is an entity.
Your website is also an entity.
They are connected.
They are not the same thing.
That distinction matters more than most people realize.
What Is WebSite Schema?
WebSite Schema is structured data that describes a website.
It can identify:
- the website name
- the website URL
- the publisher
- alternate website names
- site search functionality
It tells machines, “This is the website, and this is the organization connected to it.”
Why WebSite Schema Matters
Search engines need to understand more than individual pages.
They need to understand the site as a whole.
WebSite Schema helps clarify:
- which website is official
- who publishes the website
- what the website is called
- how the website connects to the organization entity
It supports entity clarity.
Not flashy.
Useful.
WebSite Schema vs Organization Schema
This is a common mix-up.
| WebSite Schema | Organization Schema |
|---|---|
| Describes the website. | Describes the business. |
| Identifies the digital property. | Identifies the real-world organization. |
| Usually belongs on the homepage. | Usually belongs on the homepage or organization profile page. |
| Can include SearchAction. | Can include SameAs, logo, founder, and contact details. |
Both can exist on the same site.
They just describe different things.
Where Should WebSite Schema Go?
WebSite Schema is usually placed on the homepage.
The homepage normally represents the website as a whole.
For a static Knowledge Catalog like this one, the homepage and major hub pages should work together to make the website structure obvious.
The schema should reinforce that structure.
Common WebSite Schema Properties
| Property | Purpose |
|---|---|
| name | The official name of the website. |
| url | The canonical URL of the website. |
| publisher | The organization that publishes the website. |
| alternateName | Other names people may use for the website. |
| potentialAction | Optional search functionality using SearchAction. |
A Simple Example
This is a simplified WebSite Schema example.
{
"@context":"https://schema.org",
"@type":"WebSite",
"name":"Firm IQ Knowledge Catalog",
"url":"https://knowledge.firmiq.io/",
"publisher":{
"@type":"Organization",
"name":"Firm IQ",
"url":"https://firmiq.io"
}
}
Your actual implementation should match the real website and publisher information.
WebSite Schema and SearchAction
Some websites use WebSite Schema with SearchAction.
SearchAction can describe how users search the site.
That only makes sense if the website has real site search functionality.
Do not add SearchAction just because it looks technical.
That is how schema turns into digital confetti.
WebSite Schema Supports Knowledge Catalogs
A Knowledge Catalog should be understood as a structured information system.
WebSite Schema helps identify the catalog itself.
Breadcrumb Schema then helps explain how individual pages fit inside the catalog.
Article Schema helps explain the educational pages.
Everything works together.
Common Mistakes
- Confusing the website name with the company name.
- Using WebSite Schema instead of Organization Schema.
- Adding SearchAction when the site does not have search.
- Using the wrong URL.
- Creating conflicting website entities.
- Forgetting to connect the publisher.
The fix is simple.
Describe the real website accurately.
There’s that word again: accurately.
Firm IQ Definition
At Firm IQ, WebSite Schema is machine-readable documentation for the website entity.
It helps search engines and AI systems understand the website as a structured digital property connected to the organization that publishes it.
Here’s what we’ve learned: your website is not just a pile of pages. It is a knowledge system. WebSite Schema helps machines recognize the system, not just the individual documents inside it.