Favicon Not Showing in Google Search Results: How to Fix It

By Idea to Traffic Editorial Team · Published October 1, 2026 · Last updated October 1, 2026

Your favicon is the little square that sits next to your site name in Google results. When it vanishes, Google shows a plain grey globe instead, and your listing looks less trustworthy than the ones around it. The good news is that the cause is almost always one of a short list of things, and you can test every one of them in about ten minutes.

A common version of the question this week: everything was fine, then Search Console and Google results stopped showing the icon, and even the Chrome tab went blank, while the WordPress admin area still showed it. That last detail is a strong clue, and we will come back to it.

Rule out a Google side bug first

Before you touch your theme, check whether the problem is yours at all. In late August 2026 site owners reported favicons being swapped for the generic globe across many sites at once, and a Google search lead confirmed it was an issue on Google's end that was being fixed. If dozens of unrelated sites lose their icons on the same day, the fix is waiting, not editing.

Two quick ways to tell:

• Search for a few competitors in your niche. If their icons are missing too, it is probably not you.
• Look at your own favicon in a browser tab on a fresh profile or private window. If the tab shows nothing, the problem is on your site, because browsers do not depend on Google at all.

If the browser tab is also blank, as in the case above, skip straight to the next sections. Google is not the cause.

What Google requires from a favicon

Google's favicon documentation (last updated August 28, 2026) is short, and most failures break one of these rules:

• A link tag on the home page. Google reads the favicon from your home page's <head>, using rel="icon", rel="shortcut icon", rel="apple-touch-icon" or rel="apple-touch-icon-precomposed". An icon set only on inner pages does not count.
• Square, at least 8x8 pixels. Google recommends going larger than 48x48 so it looks sharp. A 48x48, 96x96 or 192x192 PNG is a safe choice. A 300x120 logo will not work, because it is not square.
• A supported format. BMP, GIF, ICO, PNG, JPEG, PPM and TIFF are listed. SVG is not on Google's list, so if your only icon is an SVG, add a PNG alongside it.
• Crawlable. Googlebot must be able to fetch the home page and Googlebot-Image must be able to fetch the icon file. A robots.txt rule or a firewall challenge on either breaks it.
• Stable URL. If the icon URL changes on every deploy (a hashed file name, a query string that rotates), Google keeps chasing a moving target.
• One per hostname. example.com and blog.example.com can have different icons. example.com/shop cannot have its own.

The correct tag looks like this, placed inside <head> on the home page:

<link rel="icon" href="/favicon-96.png" sizes="96x96" type="image/png">
<link rel="icon" href="/favicon.ico" sizes="any">

The seven checks, in order

Run these from a terminal. Replace example.com with your own domain, and use the exact hostname that ranks (with or without www).

1. Is the tag actually in the home page HTML?

curl -sL https://example.com/ | grep -i 'rel="[^"]*icon'

If this prints nothing, the tag is missing from what servers send. On WordPress this happens when a theme update drops the Site Icon output, or when an optimisation plugin strips or rewrites the head. The setting lives in Appearance > Customize > Site Identity > Site Icon in classic themes, and under Settings > General in recent WordPress versions: remove the icon, save, upload it again and save.

2. Does the icon URL return 200 and an image type?

curl -sI https://example.com/favicon-96.png | grep -iE '^(HTTP|content-type)'

You want HTTP/2 200 and content-type: image/png (or the matching image type). A 404, a 301 to a login page, or text/html means the browser and Google are being handed something that is not an image. That is the most likely explanation for the "works in wp-admin, blank everywhere else" pattern: the admin area uses its own markup, while the public pages point to a file that a cache or CDN is no longer serving correctly.

3. Is the image square and big enough? Open the file and check its dimensions, or run file favicon-96.png. Anything that is not 1:1 should be redone.

4. Is it blocked in robots.txt?

curl -s https://example.com/robots.txt

Look for a Disallow that covers the icon path, such as /wp-content/uploads/, /assets/ or /images/, or a group aimed at Googlebot-Image. Remove it or add a specific Allow for the icon file.

5. Is a firewall challenging bots? Bot protection, "under attack" modes and some security plugins answer crawlers with a challenge page instead of the file. In Cloudflare, open the Security Events log for your domain and filter for blocked requests to your icon path from Google user agents. In Search Console, run URL Inspection on your home page and click Test live URL: if Google cannot fetch the page, it cannot find the icon.

6. Does the home page redirect? If example.com redirects to www.example.com, the favicon has to be declared on the final home page that Google indexes. Check the chain with curl -sIL https://example.com/ | grep -i '^location'.

7. Did the URL just change? If you moved to a new theme, a new host or a build tool that renames files, Google may still hold the old URL. Give the icon a fixed name like /favicon-96.png and keep it there.

Fixing the browser tab too

Browsers are simpler than Google: if there is no tag, they still try /favicon.ico at the root. So a blank tab usually means both the tag and the root file are failing. Put a real favicon.ico at your domain root as a safety net, then clear your cache plugin and CDN cache so stale HTML is not served. Browsers also cache favicons aggressively, so test in a private window before deciding the fix did not work.

If you host a static site on Cloudflare Pages or a similar platform, check that the icon file is inside your build output folder. A file that sits in the project root but not in dist or public never gets deployed, and the server may answer the request with your 404 page or even your home page with a 200 status.

Getting Google to pick up the fix

Once all seven checks pass, open Search Console, run URL Inspection on your home page, and click Request indexing. Google says recrawling the favicon can take from several days to several weeks, so a fix today may not show in results until later this month. Do not keep swapping files while you wait, because each change resets the clock.

If you want a quick second opinion on the basics around this, the free site checker looks at your home page's head tags, status codes and robots.txt in one pass, which covers several of the checks above.

The short version: if the browser tab shows your icon and only Google does not, wait and request indexing. If the tab is blank too, the file or tag is broken on your side, and checks 1 and 2 will almost always find it.

Where this question came from

• r/SEO: Why my search console, google and sometimes active tab does not show the favicon?
• Google Search Central: Define a favicon to show in search results
• Search Engine Roundtable: Google Search favicons breaking

Questions about favicons in search results