WebSite schema generator
Tell Google what your site is called, so the name above your URL in results reads "Example Outfitters" rather than "example.com".
The sitelinks search box that used SearchAction was retired in November 2024; WebSite markup now matters for site names.
Required
2/2
Recommended
1/1
All Google-required properties present. That makes the page eligible, not guaranteed. Google's docs
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "Example Outfitters",
"alternateName": [
"ExO",
"example.com"
],
"url": "https://example.com/",
"inLanguage": "en"
}
</script>When to use WebSite markup
- Once, on the home page of a domain or subdomain.
- When Google shows the wrong site name, or your domain instead of your brand.
- Pair with Organization markup on the same page.
Getting it right
- Required: name and url (the canonical home page).
- Use alternateName for acronyms or a shorter version.
- Keep the name consistent with your title tag, headings and Organization name.
- SearchAction for the sitelinks search box no longer does anything in Google; you can leave it or remove it.
Source: Google Search Central, Site name structured data documentation, and schema.org/WebSite.
Google's property list
| Property | Google says |
|---|---|
name | required |
url | required |
alternateName | recommended |
Example output
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "Example Outfitters",
"alternateName": [
"ExO",
"example.com"
],
"url": "https://example.com/",
"inLanguage": "en"
}WebSite schema questions
Does the sitelinks search box still work?
No. Google retired the sitelinks search box in November 2024 and removed its documentation. WebSite markup is still used for site names.
Why does Google ignore my site name?
Google checks several signals. Make the name concise, used consistently across the home page, and not a generic phrase.
Does it work for subdomains?
Yes, for domain-level and subdomain-level home pages, but not for subdirectories.