The small icon that shows up everywhere your brand does
A favicon is the tiny icon that represents your site in a browser tab, a bookmark, a history list, and increasingly in search results themselves. It is easy to dismiss as cosmetic, but it is one of the few brand assets that appears the moment someone interacts with your site and keeps appearing every time they return. Google now shows favicons next to results on mobile and in many desktop layouts, so the icon is no longer just decoration in the browser chrome — it is part of how your listing looks in the place where clicks are won or lost. This checker fetches a page, reads the favicon-related link tags in the head, and confirms whether the actual icon files browsers and Google look for exist and respond correctly.
Favicons are deceptively easy to get wrong because there is no single file or single tag that covers every context. Browsers, operating systems, and search engines each look for icons in slightly different ways and at different sizes. A site can look perfectly fine in your own browser, which has cached an icon from months ago, while Google sees nothing and shows a blank globe next to your result. The only reliable way to know is to check what is actually declared and actually served, rather than trusting what you see in your own tab.
What browsers and Google actually look for
There are two layers to favicon delivery. The first is the historical fallback: browsers and Google will automatically request a file named favicon.ico at the root of your domain even if no tag points to it. This is the safety net that has existed since the earliest days of the web, and it is why some sites show an icon without any markup at all. The second layer is explicit link tags in the head that declare icons of specific types and sizes — a standard icon link, larger icons for high-resolution displays, an apple touch icon for when someone saves your site to a phone home screen, and sometimes a web manifest that bundles a set of icons for installable web apps.
Google has its own specific requirements for the favicon it shows in search results. It looks for an icon declared with a recognized rel value, expects the file to be a square that is a multiple of 48 pixels (so 48 by 48, 96 by 96, 144 by 144 and so on), wants it in a supported format, and requires that the file be crawlable rather than blocked by robots rules. It also wants the icon to be visually consistent over time rather than changing constantly. The checker inspects all of this: which link tags are present, what files they point to, whether those files actually load, and whether the setup meets the conditions Google needs to display your icon rather than a generic placeholder.
What this checker inspects
Run the tool against a URL and it parses the head for every icon-related link relation, listing each declared icon along with its type and stated size. It then checks the most important fallback directly: a request to the root favicon.ico, since that is what gets used when no tag is present and what many crawlers still probe for. It reports whether each referenced file returns a successful response or a 404, whether the paths are absolute and correctly formed, and whether anything points to a file that simply does not exist.
Beyond mere presence, the tool evaluates whether the setup satisfies the practical needs of the main contexts: a small icon for the browser tab and search results, a larger apple touch icon for home-screen saves, and ideally a manifest for installable experiences. It flags the common gaps — a declared icon that 404s, a missing root favicon.ico with no tag-based replacement, an icon that is the wrong shape or an unsupported format for Google search, or a favicon path blocked from crawling so Google can find the tag but never fetch the image.
How to read the results
A clean result shows at least one declared icon link pointing to a real file that loads successfully, a working root favicon.ico fallback, and a square icon in a supported format and crawlable location that meets Google search requirements. With that in place, your icon should appear consistently in tabs, bookmarks, and on mobile search results, and you can stop worrying about it.
Warnings tell you exactly where the chain breaks. A declared icon that returns a 404 means the markup promises an image that is not there, so the browser falls back to whatever it can find or shows nothing. A missing root favicon.ico with no tag-based icon means there is no safety net at all. An icon that is not square, not a multiple of 48 pixels, or in a format Google does not accept means tabs may show it but search results will not. A favicon blocked by robots rules is a subtle one: the tag is correct and the file exists, but Google is forbidden from fetching it, so your search listing stays blank. Each of these points to a specific, quick fix rather than a vague problem.
The mistakes that keep your icon from showing
The most frequent issue is caching confusion. Browsers hold onto favicons aggressively, so a developer changes the icon, sees the old one in their tab, assumes it did not work, and starts second-guessing the setup — or worse, the file was actually removed but the browser keeps showing a cached copy, masking the fact that it now 404s for everyone else. The checker bypasses your local cache and reports what the server genuinely sends. Another common mistake is using a relative path in the link tag that resolves correctly on the homepage but breaks on deeper URLs, so the icon vanishes on interior pages.
Format and size mistakes are also routine. People ship a single tiny low-resolution icon that looks blurry on high-density screens, or use a transparent icon that disappears against certain backgrounds, or supply only an apple touch icon and forget the standard one. For Google specifically, the recurring failures are a non-square image, a size that is not a multiple of 48 pixels, an unsupported format, an icon that changes too often for Google to settle on, and a robots rule that blocks the icon path. Any one of these can leave a generic globe next to your result no matter how good your content is.
Why a tiny icon matters for clicks and AI search
In search results, the favicon is part of your visual identity competing for attention against every other listing on the page. A crisp, recognizable icon next to your title makes your result feel established and trustworthy, while a blank placeholder makes it feel anonymous or broken. When users scan a results page quickly, that small cue nudges click-through in your favor. The same icon then reinforces recognition in the tab, the bookmark bar, and the history list, building familiarity every time someone returns — a quiet compounding brand effect from a single small file.
As AI search interfaces mature, many of them surface source attributions with site icons and names to help users judge credibility at a glance. A site with a clean, consistent favicon presents as a coherent brand in those attribution chips, while a site with a missing or broken icon looks less polished next to competitors. The favicon is a small part of being recognizable as a legitimate source, and being recognizable is increasingly tied to being chosen and cited. It is low effort with outsized presence, which is exactly why it is worth getting right and worth verifying rather than assuming.
What to do after you run the checker
Fix any broken paths first — if a declared icon 404s or the root favicon.ico is missing, put a real file in place and confirm it loads. Use absolute paths in your link tags so the icon resolves identically on the homepage and on deep pages. Provide a square icon in a supported format at a size that is a multiple of 48 pixels so Google search can use it, and add a higher-resolution version plus an apple touch icon so the experience holds up on retina displays and home-screen saves. If you support installable web apps, include a web manifest that references a proper icon set.
Make sure none of your favicon paths are blocked by robots rules, since a blocked icon is invisible to Google even when everything else is correct. After deploying, verify in a fresh browser session or incognito window to defeat caching, and confirm the icon appears on an interior page, not just the homepage. Keep the icon stable over time rather than swapping it frequently, because Google prefers a consistent image and a constantly changing icon can stop it from showing one at all. Re-run the checker after any redesign or domain change, since favicons are a classic casualty of migrations and are rarely the first thing anyone thinks to test.