Reference guide · technical-seo · Published 2026-08-16 · 3 min read
Site name structured data explained
Site name structured data: JSON-LD markup, the visible page name rule, and how Google chooses the title it shows.
- ·The markup
- ·Google's display rules
- ·Common pitfalls
Why a site name matters
Google takes the site name it displays from the page title, the content, and any structured data it can trust. Without a markup nudge, a site called "Bluepeak Coaching" can show up as "Home | Bluepeak Coaching, Coaching Near Me" in results, especially on the root page. The WebSite schema with a name helps Google keep the brand the way you want it.
The markup
Embed in every page's <head>, usually on the homepage and kept on the key pages:
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "Bluepeak Coaching",
"url": "https://www.example.com/"
}For larger setups, two extra optional fields help:
{
"@type": "WebSite",
"name": "Bluepeak Coaching",
"potentialAction": {
"@type": "SearchAction",
"target": "https://www.example.com/search?q={search_term_string}",
"query-input": "required name=search_term_string"
}
}The potentialAction adds a site-link search box in search results when eligible. It is not required for the brand name part.
Google's display rules
Google's documentation on site names has three rules that matter:
- The name in markup must be a valid, honest name for the site; it cannot be a different brand or a keyword-stuffed phrase.
- Google ignores the markup when the value is inconsistent with the page content and the site's name as shown elsewhere, so stamp it the same on every page.
- The structured data crosses the "same as the visible page name" check silently; a mismatch means no benefit, not an error.
The only way to know what Google selected is the live search result or the URL inspection result, which shows the current display name on the Search Appearance tab.
Common pitfalls
- marking a subpage with a different brand. A subdomain or a /blog section that marks itself a separate site splits the site name in search results.
- putting the markup in a JSON-LD block that a minifier strips. The site name ends up missing from the render, so the report says "No data". Keep it in the SSR'd
<head>. - using the same
@idtwice. Use"@id": "https://www.example.com/#website"once, and reference other schema from it, or the item merges incorrectly. - a name that is not the visible one. Google has an explicit "not the same as the visible site name" failure; make the markup match the
<title>-and-logo brand.
Where it fits
The site name markup is the sibling of title and meta in the <head>. Add it once, test with the structured data guide and the enhancement report for errors, then leave it. It rarely changes, and it is the cheapest way to keep the brand clean in search results.
In short
Site name structured data is a tiny JSON-LD block that keeps Google's display of your brand consistent. It is not a ranking signal, but it is the one that decides how visitors see your results. Stamp the same name on every page, keep it matching the visible content, and check it once.