Favicon Not Showing in Google Search Results? Here's the Fix
Favicon not showing in Google search results? Usually a missing favicon.ico, a robots.txt block, or Google's normal crawl lag. Here's how to fix it.
DidYouSEO Team··6 min read
Your site has a favicon. It shows up fine in the browser tab. But Google search results still show a gray globe, a generic icon, or a stale version from months ago. If that's what you're staring at right now, the cause is almost always one of three things — and none of them requires waiting on Google.
Favicon not showing in Google search results is a narrower problem than it looks, because Google's favicon crawler behaves differently than a browser does. A setup that works perfectly for every visitor's browser tab can still fail Google's specific requirements.
Why this happens: Google checks a different path than your browser does
Modern frameworks increasingly ship favicons as SVG files using file-based conventions — in Next.js specifically, an app/icon.svg file. Browsers handle this fine; they read the <link> tag in your page's <head> and load whatever it points to.
Google's favicon crawler works differently. It specifically looks for a file at /favicon.ico, at the domain root, largely independent of what your <link> tags say. If a site relies solely on an SVG file-convention favicon with no /favicon.ico fallback present, that root path returns a 404 — and Google either falls back to a stale cached icon or shows the generic globe placeholder instead of your actual logo.
This is a common gap in modern setups precisely because it's invisible in normal browser testing. The tab icon looks correct. Nothing in your build process errors. The only place it shows up is in Google's own results — Amsive's troubleshooting guide on missing favicons flags this exact SVG-only gap as one of the most frequent root causes they see in audits.
Google's actual favicon requirements
Per Google Search Central's favicon documentation, a favicon needs to meet all of the following:
- Square (1:1 aspect ratio).
- A multiple of 8px. Google's minimum is 8x8px, but it explicitly recommends going larger — above 48x48px — so the icon holds up across different display surfaces. Search Engine Journal reported on Google's push toward higher-resolution favicons specifically because low-res icons look blurry on the denser displays most searchers now use.
- A supported format. Google accepts any valid favicon format (ICO, PNG, SVG, GIF among them).
- Not blocked by robots.txt. Both Googlebot and Googlebot-Image need unrestricted access to the favicon file itself and to your homepage.
- Reachable at a stable URL. Google's own guidance is explicit: "the favicon URL must be stable" — changing the path or filename frequently works against you.
Miss any one of these and Google can silently decline to show your favicon, without any warning in Search Console.
The four most common causes, in order of likelihood
1. SVG-only favicon, no .ico fallback
The scenario above. Add a real favicon.ico file at your site root as a fallback, even if your primary favicon is an SVG for browsers. In Next.js, drop a favicon.ico directly into the app/ directory alongside icon.svg — the framework's file-based metadata convention serves both automatically, with favicon.ico covering the root-path check and icon.svg covering modern browsers, per Next.js's own metadata file documentation.
2. Favicon blocked by robots.txt
A broad Disallow rule — sometimes added to block a /assets/ or /static/ directory generally — can accidentally catch the favicon path too. Check your robots.txt for any rule that would match /favicon.ico or your icon's actual path, and confirm it explicitly allows it. Our free robots.txt tester checks exactly this — whether a given path is blocked or allowed under your current rules. If you're not sure which crawlers are actually being let through, our guide to checking whether AI crawlers are blocked covers the same rule-reading process, since it's the identical mechanism blocking any bot, Googlebot included.
3. Wrong dimensions or aspect ratio
A non-square icon, or one smaller than 8x8px, fails Google's basic shape requirement outright. Re-export at a square canvas, ideally 48x48px or larger, in a format your framework's icon convention supports cleanly.
4. Caching — yours, not Google's
This one causes the most false alarms. If you just changed your favicon, your own browser or CDN may still be serving the old cached version, which makes it look like "Google hasn't picked up the new one" when actually your own site hasn't served the new one yet, from your visitor's point of view or your own testing browser. Hard-refresh, check in an incognito window, and verify via curl -I that your server is actually returning the new file at the expected path before assuming it's a Google-side issue.
The part nobody likes: there's a real lag, and no manual refresh button
Once your favicon setup is genuinely correct, Search Console and Google's search results still won't update immediately. Google's own documentation is blunt about this: allow time for Google to recrawl and process your homepage, and that "crawling can take anywhere from several days to several weeks." There is no button in Search Console that forces an immediate favicon refresh — the URL Inspection tool's "Request Indexing" can nudge a recrawl of the page, but it doesn't guarantee an immediate favicon update on its own.
If you've fixed all four causes above and it's been under a week, that's expected behavior, not a sign something is still broken.
Quick diagnostic checklist
| Check | How to verify |
|---|---|
| /favicon.ico returns 200, not 404 | Visit yourdomain.com/favicon.ico directly in a browser |
| Square, ≥8px, multiple of 8 | Check actual pixel dimensions of the file |
| Not blocked in robots.txt | Run our free robots.txt checker |
| Stable URL, no recent path changes | Confirm the favicon path hasn't moved in your last few deploys |
| Not a caching illusion | Test in incognito / via curl -I for the real server response |
What to do next
Run a full SEO audit to check your favicon setup alongside the rest of your technical foundation — meta tags, canonical tags, robots.txt, and sitemap issues often cluster together on the same sites, since they're usually symptoms of the same missing step during a framework migration or redesign.
FAQ
How long does it take for Google to update a favicon in search results? Google's own guidance says several days to several weeks after its next crawl of your homepage. There's no manual override that forces it faster.
Why does my favicon work in the browser tab but not in Google search results?
Browsers read your <link> tags directly. Google's favicon crawler specifically checks /favicon.ico at your domain root — if that exact path 404s, Google can ignore a perfectly working SVG or PNG favicon referenced elsewhere.
Does my favicon need to be an .ico file specifically?
No — Google accepts several formats including PNG and SVG. But having a file actually reachable at /favicon.ico as a fallback avoids the specific failure mode of Google's crawler checking that exact path and finding nothing.
Can robots.txt really block just my favicon and nothing else?
Yes, if a broad Disallow rule happens to match the favicon's path (a blanket rule on /assets/ or similar). Test the specific path, not just the general rule, to confirm.
Check your favicon setup
Run a free SEO audit to check whether your favicon, robots.txt, and other technical fundamentals are actually configured the way Google expects — before assuming it's just a matter of waiting.
See how your site scores - free
30+ SEO checks plus AI visibility. No credit card required.