Favicon not showing in Google: requirements and a fix order
A browser tab icon and a Google search icon are separate surfaces. Check the homepage declaration, image response, size and crawl access, then wait for recrawling.
Two different surfaces
The browser tab uses the declaration on the page you are viewing. Google Search reads the declaration on the homepage and must be able to crawl both the page and the icon. A correct tab icon does not prove the search icon is eligible.
Treat “wrong in the browser” and “missing in Google” as separate investigations. Fixing a cache will not repair an icon URL that returns HTML, and uploading a new file will not guarantee search display.
Check the requirements Google states
Google’s current guidance asks for a square icon, at least 8×8 pixels, and recommends a larger source than 48×48. The icon should be declared on the homepage, have a stable URL, and be crawlable.
A reachable image is necessary but not sufficient. Google chooses whether and when to show it, and changes can take days to weeks to appear.
- Square source, not a wide logo cropped at runtime.
- Declared with a link rel icon or the framework equivalent.
- Returned as an image with the correct content type.
- Not blocked by robots.txt or a login redirect.
- Stable URL, not a cache-busted path that changes on every build.
Fix order that avoids wasted deploys
Start with the resolved URL. Fetch the icon path and confirm the bytes are an image rather than an HTML page. Then check the homepage declaration and the size of the source. Only then look at caches.
| Symptom | Check | Fix |
|---|---|---|
| Icon 404s | Resolved href and deployed asset | Correct the path and deploy the file |
| Icon returns HTML | Catch-all route or login redirect | Serve an image at that URL |
| Tab shows an old icon | Browser and CDN cache | Deploy, then test in a fresh session |
| Google shows nothing | Homepage declaration and crawl access | Allow crawling and wait for recrawl |
| Only some pages differ | Relative icon path | Use the correct absolute path |
When to stop changing the file
If the homepage declares a stable, square, crawlable icon and the response is an image, the technical work is done. Constantly replacing the file or adding more sizes resets discovery and does not speed up Google’s decision.
Record the change date and check the search result again in a few weeks. Use the browser tab only for rendering checks, not as evidence about Google.
Frequently asked questions
How long does Google take to show a new favicon? Days to weeks; there is no guaranteed timeline or display.
Is an ICO required? No. Google accepts common image formats; the important part is a square, crawlable image declared on the homepage.
Does a 512×512 file guarantee display? No. It meets the size guidance, but display remains Google’s decision.
Check the live icon, not the design file
Run a free audit to see the favicon declaration and the actual image response before waiting on Google.
Run a free audit