You search your own brand on your phone. The result sits at the top, ranking exactly where it should, and yet something looks wrong. The name printed above the headline reads “Home,” or just the bare domain, instead of your company. Where a small icon should sit, there is a plain gray globe. You open the page, scan the copy, check the meta description, and everything reads clean. Nothing you change inside that article moves either element, because neither one is decided inside the article. They are decided at the level of the whole site, from signals most publishers never set on purpose.
Two of the first things a searcher sees are the site name and the favicon. Both load before a single word of your content is read. This is a look at where those two elements come from, what Google’s own documentation says controls them, and what to check when the wrong name or a blank icon shows up.
The two elements Google shows before the headline #
Every result carries a small identity strip. On a phone, that strip pairs a favicon with the site name, then the title link sits underneath. Google’s documentation describes the site name as the name of the site a page comes from, and states it appears in all languages where Search is available, on both mobile and desktop. The favicon is the small square icon that sits beside the result.
Here is the part that trips people up. Both are site-level signals, not page-level ones. A blog post cannot declare its own site name, and a product page cannot declare its own favicon. Google resolves both at the hostname and home page level, then reuses that answer across every URL on the site. So the fix for a wrong name is never in the ranking page. It is on the home page and in the site’s markup.
How Google decides your site name #
Google states the process is completely automated. It takes into account content from a site’s home page and references to that site that appear across the web. You do not submit a site name and receive approval. You supply signals, and the system picks.
Those signals are read in a rough order of weight. According to Google’s site names documentation, the sources it considers include:
- WebSite structured data on the home page, described as the most important source if you want to state a preference.
- Open Graph data, specifically the
og:site_namevalue. - Home page text, including the
<title>element, heading elements, and other content on the page.
The structured data itself is small. The WebSite type needs two properties, a name and the home page url, plus an optional alternateName for a commonly used acronym or shorter form. That alternate matters more than it looks. Google’s guidance says that when its system is less confident in the name you provided, it may fall back to other sources or show a domain or subdomain instead, and the alternateName gives it a second acceptable option before it reaches for the raw domain.
Two limits are worth pinning down. The markup only needs to live on the home page, and Google supports one site name per site. It does not support site names at the subdirectory level, so example.com/news cannot carry a name separate from example.com. Subdomains are treated as their own sites, though names starting with www or m are generally treated as equivalent.
The favicon rules that actually decide whether yours shows #
The favicon has a tighter, more mechanical checklist, and most missing icons fail one specific item on it rather than all of them. Most of it is mechanical. Google’s favicon documentation is direct about the shape and delivery of the file.
- Shape and size. The image has to be a square, a 1:1 aspect ratio, at least 8×8 pixels. Google recommends going larger than 48×48 pixels so it holds up across different surfaces.
- Format. Any valid favicon format is supported, so the older
.icofile and a modern PNG both qualify. - Declaration. A link element in the home page head points to the file, using
rel="icon". Google also accepts the historicalshortcut icon, along withapple-touch-iconandapple-touch-icon-precomposed. - One per hostname. A site, defined by hostname, gets one favicon. A subdomain can differ from the main domain, but a subdirectory cannot have its own.
- Crawlability. Googlebot-Image has to be able to fetch the favicon file, and Googlebot has to be able to fetch the home page. If either is blocked in robots rules, the icon will not appear.
- Stable URL. The favicon URL should not change often, because a moving target resets the discovery clock.
Timing catches people out. Google allows several days to several weeks to recrawl and reflect a new or changed favicon, so an icon that is correct today can still be blank in results next week without anything being broken. And even a file that passes every rule carries no promise. Google’s documentation says a favicon is not guaranteed to appear even when all guidelines are met, and it will replace an image it deems inappropriate, such as hate symbols, with a default icon.
When the wrong name or a blank icon shows up #
Most of these problems trace back to a small number of causes. Matching the symptom to the likely cause narrows the fix before you start editing files.
| What you see | Likely cause | What tends to resolve it |
|---|---|---|
| Bare domain instead of your brand name | No WebSite structured data, or weak and inconsistent home page signals | Add WebSite structured data with a name and url on the home page, and keep the title and og:site_name consistent with it |
| A different name than the one you set | The system is less confident in your name, or references across the web point elsewhere | Provide an alternateName, align the title and Open Graph name, then request a recrawl |
| Gray globe, no favicon | File blocked from crawling, not square, an unstable URL, or simply not recrawled yet | Confirm a rel="icon" link in the head, a square file above 48px, and that Googlebot-Image can reach it |
| An old favicon still showing | Cached result, a changed favicon URL, or a pending recrawl | Hold the favicon URL steady, request a recrawl, and allow days to weeks |
| Favicon swapped for a generic icon | Google could not fetch the file, or judged the image unsuitable | Check that the file returns successfully, is not blocked, and represents the brand plainly |
The single most useful move across almost all of these is the URL Inspection tool in Search Console. It lets you request that Google recrawl the home page after you change the markup, which shortens the wait between a fix and the next crawl. Google is explicit that it cannot manually change an automatically selected site name for you, so the lever is always the signals plus a fresh crawl, not a support request.
What you can influence, and what you cannot #
It helps to be honest about the boundary. You do not control the output. You control the inputs, and then an automated system reads them.
What sits inside your hands is concrete: a clean WebSite block on the home page, a consistent name across the title, Open Graph, and structured data, a square favicon above 48 pixels declared in the head, and crawl access for both Googlebot and Googlebot-Image. What sits outside your hands is the final call and the timing. Google may still show a domain if its confidence is low, may take weeks to recrawl, and offers no guarantee that a compliant favicon appears at all. The realistic goal is not to force a result. It is to remove every reason for Google to pick something worse.
FAQ #
Where do I set my site name and favicon? On the home page, not inside individual posts or product pages. Both are resolved at the site and hostname level, so home page markup and a home-page-referenced favicon file drive what shows across the whole site.
Why does Google show my domain instead of my brand name? That fallback points to a system that was not confident enough in the name you set, or that found conflicting signals across the web. Adding WebSite structured data with a clear name, plus an alternateName, and aligning the title and Open Graph name gives it a stronger, single answer to choose.
How long until a new favicon appears? Google’s documentation states it can take several days to several weeks, because the icon updates on the next recrawl of the home page rather than instantly. Keeping the favicon URL stable and requesting a recrawl shortens the gap.
Can my subdomains have different favicons or names? Yes. A site is defined by hostname, so a subdomain can carry its own favicon and its own site name. A subdirectory cannot, because it shares the hostname of its parent.
My favicon meets every rule and still is not showing. Is something broken? Not necessarily. Google states a favicon is not guaranteed to appear even when all guidelines are met, and recrawling takes time. If the file is square, crawlable, stable, and declared with a valid rel, the common remaining factors are the crawl schedule and Google’s own discretion.
Run the search you started with one more time, but this time look at your home page instead of the ranking article. That is where the name and the icon are decided. A small WebSite block, one consistent brand name across your title and Open Graph, and a square favicon that Google can actually crawl will cover the signals that matter. After that, the only thing left to do is hold the URLs steady and give the next crawl room to catch up.