Technical SEOPublished26.05.2026

WebSite schema

WebSite schema is a Schema.org markup for describing a website as a resource. It enables the sitelinks search box, sets the site name, and specifies its URL for display in Google Search.

In brief

WebSite schema is a Schema.org markup type describing an entire website as a resource. It includes properties: name, url, description, alternateName, and SearchAction for activating in-SERP site search (sitelinks search box).

What is WebSite schema

WebSite schema is a Schema.org markup type for describing a website as a single resource. It is added to the homepage once and describes the resource as a whole: name, URL, description, and alternative names (e.g., abbreviations).

The primary practical use of WebSite schema is activating the sitelinks search box: a search bar that appears directly in Google's search results next to the homepage snippet, allowing users to search your site's content without visiting it.

WebSite schema doesn't guarantee a sitelinks search box — Google decides independently whether to show it. The markup only signals support for the feature and specifies the search endpoint.

Key WebSite schema properties

name: The official name of the site or organization. Displayed in search as the resource name.
url: Canonical URL of the homepage.
description: Brief site description — optional, but helps Google understand context.
alternateName: Alternative name: abbreviation or shorthand. For example, 'PSI' for 'PageSpeed Insights'.
potentialAction: SearchAction — describes the site's search function. Includes query-input and the target URL template.

Sitelinks search box is a search bar that appears in Google results for the homepages of popular sites. To enable it, add a potentialAction of type SearchAction to the WebSite markup.

Add WebSite markup to the homepage only — not all pages
In potentialAction, set @type: SearchAction
Add query-input: required name=search_term_string
In target, specify your site's search URL: https://example.com/search?q={search_term_string}
Verify that site search actually works at that URL

WebSite vs. WebPage schema

Parameter	WebSite schema	WebPage schema
Describes	The entire site as a resource	A specific page
Where added	Homepage only	Each target page
Primary use	Sitelinks search box, site name	Page metadata, breadcrumbs
Frequency	Once per site	One markup per page
Relationship	WebPage links to WebSite via isPartOf	WebSite is the parent of WebPage

WebSite schema example

Example WebSite JSON-LD: { "@context": "https://schema.org", "@type": "WebSite", "name": "seohead.tech", "url": "https://seohead.tech", "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://seohead.tech/search?q={search_term_string}" }, "query-input": "required name=search_term_string" } }. Add only to the homepage.

FAQ

Common questions

No. WebSite schema is added to the homepage only — once. It describes the site as a whole. For individual pages, use WebPage or more specific types.

No. Google decides independently whether to show this feature. It typically appears for large sites with established brand traffic. The markup only enables support for the feature.

Through the isPartOf property in the WebPage markup: { "isPartOf": { "@id": "https://example.com/#website" } }. Assign an @id to WebSite so WebPage can reference it.

Not directly. It helps Google better identify the resource and its name. The sitelinks search box can improve CTR for brand queries if Google chooses to display it.

Direct contacts

Discuss your project?

Share your goals and website context — I will suggest a practical next step.

[email protected]@pavelbarushka LinkedIn