Favicon Not Showing in Google Search? 9 Causes and How to Fix Each
Your favicon shows up fine in the browser tab, but next to your page in Google's results there's a grey globe. That gap is the whole problem: the browser and Googlebot fetch your icon under completely different rules, so a favicon that works in Chrome can still be invisible in search.
Google shows a favicon next to your result only when its own crawler can find, fetch, and validate an icon that meets its published requirements. Miss any one of those and you get the default globe. The good news is the list of things that go wrong is short. In the audits we run, a missing search favicon is almost always one of nine causes below, and most take a few minutes to fix.
Before you change anything, confirm what Googlebot actually sees. Run your homepage through our favicon checker to see which icon Google can fetch, at what size, and whether the URL returns a clean 200. If you want the full background on how favicons and search interact, the favicon SEO complete guide covers the mechanics; this post is the troubleshooting checklist.
First, what Google actually requires
Google's Search Central documentation is specific about favicons, and every fix below maps back to one of these rules:
- The icon must be a multiple of 48px square (48x48, 96x96, 144x144, and so on). A 16x16 favicon that renders in your tab is too small for Google to use.
- It must be referenced from a
<link rel="icon">(orshortcut icon,apple-touch-icon) in the<head>of your homepage, not just deep pages. - The favicon file and the homepage must both be crawlable, not blocked by robots.txt.
- The favicon URL should be stable. Google caches it; a URL that changes every deploy resets the clock.
- The icon should be visually square and recognizable at small sizes.
Now the causes, roughly in the order we find them.
1. The icon is blocked by robots.txt
This is the single most common cause. If your robots.txt disallows the directory the favicon lives in, or blocks Googlebot-Image, the crawler can fetch your HTML but not the icon file itself. A rule as broad as Disallow: /assets/ will silently kill a favicon at /assets/favicon.png.
Check by opening yoursite.com/robots.txt and confirming nothing blocks the favicon's path. If you're not sure your rules do what you think, validate them with our robots.txt generator, and see the robots.txt guide for SEO for how disallow paths are matched.
2. The rel value is wrong or non-standard
Google looks for specific rel values. These work:
<link rel="icon" href="/favicon.png" sizes="96x96" type="image/png">
<link rel="apple-touch-icon" href="/apple-touch-icon.png">
A rel="image_src", a rel="fluid-icon", or a typo like rel="favicon" will render in some contexts but Google won't treat it as a favicon. Stick to icon, shortcut icon, or apple-touch-icon.
3. The favicon is too small
A 16x16 or 32x32 favicon.ico is enough for a browser tab but below what Google will display in search. The requirement is a multiple of 48px, and the practical minimum that looks sharp on modern displays is 96x96 or larger. If your only icon is a tiny .ico, add a larger PNG:
<link rel="icon" href="/favicon-96x96.png" sizes="96x96" type="image/png">
4. There's a redirect on the icon URL
Google wants a direct 200 response. If /favicon.ico 301s to /favicon.png, or your CDN bounces the request through an HTTP-to-HTTPS redirect, the crawler may not follow it for the favicon fetch. Request the icon URL directly and confirm it returns 200 with no hops. Our redirect checker shows the full chain; if you find one, 301 vs 302 redirects explains which status you're dealing with.
5. It's new, and Google hasn't recrawled
If you just added the favicon, patience is part of the fix. Google updates the favicon on its own crawl schedule, and for the homepage that can be days to a few weeks. There is no "submit my favicon" button. You can nudge a recrawl by requesting indexing for the homepage in Search Console (Inspect URL > Request Indexing), but the favicon itself updates whenever Google next fetches the home page and its head.
6. The favicon differs across www and non-www (or HTTP and HTTPS)
Google picks the favicon based on the canonical homepage it indexes. If https://www.example.com has a favicon but your indexed canonical is https://example.com without one (or with a different, broken one), search shows the wrong result. Make the icon identical and present across every host variant, and confirm which version Google treats as canonical. The www vs non-www post covers picking one and redirecting the rest.
7. The tag is injected client-side
If your favicon <link> is added by JavaScript after the page loads, Googlebot may not see it in the initial HTML it fetches. This is common with single-page apps that set the icon in a framework head component that only runs client-side. View the page source (not the rendered DOM) and confirm the <link rel="icon"> is in the raw HTML. If it isn't, move it into the server-rendered head.
8. The image format or MIME type is off
Google supports PNG, ICO, SVG, and a few others, but the server has to return the correct Content-Type. An SVG favicon served as text/html, or a PNG served as application/octet-stream, can fail validation. Also worth knowing: SVG favicons are well supported in current browsers, but if you support older platforms, keep a PNG fallback. For the format tradeoffs, see how to make a favicon.
9. The icon isn't square, or is mostly transparent
Google displays the favicon in a small square. An icon that's wide, mostly empty, or a light logo on a transparent background can render as blank or get rejected. Give it a solid or contrasting background and center the mark so it reads at 16px on a white results page.
A quick diagnostic order
Work top to bottom and stop when you find the break:
| Step | Check | Tool | | --- | --- | --- | | 1 | Does the icon URL return a clean 200? | redirect checker | | 2 | Is the file blocked by robots.txt? | robots.txt generator | | 3 | Is there a 48px+ icon in the raw HTML head? | View source | | 4 | Does Googlebot see the same icon Google shows? | favicon checker | | 5 | Has Google recrawled since you fixed it? | Search Console URL Inspection |
If all five pass and you still see the globe, it's almost always cause 5: you've fixed it and Google hasn't recrawled yet. Give it a couple of weeks after requesting indexing before assuming something's still wrong.
Frequently Asked Questions
How long does it take for a favicon to appear in Google search?
There's no fixed time. Google refreshes the favicon whenever it next crawls your homepage, which can be a few days to a few weeks. Requesting indexing for the homepage in Search Console can speed up the recrawl, but there's no way to submit a favicon directly.
Why does my favicon show in the browser but not in Google?
Browsers and Googlebot fetch favicons under different rules. A 16x16 icon is fine for a tab but too small for Google, which needs a multiple of 48px. The icon also has to be crawlable, referenced from the homepage head, and served with the right content type, none of which the browser tab requires.
What size does a favicon need to be for Google search?
Google requires the favicon to be a multiple of 48 pixels square, so 48x48, 96x96, or 144x144. In practice a 96x96 or larger PNG looks sharp on modern displays. A tiny .ico alone is usually too small.
Can robots.txt block my favicon from Google?
Yes, and it's the most common cause. If your robots.txt disallows the folder the favicon lives in, or blocks image crawling, Google can read your HTML but not fetch the icon. Confirm the favicon's path isn't covered by any Disallow rule.
Do I need a separate favicon for the homepage?
Google reads the favicon from the head of your homepage and applies it across your site's results. The tag should live on the homepage specifically. Having it only on interior pages is a frequent reason the search favicon never appears.