Website schema is JSON-LD structured data applied to a site's homepage that enables the Sitelinks Searchbox feature in Google Search and reinforces brand entity information for knowledge panels.
Quick Answer
Website schema is JSON-LD structured data applied to a site's homepage that enables the Sitelinks Searchbox feature in Google Search and reinforces brand entity information for knowledge panels.
WebSite schema goes only on the homepage — duplicating it site-wide creates conflicting entity signals.
Combining WebSite + Organization schema on the homepage maximizes Knowledge Panel eligibility.
Sitelinks Searchbox requires a live, functional internal search endpoint — never point to a 404.
Key Takeaways
WebSite schema goes only on the homepage — duplicating it site-wide creates conflicting entity signals.
Combining WebSite + Organization schema on the homepage maximizes Knowledge Panel eligibility.
Sitelinks Searchbox requires a live, functional internal search endpoint — never point to a 404.
How Website Schema Works
The WebSite schema type (schema.org/WebSite) is placed exclusively on the homepage and tells Google the site's name, URL, and — when combined with a SearchAction property — the internal search endpoint that powers the Sitelinks Searchbox. The Sitelinks Searchbox appears beneath the main listing in branded SERPs, allowing users to search the site directly from Google results. Google's documentation specifies that the SearchAction target must point to a live, functional search results page using the query-input parameter.
Why Website Schema Matters for B2B Marketing
For B2B companies, Website schema is a foundational brand entity signal. Combined with Organization schema (also on the homepage), it feeds Google's Knowledge Graph with canonical name, URL, logo, and social profile data. Brands with complete entity markup are more likely to earn a Knowledge Panel in branded searches — a critical trust signal when prospects research vendors before purchase decisions. HubSpot and Salesforce both implement full WebSite + Organization combos on their homepages.
Website Schema: Best Practices & Strategic Application
Best practices: place WebSite schema only on the canonical homepage URL (not subdomains or blog subdirectories). Ensure the name property uses your exact brand name as it appears in Google's index — inconsistencies delay Knowledge Panel generation. If you have a site search function, include the potentialAction SearchAction block; if not, omit it rather than pointing to a 404. Validate with Google's Rich Results Test before pushing to production.
Agency Perspective: Website Schema in Practice
Agencies commonly duplicate WebSite schema across all pages via a CMS template — this is incorrect and can create conflicting entity signals. Another mistake is using the www vs. non-www variant inconsistently in the URL property: always use whichever version is your canonical (typically the one set in Search Console as preferred domain). Revisit Website schema after any domain migration or brand rename to ensure the name and URL properties are updated within 24 hours of the change going live.
Frequently Asked Questions: Website Schema
Website schema is JSON-LD structured data applied to a site's homepage that enables the Sitelinks Searchbox feature in Google Search and reinforces brand entity information for knowledge panels.
Yes. Google requires WebSite schema with a valid SearchAction property to enable the Sitelinks Searchbox. Without it, Google may still show sitelinks in the regular format, but the interactive search box will not appear in branded results.
Website schema must be placed on the homepage only, within a JSON-LD script block in the <head> or <body>. It should never be replicated on internal pages, category pages, or blog posts.
Not directly. Website schema primarily benefits branded search features (Sitelinks Searchbox, Knowledge Panel). However, stronger brand entity signals can indirectly improve topical authority and trust, which may benefit overall domain-level rankings over time.
MV3 Marketing helps B2B companies apply these strategies to drive measurable pipeline growth. Our team executes technical seo audit for technology, SaaS, and professional services companies.
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
