The Internet Marketing Driver

  • GSQi Home
  • About Glenn Gabe
  • SEO Services
    • Algorithm Update Recovery
    • Technical SEO Audits
    • Website Redesigns and Site Migrations
    • SEO Training
  • Blog
    • Web Stories
  • Contact GSQi

Favi-gone: 6 Reasons Why Your Favicon Disappeared From The Google Search Results [Case Studies]

February 22, 2022 By Glenn Gabe Leave a Comment

Share
Tweet
Share
Email
19 Shares
favicons in Google Search

Update: October 20, 2022
Google confirms there is a bug with favicons not showing up in the search results for some sites.
Update: October 26, 2022
Google confirms they have fixed the favicon bug.

———————-

They say “a favicon is worth a thousand words”. OK… they really don’t say that, but favicons can definitely be important from a Search perspective. In 2019, Google started displaying favicons in the mobile search results as part of a mobile redesign, and it ends up that those little graphics in the SERPs can sure help on several levels. For example, a favicon can help reinforce your brand, it can attract eyeballs in a crowded SERP, and it can also help with click-through rate. So you definitely want to make sure your favicon game is strong.

Favicons in the Google search results.

Google published guidelines for defining a favicon in order to make sure they can be properly displayed in the SERPs. If you don’t adhere to those guidelines, Google can choose to ignore your favicon and provide a generic one for you. And there’s nothing more “meh” than the generic globe favicon Google provides. Let’s just say you won’t stand out in the SERPs with their generic favicon showing…

Generic favicon in Google search results.
Generic globe favicon in the Google search results.

In addition, you can end up with a blank favicon, which is super-awkward. The space for the favicon is reserved, but nothing shows up. It’s a just a blank white space where a favicon should appear. So sad… and I’ll explain more about that later in the post.

Blank favicon in the Google search results.

Here is another example of a blank favicon (and not just the generic globe favicon):

Missing favicon in the Google search results.

Favicon Assistance: When site owners reach out about favicon problems.
Every now and then I have site owners reaching out in frustration when their favicons go missing from the search results. When that happens, it can be a very confusing situation for those site owners… Well, I recently just helped a few more site owners over the past few weeks troubleshoot favicon problems in the search results. And based on what I found, I figured I would write a post explaining some of the top reasons I’ve seen that cause favicon problems in Google Search.

The problems are relatively easy to fix and changes can be picked up by Google pretty quickly for most sites. For example, one of the latest fixes I helped with was picked up in just a few hours and the SERPs were updated in less than a day (with the new favicon).

Here is a quick table of contents if you want to jump to specific sections:

  • Favicons disappearing and questions about quality.
  • Wrong dimensions for the favicon.
  • Robots.txt blocking the favicon.
  • Duplicate favicon references and one didn’t meet the requirements.
  • Location of the favicon image file.
  • Empty favicon code.
  • Platform or CMS botched the favicon.
  • Bonus 1: Don’t push the limits with your favicon.
  • Bonus 2: Creating an adaptive favicon that works well in dark mode.
  • October 20, 2022 – Confirmed bug.
  • October 26, 2022 – Google confirms bug has been fixed.
  • Frequently Asked Questions (FAQs)

Favicons Disappearing and Questions About Quality:
When favicons go missing, some site owner immediately jump to thinking that Google somehow doesn’t trust their site  anymore or that there are quality problems causing Google to stop displaying their favicons (like how rich snippets can be impacted by broad core updates). That’s not the case. Favicons going missing in the SERPs have nothing to do with site quality. Instead, it has everything to do with technical problems with the favicons, or violating Google’s guidelines for providing favicons.

So if your favicon goes missing, it’s not that Google has suddenly reevaluated your site quality-wise. It’s probably due to technical issues or other guideline violations (which I’ll cover below). 

Where did your favicon go? Troubleshooting common favicon problems in Google Search.
Below, I’ll cover several common problems I have seen while helping site owners troubleshoot favicons that disappear from the search results (or favicons that just aren’t displayed properly by Google).

