Favicon Not Showing in Google: Redirects and Blocked Crawlers

In this article
A favicon not showing in Google almost always means one of three things broke. The home page has to link an icon with a supported rel value. Googlebot has to be able to crawl that page and follow its redirects. And Googlebot-Image has to be able to fetch the icon file. Even with all three in place, Google doesn’t promise to show a favicon, so the goal is to remove every reason it has to skip yours. The checks below tell you whether the HTML or the server is to blame.
What are Google’s favicon requirements?
Google needs a link tag in the head of your home page, pointing to a square image in a format it supports. Its guide on defining a favicon for search results gives the syntax as <link rel="icon" href="/path/to/favicon.ico">. The image has to be 1:1 and at least 8x8px. Google recommends going bigger than 48x48px so the icon stays sharp wherever it’s shown.
- rel values: icon (shortcut icon still works, for historical reasons), apple-touch-icon or apple-touch-icon-precomposed.
- href: relative or absolute URL, either works. The file can live on a CDN instead of your own host.
- Formats: BMP, GIF, ICO, PNG, JPEG, PPM and TIFF.
- Stable URL: don’t change the icon address with every redesign.
If Google decides the imagery is inappropriate, it replaces it with a default icon, whatever your markup says.
Do home page redirects stop the favicon in search results?
Yes, a broken redirect path can stop the favicon, because Googlebot starts at the home page and has to follow every hop until it reaches the page with the tag. The usual chains are http to https, non-www to www, or the root to a language or country version. Wherever the chain goes, it has to end on a 200 response that contains the link tag. No loops, and no hop that depends on cookies or the visitor’s location: a crawler arrives without cookies, sometimes from a country you didn’t expect, and can land somewhere other than your browser does.
The cleanest fix starts with choosing one host and redirecting the rest. In NGINX, give each alternate host its own server block with one permanent redirect straight to the final https URL. Keep conditional logic such as geo or Accept-Language checks off the root path.
Robots.txt, hotlink rules and bot filters that block Googlebot-Image
Google says the home page, its redirect targets and the favicon file must not be blocked by robots.txt or by anything else. For robots.txt, that means no Disallow line covering the icon path or its image folder, including rules written only for Googlebot-Image.
Server rules are where the quiet failures happen. Referer-based hotlink protection can turn the crawler away, because its request doesn’t arrive with a referrer from your page. Either exempt the icon or follow a pattern for hotlink protection that still lets Google Images in. The same applies to a WAF, a bot rule or a request limit on the origin or proxy: none of them should answer Googlebot-Image with a forbidden or too-many-requests error. The guide to rate limiting bots without slowing Googlebot shows how to keep limits in place without catching crawlers in them.
In NGINX, add a dedicated location = /favicon.ico block (plus one for any PNG icon) that skips the referer and bot checks. The file stays reachable and the rest of the image folder stays protected.
One favicon per hostname: subdomains and site networks
Google supports one favicon per site, defined by hostname. So news.example.com can have its own icon. example.com/news can’t have a separate one, because Google doesn’t support a subdirectory-level home page.
Running a network of domains? Each home page needs its own link tag, though they can all point to one shared icon URL. If the domains sit behind a single reverse proxy such as Jalvo, test every hostname on its own. Redirects and access rules often differ from one server block to the next.
Favicon not showing in Google: how to check the cause
Go from the HTML out to the server, one hostname at a time:
- Fetch the home page with
curl -sL. Make sure the final response is 200 and the HTML contains the link tag. - Request the icon URL with curl twice: once normally, once with a Googlebot-Image user agent. Both should return 200 with an image content type.
- Read robots.txt and look for any rule that matches the icon path or its folder.
- Run URL Inspection on the home page in Search Console, and request indexing after each fix.
- Search the access logs for Googlebot-Image requests to the icon and note the status codes. The walkthrough on reading server logs for crawl problems shows what to filter for.
Recrawling can take anywhere from several days to several weeks, so judge the result after that window, not the next morning.
When the favicon is not showing in Google, the cause is usually the tag, the redirect chain or some rule blocking Googlebot-Image. Fix the server path first and keep the icon URL stable. Then let Google recrawl the home page in its own time.
FAQ
Can I host the favicon on a CDN or another domain?
Yes. Google accepts an href pointing outside your site, CDN included. The condition is that Googlebot-Image can fetch the file there, so check the CDN’s own robots.txt and hotlink settings too.
Does an SVG favicon work in Google Search?
Google lists BMP, GIF, ICO, PNG, JPEG, PPM and TIFF as supported formats. SVG isn’t on the list, so add a PNG or ICO next to it with a supported rel value.
How long until a new favicon appears?
Crawling can take from several days to several weeks. You can request indexing of the home page through URL Inspection. Even when you meet every guideline, Google doesn’t guarantee the icon will show.


