When a favicon is missing, the file is not always the problem. The browser, a CDN, a service worker and a search engine can each retain a different version. An ordered diagnosis avoids changing several variables at once.
Start with the file request
Open the exact URL referenced by the link element. It must respond without authentication, with the right content and without an unnecessary redirect chain. An HTML error page named favicon.ico cannot be decoded as an icon.
In the Network panel, filter for icon or favicon. Record the final URL, status, content type and whether the response came from cache.
| Check | Expected result | Fix |
|---|---|---|
| Direct URL | 200 image response | Fix path or deployment |
| Link element | Present in head | Fix rendered HTML |
| Cache | New response received | Purge, then retest |
| Crawl access | File is reachable | Remove the block |
Check the HTML that is actually rendered
Inspect the produced document, not only its source template. An extension, theme or component may inject a second icon element after yours and cause the browser to choose another file.
Check paths from a deeply nested page and the exact filename casing. On a case-sensitive server, Favicon.svg and favicon.svg are different resources.
Isolate every cache layer
First test in a fresh profile or with the network cache disabled. If the new image reaches the origin but not the public domain, purge the CDN. If a PWA is installed, inspect its service worker and manifest too.
For a future revision, a versioned filename can make the change explicit. Keep /favicon.ico available for clients that request it by convention.
Separate browser and search-result behavior
Google requires a square favicon that can be crawled and is associated with the site's home page. Its URL may be crawled at a different time from the page, which explains a delay after a fix.
Use URL inspection to confirm that the home page is reachable and request recrawling when it has changed. Then allow time for processing: clearing a local browser cache does not affect the search index.
Primary sources
Frequently asked questions
Why does the old favicon return?
A cache layer, service worker or second icon element may still serve the old file. Identify the URL actually loaded before purging.
Is a version query parameter enough?
It can bypass some caches, but a new filename is often more explicit. Keep the /favicon.ico fallback available.
Does the Google favicon change immediately?
No. Google must recrawl and reprocess the page and icon. There is no guaranteed exact delay.