In short and in plain language
Above each result on Google there is a name. Next to it there is a small picture. The picture is called a favicon.
Google picks the name by itself. It looks at the first page of the website. The name should be the same everywhere on that page.
The name should also be in a special code for Google. This code only goes on the first page.
The picture should be square. It should be at least 48 pixels wide. A PNG file works well.
After a change, Google needs time. It can take a few days or weeks.
Before anyone clicks a search result, they see two things that do not belong to the individual page at all: a small icon and the name of the website. Both sit above the title link on every result from your domain, whether it is the home page, a service page or a blog article. Google calls this header line the attribution; it can include the site name, the favicon and the URL of the page (Google Search Central). If it shows only the bare domain instead of your business name, or your logo is missing, the result looks less familiar than the one directly below it. Google generates site names automatically, but it takes into account what your home page states: WebSite structured data, og:site_name, the title element and headings (Google Search Central). The favicon is subject to fixed requirements on size, format and location, and since August 28, 2026 the documentation lists the supported file formats individually (Google Search Central). This article shows how to state name and icon so that Google can use them, which mistakes prevent that and how long it takes for a change to become visible.
Key takeaways
- State your preferred site name with WebSite structured data on the home page, with name and url as required properties; subpages do not need the markup (Google Search Central).
- Markup, og:site_name, title and H1 on the home page carry the same name. If Google is not confident enough about the stated name, it can build one from other sources or show the domain name (Google Search Central).
- Use alternateName to add a short form or acronym and, as a last option, the domain name in lowercase, ordered by your preference (Google Search Central).
- The favicon is square and at least 8 × 8 pixels, 48 × 48 pixels or more is recommended, in BMP, GIF, ICO, PNG, JPEG, PPM or TIFF, linked via link rel=icon on the home page (Google Search Central).
- Google supports one favicon per hostname and one site name per domain or subdomain. A shop under /shop/ gets neither its own icon nor its own name (Google Search Central).
- After a change, submit the home page for indexing in the URL Inspection tool. Recrawling and processing can take anywhere from several days to several weeks (Google Search Central).
What sits above the title link
A simple text result in Google Search is made up of several building blocks: the attribution, the title link and the snippet (Google Search Central). The attribution is the header line. It describes the source of the result and can include the site name, the favicon and the URL of the page; the visible URL in turn consists of the domain and the breadcrumb (Google Search Central). Below it comes the title link, the linked headline, followed by the snippet with a short description of the page.
For anyone working on a website, separating these levels is essential. The title link belongs to the individual page and is built from its title element, its main heading and other sources. The site name, by contrast, applies to the entire website, while title links refer to individual web pages (Google Search Central). Improving the title of a service page therefore changes nothing about the name above the result. Conversely, correcting the site name affects every result from the domain at once. How to handle titles and descriptions of individual pages is covered in our technical SEO checklist; here we deal with the line above them.
Site names are no longer a side issue. Google has documented them since October 14, 2022 (Google Search Central), and since September 7, 2023 the documentation has listed them as available in all languages where Google Search is available (Google Search Central). Today it states that site names are available in all of these languages, on mobile devices as well as on desktop (Google Search Central). How an individual result looks still depends on the device, country and language of the query, and not every result shows every possible element (Google Search Central). On the narrow screen of a smartphone in particular, name and icon shape the first impression before the title has even been read.
Where Google gets the site name
Google generates site names automatically. It takes into account content on the home page and references to the website that appear on the web; the aim is to describe the source of each result as accurately as possible (Google Search Central). By its own account, Google cannot manually change an automatically selected site name (Google Search Central). So there is no form where you enter the name you want and the problem is solved.
What you can do is state your preference clearly and without contradictions. The most important signal is WebSite structured data on the home page. In addition, the system evaluates the content of og:site_name, the title element, headings and other text on the home page (Google Search Central). Each of these places is a kind of ballot. If they agree, Google has little reason to deviate from what you state. If the markup says “Sample-Heating”, the page title says “Home | SHC” and og:site_name says “SH Services Inc.”, the system has to choose between several candidates.
If the system is not confident enough about the name you provided, it can create a site name from other sources or display a domain or subdomain name (Google Search Central). That is exactly the error case on the right half of the graphic above: inconsistent names on the home page, and in the end only the domain appears above the result. Businesses that are known by their domain anyway may live with that. For everyone else, the result looks unfamiliar even though the page behind it would be exactly the right one.
The site name is not the legal name
Choosing a name Google will adopt
The guidelines for the name are brief. It should be unique, accurately reflect the identity of the site and not be misleading to users (Google Search Central). There is no fixed character limit, but long site names may be truncated on some devices (Google Search Central). For most businesses, the right choice is the name customers know them by: the brand name or the short business name without the legal form.
Generic names stand little chance. According to the documentation, a generic name that only describes a service and a location is unlikely to be selected as a site name unless it is a very well-known brand name (Google Search Central). Identical names also get in each other's way: Google generally does not use the same site name for two different global sites (Google Search Central). If your website is named after your trade and town, check whether there is a distinguishable name and then use it consistently, on the website as well as in your Google Business Profile. How name, profile and location pages work together in local search is part of our work in local SEO.
- Do customers know the business by exactly this name?
- Does the name fit on one line on a smartphone?
- Does it describe the business and not just the trade and town?
- Is it used the same way on vehicles, invoices and the Business Profile?
- Is there a common short form that works as an alternative?
The WebSite markup on the home page
WebSite structured data is the direct way to tell Google your preferred name. The required properties are name with the site name and url with the canonical home page of the domain or subdomain (Google Search Central). The markup belongs on the home page and does not need to be on every page of the site (Google Search Central). The home page here means the root URI: https://example.com is the home page of the domain, https://example.com/de/index.html is not (Google Search Central). The format can be JSON-LD, RDFa or microdata; in practice, JSON-LD in the head of the page is easy to maintain.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "Sample Heating",
"alternateName": ["SH Heating", "sample-heating.example"],
"url": "https://www.sample-heating.example/"
}
</script>The type is widespread: schema.org lists WebSite as used on 10 million domains and more, based on monthly aggregations from the Google index (schema.org). Widespread does not automatically mean used correctly, though. Some themes and extensions write a WebSite block with the page title as the name, and a second extension adds another one. Google advises nesting the site name properties in the existing WebSite node and not creating an additional block when it can be avoided (Google Search Central).
If the home page exists in several versions, for example under HTTP and HTTPS or with and without “www”, all of them should carry the same structured data, not just the canonical version (Google Search Central). You can check the markup with a schema testing tool such as the Schema Markup Validator; the Rich Results Test does not support site names (Google Search Central). If you also use structured data for other result types, the basics are covered in our article on rich results and structured data.
Naming title, og:site_name and H1 consistently
The markup is the most important signal, but not the only one. Google explicitly asks you to use the site name consistently on the home page: the name in the structured data should match how the home page refers to the website in the other places the system considers (Google Search Central). In practice, that means laying markup, og:site_name, title and the visible main heading side by side.
| Signal | Place in the source code | Correct (example) | Typical mistake |
|---|---|---|---|
| WebSite markup | JSON-LD in the head | name: Sample Heating | page title as the name, second block added by an extension |
| og:site_name | meta tag in the head | Sample Heating | missing or still carries the old business name |
| title | title element of the home page | Sample Heating: Boilers, Bathrooms and Servicing | “Home” or “Start page” |
| H1 | visible main heading | Sample Heating | “Welcome” as the only large heading |
og:site_name comes from the Open Graph protocol, which was originally designed for previews when content is shared. There it is an optional property: four other properties are required for every page (Open Graph Protocol), and og:site_name gives the name of the larger website an object belongs to (Open Graph Protocol). Because Google's site name system reads the field as well, it pays to fill it on the home page with exactly the name you want.
<head>
<title>Sample Heating: Boilers, Bathrooms and Servicing</title>
<meta property="og:site_name" content="Sample Heating">
<link rel="icon" href="/favicon.ico" sizes="48x48">
<link rel="icon" href="/favicon-96.png" type="image/png" sizes="96x96">
<link rel="apple-touch-icon" href="/apple-touch-icon.png">
</head>For the title element of the home page, Google advises against vague descriptions such as “Home” and names the home page as a good place for additional information about the site (Google Search Central). On subpages, the site name can appear at the beginning or end of the title, separated by a hyphen, colon or pipe (Google Search Central). For domain-level site names, if this addition matches the name already shown in the result, Google may omit it from the title link so the name does not appear twice (Google Search Central). The H1 of the home page is not a dedicated field for the name, but it is one of the headings the system evaluates; a large “Welcome” wastes that spot.
alternateName: short form and fallback
The preferred name does not come through in every case. For that situation there is the alternateName property, which schema.org defines as an alias for the item (schema.org). Google evaluates it for site names: you can provide several alternative names in order of your preference, the most important first (Google Search Central). Typical candidates are a common acronym, a shorter form of the name or the name without the trade description. Some businesses are recognized more often by an abbreviation than by their full name; the documentation names this case explicitly as well (Google Search Central).
As a last step, the domain name itself can be added as an alternative. It must be written in lowercase, so example.com rather than Example.com, for the system to recognize it as a preference (Google Search Central). If that does not help either, the domain name can be the preferred name in the name field; Google explicitly describes this as the last resort (Google Search Central).
Domain as the name: when it fits
The favicon: size, format, implementation
The favicon is the small icon next to the site name. For Google to show it, add a link element to the head of your home page (Google Search Central). As rel values, Google supports icon, for historical reasons also shortcut icon, plus apple-touch-icon and apple-touch-icon-precomposed (Google Search Central). The address in href can be relative or absolute and does not need to be hosted on your own site; a content delivery network works too (Google Search Central). This flexibility has applied since February 23, 2023, when Google removed the hosting location requirement from the documentation (Google Search Central).
Fixed requirements apply to the file itself. It must be square, with a 1:1 aspect ratio, and at least 8 × 8 pixels (Google Search Central). At least 48 × 48 pixels is recommended so that the icon looks good on various surfaces (Google Search Central). And it must be in one of the seven supported formats: BMP, GIF, ICO, PNG, JPEG, PPM or TIFF (Google Search Central). The size requirements have been in the documentation in this form since October 24, 2024 (Google Search Central). Even when all requirements are met, Google does not commit to showing a favicon (Google Search Central).
The format list has only been written out in the documentation since August 28, 2026. Before that, Google linked to an external reference that evolved over time; according to the changelog, the supported formats did not change, they are now simply listed explicitly (Google Search Central). For practical work the list is still revealing, because SVG and WebP are not on it. A pure SVG favicon, as modern browsers like to use, should therefore get a PNG or ICO file alongside it.
In terms of design, the favicon should be a visual representation of the website's logo so that people can quickly identify the site when scanning results (Google Search Central). A business name written out in full is barely legible at this size; a brand mark or a single letter on a surface in the house color works better. If no such mark exists yet, it is worth creating together with the rest of the web design. The file address should stay stable (Google Search Central). That mainly affects build processes that append a new hash to every file name with each release.
Favicon in a subdirectory and other pitfalls
Google supports only one favicon per site, where a site is defined by the hostname (Google Search Central). www.example.com and code.example.com are two different hostnames and can have two icons; www.example.com/sub-site, on the other hand, is a subdirectory and shares the favicon of the home page (Google Search Central). If you run an online shop with its own logo under /shop/ and only add a link element there, the shop gets no icon of its own in search. The home page of the hostname is what counts.
Crawler access matters just as much. Googlebot must be able to crawl the home page and follow any redirects to the page where the favicon is specified, and Googlebot-Image must be able to crawl the favicon file (Google Search Central). None of these URLs may be blocked from crawling by robots.txt or by other means (Google Search Central). A robots.txt file that blocks the /assets/ directory for all crawlers, for example, also prevents the icon from appearing in search.
Browsers behave differently from Google here. If there is no link element with icon, the HTML standard allows them to look for /favicon.ico in the root directory on their own (WHATWG HTML Standard). An icon in the browser tab therefore does not prove that the home page declares it correctly. If several equally appropriate icons are provided, browsers use the last one declared (WHATWG HTML Standard). For Google, what counts is the declaration on the home page and whether the file can be reached.
- link element only on subpages or in the shop directory, not on the home page
- favicon file or home page blocked by robots.txt
- home page redirects to a target that Googlebot cannot reach
- only an SVG favicon without a version in a supported format
- non-square file, such as a wide logo with lettering
- changing file names because the build sets a new hash with every release
Subdomains, www and language versions
Site names follow a similar boundary to favicons, only at the level of domain and subdomain: Google currently supports one site name per site, and subdirectories do not get their own (Google Search Central). Subdomains starting with www or m are generally considered equivalent (Google Search Central). A subdomain such as news.example.com, on the other hand, can carry its own name. If its home page has no structured data, Google can use the domain-level site name as a fallback for the subdomain (Google Search Central).
For multilingual websites with folders such as /de/ and /en/, this means both language versions share one site name and one favicon. The name should therefore work in both languages, which is usually the case with a brand name anyway. “Sample Heating” reads as a name in either language, whereas a long descriptive sentence in one language looks out of place in the other. How to structure and connect language versions otherwise is covered in our article on multilingual websites and hreflang.
Redirects play a part as well. If the home page redirects to a page that is visible to Googlebot, the site name corresponds to the redirect target (Google Search Central). Moving to a new domain does not carry the name over automatically; it has to be stated again on the new home page. The full process of such a move is described in our article on a new domain with a redirect plan.
After the change: check and allow time
Once markup, meta tags, titles and favicon are adjusted, compare the result with what Google sees. With the URL Inspection tool in Search Console you can test whether the home page is accessible to Google and not blocked by robots.txt, noindex or a login (Google Search Central). You can then request indexing of the home page there. This requires you to be an owner or full user of the property, there is a quota for individual URLs, and requesting a recrawl multiple times does not speed it up (Google Search Central). If Search Console is not set up yet, the steps are in our article on how to set up Search Console.
Then it takes patience. Until Google has recrawled and processed the home page, anywhere from several days to several weeks can pass, depending on how often the system determines the content needs to be refreshed (Google Search Central). If the home page already shows the new name but subpages do not yet, that is not an error: the internal pages also have to be recrawled and processed first (Google Search Central).
- Decide on the preferred name and short form and agree on them internally
- Add WebSite markup to the home page or extend the existing block
- Align og:site_name, title and H1 of the home page
- Store a square favicon as PNG or ICO at 48 × 48 pixels or more and link it on the home page via a link element (Google Search Central)
- Check robots.txt for blocks on the home page and the favicon file
- Check the markup in the Schema Markup Validator and submit the home page in the URL Inspection tool
- After a few weeks, review the results for brand and service queries
Whether the new name also translates into clicks on brand queries can be monitored with the branded queries filter in Search Console. How to separate branded and non-branded queries is explained in our article on branded queries in Search Console.
Name and icon as part of website maintenance
Site name and favicon are quickly set up and just as quickly lost. A theme update overwrites the title of the home page, a new SEO extension adds a second WebSite block, during a relaunch the favicon moves into a directory that robots.txt blocks. None of these changes announces itself with an error message; it only becomes visible weeks later in the search results. That is why the name signals on the home page and the favicon belong on every checklist after updates and before every website relaunch. Which other points cost rankings during a relaunch is shown in our article on a website relaunch without ranking loss.
In our website care service, every update is tested on a staging environment before it goes live. That is the right moment to also check the structured data, meta tags, title, favicon and robots.txt of the home page. As part of our search engine optimization, we compare which name Google actually displays and adjust alternateName if the preferred name does not come through. If you want an overview of the fundamentals first, start with the SEO basics for businesses.
Related Articles
Structured Data: Win More Clicks with Rich Results
Schema.org and JSON-LD explained in plain terms: how structured data makes your pages appear as rich results with stars, prices and questions in Google.
Set up Search Console: choose and verify your property
Setting up Search Console: domain or URL-prefix property, verification by DNS, file or meta tag, roles for business and agency, sitemap and email alerts.
Branded or not: separating queries in Search Console
Search Console's filter separates branded from non-branded queries: what it counts, when it is missing, limits, a regex cross-check and year-over-year analysis.