Why your favicon isn't showing and how to check
You added an icon, reloaded the page, and the tab shows the old picture or nothing. The cause is usually one of a handful of things. Check them in this order.
First check: the file isn't where the page says it is
Open the icon's own address in a new tab, such as yoursite.com.au/favicon.ico with your own domain. If you see the picture, the file is there. If you see an error page, the file is missing, misnamed or in the wrong folder. Fix that first, because nothing else matters until the file loads.
Next: the link tag is missing or in the wrong place
View the source of your page and look in the head for a link line with rel="icon". The way to write it is on the adding a favicon page.
Two icons can confuse things. Say your HTML names one file and an older favicon.ico sits at the top of your site. Wikipedia says modern browsers will choose the linked favicon instead of the one in the root.1
The HTML standard adds a rule for several equally good icons. It says user agents must use the last one declared in tree order.2 A "user agent" is just the browser, and "tree order" means the order the lines appear in your page. So the last matching line wins.
Then: the declared sizes don't match the file
A link tag can carry a sizes attribute. MDN says each of the sizes listed must be contained in the resource.3 If your tag lists a size the file doesn't hold, remove the attribute or correct it.
Then: something is blocking the file
A security header called a Content Security Policy can stop the icon loading. MDN's advice is to check that the img-src directive in the Content-Security-Policy header isn't blocking it.3
For Google, blocking is a separate problem. Googlebot's crawl of your pages and icon file must not be blocked from crawling by robots.txt or other means.4 The robots.txt file is a plain text file at the top of your site that tells crawlers where they may go.
If you manage a firewall, a login wall or a hosting setting, note the existing settings before changing anything. Then follow your own provider's help pages.
Often: the browser is showing a saved copy
MDN says HTTP is designed to cache as much as possible, so even if no Cache-Control is given, responses will get stored and reused if certain conditions are met.5 Icons are files like any other, so a saved copy may stay in use.
MDN also explains that the fresh state usually indicates a saved response is still valid and can be reused.5 The HTML standard says browsers are not required to update icons when the list of icons changes, though they're encouraged to.2
So the old icon can hang around. Try the page in another browser, or on your phone's mobile data, to see the new one. If another browser shows the new icon, a saved copy in the first browser is a likely cause.
One habit helps next time. Google says the favicon URL must be stable and you shouldn't change it frequently.4 Pick a file name you can keep.
Last: it shows in the tab but not in Google
Google runs on a slower clock than your browser. Its own page puts the wait at anywhere from several days to several weeks.4 The full list of Google's conditions is on favicons in Google Search results.
Still stuck?
Go back to the first check and test the file again from a fresh tab. Small mistakes hide well: a capital letter in a file name, a missing slash, a file saved in the wrong folder. If you're using a website builder, its help pages will say where the icon setting lives and how long a change takes.
Notes and sources
- Favicon, Wikipedia
- HTML Standard, link type icon, WHATWG
- <link>: The External Resource Link element, MDN Web Docs
- Define a favicon to show in search results, Google Search Central
- HTTP caching, MDN Web Docs