Favicon Checker

The common causes: the only declared icon is an SVG, which every modern browser shows and Google Search does not support; the declared icon returns a 404; robots.txt blocks Googlebot-Image from the icon file; or Google has not recrawled your homepage since you added it. Google reads the favicon from your home page specifically, so declaring it only on inner pages will not work. Format, size and 404s are what this tool checks; recrawl delay you can only wait out.

Google needs a square icon of at least 8x8 and recommends larger than 48x48 so it looks good across its surfaces - 96x96 or 192x192 is a safe choice. Browsers are far less demanding and will happily use a 16x16 .ico. Serve one large square PNG and let clients scale it down; add an SVG alongside it if you want one for browsers, but Google Search will not use it.

It is worth keeping one at the root. Browsers and crawlers request /favicon.ico by default whether or not you declare anything, so an absent file means a stream of 404s in your logs and a fallback icon in older clients. Declare a large PNG in your HTML for everything that reads the markup (an SVG alongside it is fine for browsers), and leave an .ico at the root for everything that does not.

Nearly always a path problem. A relative href resolves against the current page, so an icon declared as "favicon.ico" works at the root and breaks on every nested route. Use a root-relative path (/favicon.ico) or an absolute URL. The other common cause is a build step that does not copy the icon into the deployed output - the tag ships, the file does not, and the result is a declared icon that 404s.