1. Wrong dimensions, no favicon for you…
This is the  most common issue I have seen. Google has explained in detail that favicons must be a multiple of 48×48 pixels. So, make sure your favicon is at least 48×48 or a multiple of 48×48. For example, 96×96, 144×144, etc. Don’t have a favicon that’s smaller than 48×48.

Favicon dimension guidelines from Google.

For example, a site used the following image as its favicon (blurred to avoid calling out the site). It was 50×50 and not a multiple of 48×48 pixels. Google just used the generic globe favicon. Again, meh in the SERPs.

Favicon with the wrong dimensions.

Also, the aspect ratio is important. If it’s not a square, it’s not going to work well. I’ve seen favicons that looked out of whack from an aspect ratio standpoint, or they just didn’t show up in the SERPs. For example, a site used the favicon below, which didn’t have a square ratio. Google forced it to fit the required aspect ratio (and it looked totally warped in the SERPs). Beware.

Favicon with the wrong aspect ratio.
Example of favicon with the wrong aspect ratio in the Google search results.

A note about favicon format: You have plenty of options:
Your favicon doesn’t have to be in the .ico format. It can be in any supported format, such as jpg, gif, png, and svg. I’ll cover more about svgs later in the post.

Favicon image formats.

2. Robots.txt blocking the favicon:
Google’s documentation states that you should allow crawling of your favicon and your homepage in order for the favicon to be used in Search. If your homepage is blocked by robots.txt, you clearly have bigger issues to worry about than just the favicon. :) But the favicon location could cause problems and be confusing from a robots.txt perspective. For example, some directives in robots.txt can be “greedy” and block more than you think.

I recommend using the robots.txt Tester in Google Search Console to make sure your favicon and homepage can be crawled. It’s a quick test and can save you some frustration. For example, here is a site with a missing favicon and it’s blocking access to the favicon. It’s a bigger brand by the way, so yes, larger companies can make this mistake too.

Favicons and robots.txt problems.

And here’s an interesting side note. Google has a specific crawler for favicons called Google Favicon. You can check the Googlebot documentation for the user-agent string. Google will use this crawler to check your favicon when you request indexing of your homepage via Google Search Console (GSC). And the crawler will ignore robots.txt directives when someone requests a recrawl of the homepage based on a favicon change.

For example, this is directly from the favicon documentation:
“The Google Favicon crawler ignores robots.txt rules when the crawl was requested by a user.”

And here is the crawler user-agent:

Google Favicon user-agent (crawler).

But again, that’s just for Google Favicon to check the new favicon. You still should enable crawling of your homepage and your favicon if you want it to be used in the search results.

3. Duplicate favicon references and one didn’t meet Google’s favicon guidelines:
This is similar to the first issue I covered, but it includes duplicate favicon references in the homepage code (and one didn’t meet the guidelines). I’ve seen situations where one, or more, of the favicon references are to files that don’t meet the requirements and Google just displayed the generic globe favicon instead in the SERPs. So just make sure to double-check all of the references to your favicon from your homepage and make sure they are ok.

For example, this site’s favicon wasn’t showing up correctly. It ended up the homepage had multiple rel=“icon” references and one didn’t meet Google’s guidelines. Fixing that by just having one rel=”icon” reference pointing at the proper file enabled the site to regain its favicon in the SERPs:

Multiple favicon references causing problems.

4. Location of the favicon image file:
Another problem I have seen that causes issues with favicons is the location of the image file used for the favicon. Google’s documentation explains that the URL of the favicon must be in the same domain as the homepage of the site. So, if your site is example.com, then the favicon must reside on example.com. If you place the favicon at another-example.com, then that can cause problems and Google can end up showing the generic globe icon. This is clearly easy to fix, since you just need to move the image file to your core domain and change your favicon code to point to the new file.

The location of your favicon is important.

5. Uh, empty favicon code…
Yes this seems obvious, but I’ve unfortunately seen it in action. If you literally leave out the file in the favicon code, then you will obviously have favicon problems in Search. :) So if you are experiencing favicon problems, then definitely double-check your code. And I also recommend using the various testing tools from Google to check both the static html and the rendered html to make sure your code is correct.

