Website Schema Markup Generator

Website schema markup helps Google recognise your site as a single entity and improves the way your brand appears in search results. It builds a clean, authoritative foundation for structured data, supporting other schema types like Organization, Article, and Product — and makes your site eligible for the Sitelinks Search Box.

Try an example

Fields

Website Name

Website URL

Internal Search URL (with {search_term_string})

Optional String After Query

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebSite"
}
</script>

Validate (Schema)Validate (Google)

Website Schema Markup FAQ

Website schema markup is a type of structured data defined by Schema.org that tells search engines general information about your website, such as its name, homepage URL, and internal search feature (if you have one).

When implemented correctly, Website schema helps Google better understand your domain as a single entity. It can also enable Sitelinks Search Box rich results - the embedded search bar that sometimes appears under your homepage listing in Google.

Adding Website schema markup helps search engines:

Identify your website as the root entity for your brand.
Understand your search function, enabling the Sitelinks Search Box rich result.
Improve indexing and crawl efficiency across your site.
Connect other schema types (like Organization, Article, or Product) back to your domain.

Think of Website schema as your site's "master label" - it ties everything else together for Google.

The main properties to include are your website's name and homepage URL, but you can do some additional work to connect your site's own search functionality.

Website schema markup strengthens your SEO in subtle but powerful ways:

Helps Google confirm your canonical homepage URL.
Makes your site eligible for the Sitelinks Search Box feature.
Improves crawl context for all other schema types connected to your domain.
Reinforces your entity identity in the Knowledge Graph.
Ensures your brand appears cleanly in search results when users search for your name.

It doesn't directly affect rankings - but it helps search engines understand your site more clearly and connect your brand to related content types.

Missing or incorrect URL: Always use the canonical homepage URL (with HTTPS).
Wrong placement: Website schema should be placed on the homepage (or global template) - not on every page.
No potentialAction despite having a search function: If your site has internal search, add the SearchAction markup to qualify for rich results.
Incorrect search query string: Test your search URL pattern - ensure {search_term_string} works when replaced with an actual query.
Duplicate Website schema entries: Only one Website schema block is needed sitewide.
Not pairing with Organization schema: These are two different types of schema markup and complement each other. Organization defines who you are, WebSite defines what you own.

No. Website schema is intended for the homepage or global template only.

It describes your entire site, not individual pages.

Yes - and you should.

They work together:

Organization defines your business or entity.
WebSite defines your website as a property of that organization.

Both can appear in the same JSON-LD block or as separate ones.

Search your brand name in Google.

If eligible, you'll see a search bar under your main result.

You can also track visibility via Google Search Console > Enhancements > Sitelinks Search Box.

Yes. Even without potentialAction, Website schema helps Google understand your domain's structure and identity.

Indirectly. Website schema helps confirm your site as the official web presence of your brand, making it easier for Google to link your website to your Knowledge Graph entity.

Yes - but each website should have its own WebSite schema block with a unique homepage URL.

You can reference them all under a single Organization entity.

Include the canonical homepage URL in WebSite schema for each localized version (e.g., .com, .co.uk, .de) and use hreflang in your HTML to help Google understand language variations.