Technical SEO

Favicon Not Showing in Google Search Results? Here's the Fix

8 min read

Summarize this blog post with:

Table of contents

If your favicon is not showing in Google search results, the cause is almost always one of these: the favicon is an SVG (Google doesn't support SVG favicons), the icon or your home page is blocked from crawling, the icon is the wrong shape or size, or Google simply hasn't recrawled your home page yet. Fix the first three, request indexing of your home page in Search Console, and give it several days to a few weeks.

The reason it catches people out: your favicon can look perfect in the browser tab and still fail Google's rules. Browsers accept formats and setups that Google Search doesn't, so the tab icon tells you nothing about what Google will show.

Why this happens: Google supports fewer favicon formats than your browser

Google finds your favicon through the <link rel="icon"> tag in the <head> of your home page. It reads that one page, follows the link, and fetches the file. So far that's the same as a browser.

The difference is the format. Modern frameworks increasingly ship favicons as SVG files (in Next.js, an app/icon.svg file). Every modern browser shows an SVG favicon in the tab. Google Search doesn't: its supported formats are BMP, GIF, ICO, PNG, JPEG, PPM and TIFF. If the only icon your home page links to is an SVG, Google has nothing it can use, and it shows the generic globe or an old cached icon instead.

This gap is invisible in normal testing. The tab icon looks right and nothing in your build errors. It only shows up in Google's results, and Amsive's troubleshooting guide on missing favicons lists the SVG-only setup among the most frequent causes they see in audits. Our SEO site audit checks the favicon on every run, so the gap shows up before Google's results do.

Google's actual favicon requirements

Per Google Search Central's favicon documentation, a favicon needs to meet all of the following:

  • Linked from your home page. Add a <link rel="icon"> tag (or shortcut icon or apple-touch-icon) to the <head> of the home page.
  • One favicon per hostname, on a domain or subdomain home page. example.com and blog.example.com can each have one. A site that lives in a subfolder, such as example.com/shop/, can't have its own favicon in Google.
  • Square (1:1 aspect ratio), at least 8x8px. Google recommends going larger than 48x48px so the icon holds up on different surfaces. Search Engine Journal reported on Google's push toward higher-resolution favicons because low-res icons look blurry on today's denser displays.
  • A supported format: BMP, GIF, ICO, PNG, JPEG, PPM or TIFF. SVG is not on the list.
  • Not blocked from crawling. Neither the favicon file nor the home page can be blocked by robots.txt or anything else.
  • A stable URL. Google's guidance is explicit: "the favicon URL must be stable", so don't keep changing the path or filename.

Miss any one of these and Google can silently skip your favicon, without any warning in Search Console. And even when everything is right, Google says a favicon "isn't guaranteed to appear".

The five most common causes, in order of likelihood

1. SVG-only favicon

The scenario above. Keep the SVG for browsers if you like, but make sure your home page also links to an ICO or PNG version. In Next.js, drop a favicon.ico (and optionally an icon.png) into the app/ directory alongside icon.svg. The framework's file-based metadata convention adds a <link> tag for each one automatically, per Next.js's own metadata file documentation. View the source of your home page afterwards and confirm a rel="icon" tag points to the .ico or .png file.

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. The site lives in a subfolder

Google shows one favicon per hostname, taken from the home page. If your site is example.com/store/, Google uses whatever favicon example.com has, and nothing you put in /store/ changes it. Move the site to its own subdomain (store.example.com) if it needs its own icon.

5. 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 five causes above and it's been under a week, that's expected behavior, not a sign something is still broken.

Favicon not appearing after a Search Console request

Search Console has no favicon report, so you can't check the icon there directly. What you can do is make sure Google can read your home page the way it needs to:

  1. In Search Console, open URL Inspection and enter your home page URL.
  2. Click Test live URL, then View tested page, and check the HTML for your rel="icon" tag. If the tag is missing from the tested page, Google can't see it either (common when the tag is added by client-side JavaScript).
  3. If the live test passes, click Request indexing.
  4. Wait. A request speeds up the recrawl of the home page, but the favicon in results can still take days to weeks to change.

Quick diagnostic checklist

CheckHow to verify
Home page links to an ICO or PNG iconView source on your home page and look for rel="icon"
The linked icon file returns 200, not 404Open the icon URL directly in a browser
Square, at least 8x8px (48x48px or larger is better)Check actual pixel dimensions of the file
Not blocked in robots.txtRun our free robots.txt checker
Stable URL, no recent path changesConfirm the favicon path hasn't moved in your last few deploys
Not a caching illusionTest 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 support more formats than Google does. The most common case is an SVG favicon: it shows in every modern browser tab, but Google Search doesn't support SVG. Link an ICO or PNG version from your home page as well.

Does my favicon need to be an .ico file specifically?

No. Google accepts BMP, GIF, ICO, PNG, JPEG, PPM and TIFF. ICO and PNG are the usual choices. SVG is the one common format it doesn't accept.

Can I check my favicon in Google Search Console?

Not directly; there's no favicon report. Use URL Inspection on your home page, run a live test, and check that the tested HTML contains your rel="icon" tag. Then request indexing.

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 with DidYouSEO

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.

DidYouSEO

Rank on Google. Show up in AI search.

Audit your site, track Search Console data and see if AI assistants mention you, in one dashboard.

  • Google
  • ChatGPT
  • Claude
  • Gemini
  • Perplexity
Start 7-day free trial

No credit card required