The site name in the results
The name shown beside a result is generated automatically, from the home page and from what is said about the site elsewhere. Markup on the home page expresses a preference, with no guarantee: a generic name is unlikely to be selected, and an alternative name can be offered.
Two labels people keep confusing
In a result, two pieces of text look alike and do not share an origin: the title, which belongs to the page, and the site name, which covers every page. The documentation opens on that distinction, which suggests it is regularly missed.
Generation of the site name shown in the results is completely automated and takes into account content from the site's home page as well as references to it that appear on the web.
officialSource : Google Search Central, “Provide a site name to Google Search”
Two sources, then, and only one of them is yours. What the site says about itself on its home page, and what the rest of the web says about it. That is exactly the structure of the reputation chapter in the rater guidelines, and the resemblance is probably not accidental.
A preference, and what it is worth
WebSite structured data on the home page indicates a preference; the system also considers the social sharing name, the page title and heading elements, but the structured data matters most, and an automatically selected name cannot be changed manually.
officialSource : Google Search Central, “Provide a site name to Google Search”
The vocabulary is that of a wish rather than a command — indicate a preference, be considered, matter most. And the most useful sentence comes last: an automatically selected name cannot be changed by hand. There is therefore no form, no recourse, no appeal procedure.
Your brand name showing badly in Google? We correct the site name within 48 hours through our partner access.
What stops a name being selected
A generic name such as “Best Dentists In Iowa” is unlikely to be selected unless it is an extremely well-recognised brand name; the documentation asks for a concise, commonly recognised name that is not misleading.
officialSource : Google Search Central, “Provide a site name to Google Search”
The example given speaks for itself, and it targets a widespread practice: naming a site after the query it aims at. The documentation says plainly that this does not work, unless the name is also a very well recognised brand — that is, in the case where the manoeuvre was unnecessary.
An alternate name property lets you offer a second choice, since the system generally will not use the same site name for two different sites that are global in nature, and may determine that a site is more commonly recognised by an acronym than by its full name.
officialSource : Google Search Central, “Provide a site name to Google Search”
The alternate name is the only fallback provided, and it is filled in once and for all. Declaring the acronym alongside the full name, or the reverse, costs a line and covers the most frequent case.
Where the markup must live
Only one name is supported per site, a site being defined by its domain or subdomain; the subdirectory level is not supported, and subdomains starting with www or m are generally considered equivalent to the domain.
officialSource : Google Search Central, “Provide a site name to Google Search”
That rule settles a question of architecture that arises long before markup: a section installed in a subdirectory can never carry its own name, while a subdomain can. The choice is made when the address is created, not when it is marked up.
The markup must sit on the home page of the domain or subdomain, and that page must be crawlable; where a subdomain's home page carries no markup, the domain-level name may be used as a fallback.
officialSource : Google Search Central, “Provide a site name to Google Search”
Since the system combines the home page with what is said about the site elsewhere, consistency of the name outside the site weighs as much as its declaration: a name used in three different forms declares itself badly, whatever markup is in place.
hypothesis
The status is that of a reading. The documentation asks for consistency on the home page and mentions outside references among the system’s inputs; it does not say external consistency weighs as much as the declaration. We infer it from the structure described, and display it as an inference.
Declaring a site name and making it consistent everywhere
hypothesis
- Effort
- low
- Time to effect
- months
- Risk
- none
- Durability
- structural
The effort is minimal for the markup, real for the consistency work, which touches dozens of places off the site. The delay is long: the system combines several sources and nothing changes on request. The risk is nil. Durability is excellent, a well-established name having no reason to change, which makes this one of the rare tasks that is not redone.
What does not work, or no longer works
Naming a site after the query it targets. The documentation writes that a generic name is generally not selected.
Then placing the markup on a section page. It belongs on the home page of the domain or subdomain, and that page must stay crawlable.
Finally, hoping for a manual correction. An automatically selected name is not changed by hand: the only recourse provided is the alternate name, declared before it is needed.
Sources
- Provide a site name to Google Search — Google Search Centralaccessed on
- Robots meta tag, data-nosnippet, and X-Robots-Tag specifications — Google Search Centralaccessed on
Block revalidated on
Frequently asked questions
- Can you impose the name shown beside your results?
- No. Generation is automated and the documentation writes that an automatically selected name cannot be changed manually. Home page markup expresses a preference, which the system considers alongside the page title, heading elements and what is said about the site elsewhere.
- Where does the markup belong?
- On the home page of the domain or subdomain, and nowhere else: a section page does not count. That page must stay crawlable. If a subdomain has no markup of its own, the domain-level name may serve as its fallback.
- Why is my name not selected?
- Two causes appear in the documentation. A generic name is only selected if it corresponds to an extremely well-recognised brand. And the same name is generally not used for two different sites that are global in nature, which explains cases of clashing names.
- What is the alternate name for?
- For offering a second choice when the first is unavailable or not selected. The documentation cites a site more commonly recognised by its acronym than by its full name. It is the one fallback provided for keeping some say when the main preference does not land.
- Is the site name the same as the page title?
- No, and the documentation opens on that distinction. The title belongs to each page, the site name covers the whole site. They appear side by side in a result, which is a good reason not to repeat the site name in every page title.