Favicon Checker
Validate your website's favicon configuration across all browsers and devices. Check for missing icons and get recommendations for optimal setup.
Enter a URL above to check its favicon configuration
If your favicon is broken, your site looks unfinished before anyone reads a word.
Most favicon problems are invisible until they are embarrassing. Your site looks fine in Chrome on your laptop because the icon is cached from when you tested it three months ago. Meanwhile a new visitor on Safari sees a blank tab, your Android user gets a default Chrome dot when they add the app to their home screen, and Google shows the globe icon next to your brand search. You only find out when a customer screenshots it.
A favicon checker fetches your URL fresh, parses the HTML, and verifies what is actually being served. It looks at every link tag in the head, follows them, checks status codes and dimensions, and flags anything Google will reject. The two things that catch most sites: the favicon resolves but is under 48 by 48 pixels, which means Google's SERP icon will not show, and the site.webmanifest is either missing entirely or its icons array points to broken URLs.
There is a specific list of things to verify, and it is not long. A favicon.ico at the root with at least a 48-pixel bitmap inside. An apple-touch-icon.png at 180 by 180 referenced from the head. A site.webmanifest with an icons array containing at least a 192 and a 512 pixel PNG. Every URL returning a 200. No robots.txt rules blocking the icon paths. No CDN redirect chains that confuse Googlebot. If any of those fail, the checker flags it.
The reasons favicons silently break in production are boringly predictable. Someone renamed the file during a redesign and forgot to update the link tag. The CDN serves a 301 redirect that Google will not follow for icons. The site.webmanifest is served with the wrong MIME type so the browser ignores the icons array. A dynamic URL like /favicon?build=abc123 changes on every deploy so Google never builds confidence in a stable image. None of these errors throw in your console. The site looks fine. The favicon just quietly does not appear.
You run this when you notice your brand SERP shows the globe, before a major launch, after any rebrand, and as part of a quarterly housekeeping pass. It takes about ten seconds to run and saves you the awkward moment of explaining to your team why the favicon never came back after the redesign.
When the Favicon Checker is the right tool
Your brand SERP shows the globe icon
Google is not displaying your favicon in search. Run the checker to confirm whether the source file meets the 48-pixel minimum, is reachable, and is not blocked. Nine times out of ten you find the cause in under a minute.
Right before a major launch or relaunch
Pre-launch checklists always cover meta tags and OG images and somehow skip the favicon. Run the audit on staging and on production once DNS cuts over. Nothing kills first-impression credibility faster than a broken tab icon on launch day.
After a redesign or site migration
File paths move, link tags get rewritten, the manifest gets dropped. Anything touching the head of your HTML is at risk. Run the checker on the new build before the old URL stops 301ing.
Quarterly housekeeping on production sites
Once a quarter, run it on your top three properties. CDN configs drift, asset hashing changes, someone moves /public around. Catching a missing manifest in a five-minute audit beats finding it from a customer email.
Auditing a competitor or a site you just acquired
When you take over a site, the favicon stack is one of the first things to verify. It tells you how much care went into the previous build. A clean favicon setup means the rest of the head is probably in decent shape too.
How to use the Favicon Checker
Audit favicon coverage across browsers and search engines.
Enter your website URL
Paste the homepage URL of the site you want to inspect.
Review the report
See which favicon sizes, manifest icons, and Apple icons are present or missing.
Fix gaps and re-run
Use the favicon generator to fill missing sizes, then re-check to confirm.
Mistakes we see all the time
Assuming the favicon works because you see it in your browser
Your browser cached it. Cached aggressively. Hard-refresh, incognito, mobile Safari, and Google's SERP all behave differently. The only honest test is a fresh fetch from a tool that does not respect your cache.
Ignoring the manifest because the favicon shows up
A working favicon.ico does not mean PWA install works, Android home screen icons render, or your theme color is applied. The site.webmanifest is a separate file with separate failure modes. Audit it separately.
Treating a 200 status as success
The favicon URL returning 200 means the request succeeded. It does not mean the bytes are a valid image, the dimensions meet Google's minimum, or the content type is correct. A good checker reads the actual file, not just the response code.
Forgetting that Google needs time to refresh
You fix the favicon, redeploy, and check the SERP an hour later. Still the globe. That is normal. Google's SERP icon updates on its own schedule, usually within a week or two after re-crawl. The checker confirms you fixed the source; patience confirms the SERP.
Favicon Checker — Frequently Asked Questions
- What does the favicon checker validate?
- It verifies that every required favicon size, .ico file, and Apple touch icon is reachable from your site.
- Does it test the manifest icons?
- Yes — it parses site.webmanifest and confirms all referenced icons load correctly.
- Why does my favicon not show in Google?
- Google requires a 48×48 minimum that loads from a stable URL. The checker flags missing or undersized icons.
- How long after fixing the favicon will Google update the SERP icon?
- Usually one to three weeks, sometimes faster if you resubmit the homepage in Search Console. Google has to re-crawl the page, re-fetch the icon, validate it meets the 48-pixel minimum, and then push it into the search index. There is no manual override, so the only lever you have is making sure the file is correct and the URL is stable.
- Why does the checker say my manifest is invalid when the file exists?
- Almost always a MIME type or JSON syntax issue. The site.webmanifest must be served as application/manifest+json or application/json. If your server sends it as text/html, the browser parses it but Lighthouse and PWA tools will reject it. A trailing comma in the JSON will also silently break it.
- Can I use a single SVG favicon instead of all these PNG sizes?
- For modern browsers, yes, with a single link tag pointing at favicon.svg. But Google's SERP still wants a raster image at 48 pixels or larger, Apple touch icons must be PNG, and the manifest icons array expects raster. The honest answer is ship both: SVG for crisp tab icons, PNGs for everything else that has not caught up.
- Does the checker test mobile and desktop separately?
- It fetches your HTML once and validates every icon reference in the head, which covers both. Mobile and desktop browsers look at the same link tags. The difference is which icons they prioritize: iOS goes for apple-touch-icon, Android reads the manifest icons array, desktop browsers default to favicon.ico. If all three pass, you are covered on every platform.
- What if my favicon is served from a CDN with a hashed filename?
- It works, but only if the link tag in your HTML points to the current hashed URL. The risk is the manifest or any hard-coded reference still pointing to last week's hash. Run the audit after every deploy that touches assets to catch the stale reference before users do.
- Why is my favicon blurry on retina displays?
- Either your source image is too small or your link tags do not include a high-resolution variant. Add a 32 by 32 PNG link tag and a 192-pixel manifest icon. For Apple touch icon, 180 by 180 is already retina-friendly. If the source itself is rasterized at 64 pixels, no link tag will save you.
- Does the checker work on sites behind authentication?
- Only the public-facing HTML. If the favicon link tags are exposed on the login page, the audit can verify them. If your app gates everything behind a login wall, the checker cannot crawl past it, and you will need to inspect the head manually in DevTools.
A broken favicon will not crash your site or tank your rankings. It will just quietly tell every visitor that nobody is paying close attention. Run the audit, fix what is flagged, move on. Ten minutes of work for the rest of your site's life.