Website Schema Generator
Generate valid JSON-LD Website schema markup in seconds. Define your site name, alternate names, supported languages, and a Sitelinks Search Box, and copy the structured data straight into your <head>.
Language 1
Sitelinks Search Box (potentialAction)
WebSite schema
What is Website schema?
Website schema is a JSON-LD block using the Schema.org WebSite type that describes your site to search engines. It belongs on the homepage only, inside a <script type="application/ld+json"> tag in your <head>.
One of the most practical uses of Website schema is indicating your preferred site name. By default, Google infers what to display as your site's name from your <title> tags and anchor text patterns across the web, which may not match your actual brand name.
The name property lets you state it explicitly, so Google can use it in search results, sitelinks, and other branded SERP features. If your domain name differs from your brand name, or if you're known by multiple aliases, this is the most direct way to tell Google what name to show.
Why the site name field matters for SEO?
When someone searches for your brand, the first thing they see in Google's results is your site name, i.e the label that appears above your URL in sitelinks and search result listings. By default, Google picks that name itself, typically pulling it from your <title> tags or anchor text across the web. The result is often a raw domain like example.com or sometimes a different variation that does not reflect how you actually present your brand.
When you implement Website schema with a name property, you give Google an explicit, machine-readable label for your site, which may appear above the page title name. This usually gives more confidence to users as th
This is especially valuable if your domain name doesn't match your brand name, if your brand name is short and could be confused with other entities, or if you operate under multiple names (e.g. a legal name and a trading name).
The alternateName field lets you list all known aliases so Google can confidently consolidate them into a single entity, reducing misattribution and improving how your brand surfaces across Search, Knowledge Panels, and AI-generated answers.
Without explicit Website schema, Google makes its best guess based on your <title> tags and anchor text patterns across the web. A single WebSite block on your homepage removes that ambiguity.
Do I need to add Website schema if I already have Organization schema?
Yes, Website schema and Organization serve different purposes. Organization schema describes the entity behind the site while Website schema describes the site itself and is the only type that enables the Sitelinks Search Box and the site name override in search results. Both can coexist on the same page.
What does this generator produce?
It outputs a WebSite JSON-LD block you paste into the <head> of your homepage. It follows the Schema.org WebSite type and supports every field Google uses to understand your site's identity.
It includes the following properties:
name: Your preferred site name as you want it to appear in Google's search results. This overrides whatever label Google would otherwise infer from your title tags or external anchor text.url: The canonical root URL of your site. This anchors the schema to a specific, stable address and helps Google resolve your site as a distinct entity.alternateName: An array of additional names your site is known by, such as brand aliases, abbreviations, or former names. Your site URL is included here automatically as a fallback option. Each entry strengthens entity consolidation across the web.inLanguage: One or more language entries, each with a human-readable name and a BCP 47 code such asenorzh-TW. Signals to search engines which languages your site serves.potentialAction: ASearchActionobject if your site has working internal search. Requires a search URL containing the literal token{search_term_string}.
Frequently Asked Questions
Will this guarantee a Sitelinks Search Box in Google?
No. Google has already deprecated the Sitelinks Search Box feature globally on November 21, 2024.
What should I put in the alternate names field?
Include any brand aliases, abbreviations, taglines, or former names your site is known by. This generator automatically adds your site URL as an alternate name, which is a recommended practice for entity disambiguation.
Can I use this for multilingual sites?
Yes. Use the "Add another" button in the language section to add one entry per supported language. Each entry takes a human-readable name and a BCP 47 code, and they will all appear inside the inLanguage array.