WebSite Schema Generator | GEO Checker Tool

Why WebSite Schema Matters

WebSite schema serves two purposes: it tells search engines and AI engines the authoritative name and URL of your site, and it enables the sitelinks search box feature in Google Search.

Site name in Google: Google uses WebSite schema's name property to display your brand name in the search result breadcrumb. Without it, Google may show your domain URL instead.
Sitelinks search box: If you include a potentialAction with a SearchAction, Google may show a search box directly in your organic listing for branded queries.
AI domain identification: AI engines associate the schema's name and url properties to confirm which brand owns a domain, particularly useful for brands with non-obvious domain names.

Frequently Asked Questions

Do I need WebSite schema if I already have Organization schema? ⌄

Yes, they serve different purposes. Organization schema establishes your brand identity and sameAs links. WebSite schema tells search engines about your website specifically: its name, URL, and search capability. Both should be on your homepage. They can coexist in separate JSON-LD script blocks.

What is the search URL template format? ⌄

The template must contain the literal string {search_term_string} (with curly braces) where the user's search query will be inserted. For example: https://example.com/search?q={search_term_string} or https://example.com/?s={search_term_string} for WordPress. Google will only show the sitelinks search box if your site has an internal search function that returns results for the given query.

On which page should WebSite schema be placed? ⌄

WebSite schema should only appear on your homepage (the root URL of your domain). Google processes it as a domain-level signal, so placing it on other pages has no additional benefit and may cause confusion. Use one WebSite schema block per domain.