Empty favicon code.

6. Your platform or CMS is botched favicon-wise.
For sites that use a specific platform or CMS to run their site, they may be in a situation where they can’t easily set or customize their favicon. And in situations where you don’t have much control, you are relying solely on the platform or CMS to get it right. And as you can guess, that doesn’t always work out well.

And yes, that means all sites using that platform could have favicon problems. I surfaced this problem recently for a smaller e-commerce platform. Google just isn’t replacing the favicon with the generic globe, it’s literally leaving the favicon blank! This is even worse than receiving the generic favicon in my opinion…

CMS platform causing favicon problems.

And when performing a query that brings up many sites using the platform, you can see the widespread problem. Yep, that’s all of the sites on the platform with missing favicons (not even the generic favicon). And look at the second listing in the SERP… the aspect ratio is messed up for the favicon. So we have a mix of blank favicons and one warped one. Not good.

All sites running the same platform having favicon problems in the Google search results.

Bonus 1: Don’t push the limits with your favicon.
In its documentation, Google has explained that it won’t show any favicon that it deems inappropriate (like pornography or hate symbols). If that’s the case, Google will simply provide the default, generic favicon. Just keep this in mind when crafting a favicon… I’m sure this won’t impact most sites, but it can clearly cause issues with your favicon displaying properly in the SERPs.

Here is what Google explains in their favicon documentation:

Google guidelines for favicons and inappropriate images.

Bonus 2: Create an adaptive favicon that works well in dark mode.
People love dark mode and that includes Google Search. But I find many don’t test how their favicon displays in dark mode.

Once you check out your favicon in dark mode, and if you think it looks less-than-optimal, then you can always create an adaptive favicon that looks great in both light and dark mode. For example, creating an SVG that uses media queries to ensure your favicon adapts to the current environment (light mode versus dark mode).

Adam Argyle wrote a post explaining how to create an adaptive favicon on web.dev where he walks you through the process of creating an SVG that can change based on light versus dark mode. I haven’t tested it out yet, but it’s an interesting technique that seems to work well in the demo. I might try doing that in the near future.

Adaptive favicons

Summary: Put your best favicon, I mean foot, forward in Search with one that actually shows up.
I hope this post helped you understand some of the most common favicon problems I’ve seen while helping site owners that reached out to me for help. With favicons being displayed prominently in the mobile search results, you don’t want a less-than-optimal favicon staring users in the face. And you also don’t want the “meh” generic favicon that Google can provide, or worse, a blank favicon. A few minutes of digging into the situation can usually surface the core favicon problem. And once fixed, you can finally have a favicon that works for you instead of against you. Good luck.

GG

Back to top>>

Update: October 26, 2022 – Google fixes favicon bug.
Google recently explained it was working on a fix based on the favicon bug that resulted in some sites losing their favicons around 9/18/22 (and the generic globe favicon being used instead). Well, the problem has been resolved! That’s great news for any site that was impacted by the bug (especially as the new site name treatment is coming to desktop soon — which includes favicons). I can confirm the bug has been fixed since I checked several sites that were impacted, and their favicons are indeed showing up normally now. Also, Google’s John Mueller confirmed on Twitter that the problem should be resolved. Again, great news for any site impacted.

Big heads-up. If you have been struggling with the favicon bug where Google stopped using your favicon around 9/18, I have incredible news. The bug was fixed last night & favicons have returned for sites that were impacted. Here are two examples (before and after screenshots): pic.twitter.com/8qUKyopp1q

— Glenn Gabe (@glenngabe) October 26, 2022

Update: October 20, 2022 – Google confirms favicon problem.
Google has confirmed there is a problem on their end with displaying favicons for certain sites. They did not explain what the problem is, but they did say they are working on resolving the issue. Google did not provide a timeframe for the fix. Google’s John Mueller explained this in a tweet after being asked about the recent favicon problems. Note, the problems started around 9/18, right after the September 2022 broad core update started rolling out. I have no idea if they are connected, but it’s worth noting. I will update this post when the problem is resolved.

