Why isn't my favicon showing up in Google search results?

Usually one of a few things: no explicit tag in the page's head, a non-square image, the icon blocked by robots.txt, or Google simply hasn't refreshed its cached favicon yet after a recent fix.

What size should a favicon be for Google search?

Google requires a minimum of 48×48 pixels and a square aspect ratio. Providing a larger square image (like 512×512) alongside a smaller one covers more display contexts without extra work.

How long does it take Google to update a favicon?

There's no fixed timeline — it can take anywhere from a few days to a few weeks, since Google caches the favicon separately from its normal page-recrawl schedule. Requesting indexing on the homepage can nudge it along but won't guarantee an immediate refresh.

Is favicon.ico enough, or do I need a link tag too?

Most browsers will find /favicon.ico automatically by convention, but Google's search favicon feature doesn't guarantee it follows that same convention. An explicit tag is the safer, documented approach.

What's the difference between a favicon and an Apple touch icon?

The favicon is what shows in a browser tab and, when requirements are met, next to your listing in Google search. The Apple touch icon is a separate, larger icon iOS uses specifically when a visitor saves the page to their home screen.

Favicon Checker: Why It's Missing From Search Results (Free)

The favicon in search results isn't automatic

Google shows a small icon next to your site's name in mobile search results — the same one that sits in a browser tab. Most people assume this just works because they uploaded a favicon.ico file somewhere years ago. It doesn't always. Google has specific, documented requirements for which icon it will show, and a surprising number of sites — including ones with a perfectly good favicon file sitting on the server — fail at least one of them without anyone noticing, because a missing search favicon doesn't throw an error. The page just quietly shows a generic globe icon instead.

What Google actually requires

A <link rel="icon"> tag in the page's <head> — Google explicitly does not guarantee it will fall back to the browser default of /favicon.ico at the domain root, even though every browser does.
A square image, minimum 48×48 pixels — a rectangular or oddly-cropped icon can get rejected outright.
A stable, crawlable URL — not blocked by robots.txt, not requiring a login, and not changing location on every deploy.
A supported format — ICO, PNG, SVG, or WebP. GIF and BMP are not reliably supported.
The same favicon the rest of the site uses — Google favors consistency; a favicon that changes per-page or per-deploy can confuse which version gets cached and shown.

A page with no declared favicon, fixed

This is more common than it sounds — a site that has a favicon file sitting at the domain root, but never actually tells the browser (or Google) where to find it with a link tag:

<head>
  <!-- No <link rel="icon"> at all — relying on the
       browser default of /favicon.ico -->
</head>

Most browsers will still find /favicon.ico by convention and show it in the tab — which is exactly why this goes unnoticed for so long. Google's crawler is less forgiving about relying on that convention. Declared explicitly:

<head>
  <link rel="icon" href="/favicon.ico" sizes="32x32">
  <link rel="icon" href="/icon.svg" type="image/svg+xml">
  <link rel="apple-touch-icon" href="/apple-touch-icon.png">
  <link rel="manifest" href="/site.webmanifest">
</head>

Four separate icon declarations, each serving a different consumer: the classic .ico for older browsers, an SVG for crisp rendering at any size, an Apple touch icon for when the site is saved to an iOS home screen, and a web manifest that ties them together for Android/PWA install prompts. Google's search favicon specifically reads the first rel="icon" declaration it finds.

Paste a URL into CheckSEO's Favicon Checker to see every icon a page actually declares — favicon, Apple touch icon, manifest icons — and download any of them, no signup.

Open the Favicon Checker

The most common favicon mistakes

No <link rel=icon> tag at all

Relying purely on the browser convention of fetching /favicon.ico works for the tab icon in most browsers, but isn't something Google's search favicon feature guarantees it will do. Fix: add an explicit link tag even if a favicon.ico file already exists.

Non-square icon

A favicon exported as a rectangle, or accidentally cropped during a redesign, fails Google's square requirement outright. Fix: re-export at an exact square size like 48×48 or 512×512.

Favicon blocked by robots.txt

A Disallow: /assets/ or similar rule that happens to also catch the icon's folder means Google can never fetch it, even though the link tag is correct. Fix: check your robots.txt doesn't block the favicon's actual path.

Favicon changes on every deploy

Some build tools hash static asset filenames (favicon.a3f9c2.ico) and the link tag updates correctly, but if the URL changes on every single deploy, Google may never catch up before the next change invalidates its cache. Fix: keep the favicon's URL stable across deploys, or accept a longer refresh lag.

Missing Apple touch icon or manifest icons

Not something Google's search results need, but a common source of a blank or default icon when a visitor saves the site to their phone's home screen — a different, often more visible, failure mode. Fix: add apple-touch-icon and a web manifest alongside the standard favicon.

Why the favicon in search sometimes lags behind a real fix

Fixing the declaration doesn't make the new icon appear in search results immediately. Google caches the favicon it has already validated for a site, and that cache doesn't refresh on the same schedule as a normal page recrawl — it can take anywhere from a few days to a few weeks for a corrected favicon to replace the generic globe icon or an old cached one. There's no dedicated "request favicon refresh" tool the way there is for page indexing; requesting indexing on the homepage through Search Console's URL Inspection tool can nudge it along, but the practical fix is simply to get the declaration right once and wait.

Favicon, Apple touch icon, and manifest icons aren't the same thing

It's easy to conflate these because they all live in the same handful of <link> tags, but each serves a genuinely different surface. The favicon is what shows in a browser tab and — when the requirements above are met — next to your listing in Google search results. The Apple touch icon is what iOS uses specifically when a visitor adds the page to their home screen, rendered at a much larger size (typically 180×180) with rounded corners applied automatically by the OS, not the image itself. The web manifest's icons array feeds Android's equivalent home-screen and PWA install-prompt icon, often wanting multiple sizes (192×192 and 512×512 are the common pair) in one JSON file rather than a single link tag. A site can have a perfect search favicon and still show a blurry, stretched icon when saved to a phone, because that failure lives entirely in the Apple touch icon or manifest, not the favicon Google reads.

Check your own page

CheckSEO's Favicon Checker reads every icon a page declares — favicon, Apple touch icon, and manifest icons — in one pass, so you can confirm the right one exists before waiting weeks to find out it doesn't.

Why Your Favicon Isn't Showing in Google Search (and How to Fix It)