We've looked into it, and the team has been working on resolving this, but afaik it's more of a niche issue. (Also, I wouldn't assume that Google sites get SEO right automatically, we're people too :-))

— John Mueller is watching out for Google+ 🐀 (@JohnMu) October 19, 2022

Back to top>>

Frequently Asked Questions:

Q: Why is Google showing a generic globe icon as my favicon?

A: Google has a specific set of guidelines for providing a favicon file. If your favicon is not meeting those requirements, then Google can ignore your favicon and provide a generic globe icon in the search results. There are several reasons this could be happening.

Q: Is there an image format that’s better for Google?

A: Any of the supported file formats can be used. One is not better than another when it comes to showing up in the Google search results. For example, you could use a jpeg, png, gif, ico, svg, etc.

Q: Are the size and dimensions of the favicon file important?

A: Yes, the dimensions of your favicon are extremely important. Google explains in its documentation that the favicon must be a multiple of 48 pixel square. For example, 48×48, 96×96, etc. Your favicon file must be at least 48x48px.

Q: Does the location of the favicon file matter?

A: Yes, Google explains that the favicon file must reside on the same domain as the homepage. So don’t host the favicon file on a third-party domain.

Q: Is it ok to block the favicon file via robots.txt?

A: No, Google needs to crawl the favicon file and the homepage in order for it to be shown in the search results. Make sure your robots.txt directives are not blocking the homepage or the favicon file.

Back to top>>

Share
Tweet
Share
Email
19 Shares

Filed Under: google, seo

Connect with Glenn Gabe today!

Latest Blog Posts

  • Continuous Scroll And The GSC Void: Did The Launch Of Continuous Scroll In Google’s Desktop Search Results Impact Impressions And Clicks? [Study]
  • How to analyze the impact of continuous scroll in Google’s desktop search results using Analytics Edge and the GSC API
  • Percent Human: A list of tools for detecting lower-quality AI content
  • True Destination – Demystifying the confusing, but often accurate, true destination url for redirects in Google Search Console’s coverage reporting
  • Google’s September 2022 Broad Core Product Reviews Update (BCPRU) – The complexity and confusion when major algorithm updates overlap
  • Google Multisearch – Exploring how “Searching outside the box” is being tracked in Google Search Console (GSC) and Google Analytics (GA)
  • Sitebulb Server – Technical Tips And Tricks For Setting Up A Powerful DIY Enterprise Crawler (On A Budget)
  • Google’s Helpful Content Update Introduces A New Site-wide Ranking Signal Targeting “Search engine-first Content”, and It’s Always Running
  • The Google May 2022 Broad Core Update – 5 micro-case studies that once again underscore the complexity of broad core algorithm updates
  • Amazing Search Experiments and New SERP Features In Google Land (2022 Edition)

Web Stories

  • Google’s December 2021 Product Reviews Update – Key Findings
  • Google’s April 2021 Product Reviews Update – Key Points For Site Owners and Affiliate Marketers
  • Google’s New Page Experience Signal
  • Google’s Disqus Indexing Bug
  • Learn more about Web Stories developed by Glenn Gabe

Archives

  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • August 2021
  • July 2021
  • June 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • December 2018
  • November 2018
  • October 2018
  • September 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • August 2016
  • July 2016
  • June 2016
  • May 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • July 2015
  • June 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • December 2014
  • November 2014
  • October 2014
  • September 2014
  • August 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • December 2012
  • November 2012
  • October 2012
  • September 2012
  • August 2012
  • July 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • GSQi Home
  • About Glenn Gabe
  • SEO Services
  • Blog
  • Contact GSQi
Copyright © 2023 G-Squared Interactive LLC. All Rights Reserved. | Privacy Policy
This website uses cookies to improve your experience. Are you ok with the site using cookies? You can opt-out at a later time if you wish. Cookie settings ACCEPT
Privacy & Cookies Policy

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience. You can read our privacy policy for more information.
Cookie Consent