Your Favicon Is Missing from Google Search Results—How to Fix It

A favicon is tiny, but when it disappears from Google Search the result can look unfinished or unfamiliar. The frustrating part is that the icon may appear correctly in your browser tab while Google still shows a generic globe, an old logo, or no recognizable mark at all.

That mismatch usually means the browser and Google are reading the site differently. The practical fix is to trace the favicon from the homepage markup to the image file, crawler access, hostname and recrawl status—in that order.

First, identify which favicon problem you actually have

Open the live homepage in a normal browser and then search for the brand on Google. Compare four places: the browser tab, the page source, the favicon file URL and the search result.

• Missing everywhere: the site setting or HTML link is probably absent.

• Visible in the tab but absent in Google: eligibility, crawling, hostname or recrawl timing is more likely.

• Old icon in Google: Google may not have processed the replacement yet, or the favicon URL stayed cached.

• Wrong icon on only one subdomain: that hostname may publish a different favicon.

Do not start by repeatedly uploading new files. Capture the current evidence first so you know whether your change solved the cause.

Check the homepage link element

Google looks for a favicon reference in the homepage header. A common form is <link rel="icon" href="/favicon.png">. Open the rendered source or browser developer tools, search for rel="icon", and inspect the final URL.

The Google Search favicon documentation says the URL can be relative or absolute. What matters is that it resolves to the intended image and remains stable. The MDN reference for rel="icon" also explains how browsers select between multiple icon declarations.

If several plugins, themes or apps inject favicon tags, the browser may choose one while a crawler discovers another. Remove obsolete declarations and keep the ownership of this setting clear.

Open the favicon URL as a crawler would

Copy the favicon URL from the HTML and open it in a private window. It should return the image directly, without login, a consent wall, a redirect loop or an HTML error page.

Then check the response in the Network panel. A successful browser preview is not enough if the server returns the wrong content type, intermittent 403 responses or a bot challenge. Google requires both the homepage and the favicon file to be crawlable by Googlebot and Googlebot-Image.

If your robots rules are complicated, compare them with Webcurry’s guide to controlling search and AI crawlers. Blocking an AI-training crawler is different from blocking the crawlers needed for Google Search.

Use an eligible image, not simply a good-looking logo

Google requires a square favicon and recommends a size larger than 48×48 pixels. A multiple of 48—such as 48×48, 96×96 or 144×144—is a dependable working choice. The design should still be recognizable when reduced to 16×16.

Use a simple symbol with strong contrast and enough padding. Fine text, thin outlines and a full horizontal logo often turn into visual noise. Keep the favicon URL stable after launch; changing it repeatedly makes recrawling harder to interpret.

Confirm the hostname and homepage agree

Google supports one favicon per hostname. That means example.com and shop.example.com can have different icons, but a subdirectory such as example.com/shop cannot have its own Google Search favicon.

Test the exact canonical hostname used in search: HTTP versus HTTPS and www versus non-www. Each alternate should redirect consistently to the preferred homepage. Conflicting versions can accompany broader canonical problems, so use the canonical troubleshooting workflow if Google is selecting a different URL version.

Platform-specific fixes

Wix

In Wix, open the site dashboard, go to Website Settings and upload the favicon. Wix requires a Premium plan, a connected domain and a published site for a custom live favicon. Its current guidance recommends a square multiple of 48 pixels unless the file is SVG. Follow the official Wix favicon instructions, publish, and inspect the live homepage rather than relying on the editor preview.

After the icon is correct, use Webcurry’s Wix SEO checklist to verify indexability, titles, internal links and other site-wide signals.

WordPress

For WordPress 6.5 and later, the official documentation places Site Icon under General Settings and recommends a square image of at least 512×512 pixels. Older installations commonly expose it under Appearance, Customize, Site Identity. Use the built-in Site Icon control described in the WordPress favicon documentation.

If the setting looks correct but the front end does not change, purge the page cache, CDN cache and optimization cache. Also inspect whether the active theme or an SEO/performance plugin prints a second favicon tag. Webcurry’s website cache diagnostic helps separate a cached file from a publishing problem.

Shopify

In Shopify, open Online Store, edit the active theme, then check Theme settings under Logo or Favicon. Confirm you changed the published theme rather than an unpublished copy. Shopify’s favicon guide notes that the theme editor itself may not display the live storefront favicon, so verify the public URL.

Request a recrawl only after the technical checks pass

A favicon change is not instant. Google says recrawling and processing can take several days to several weeks, depending on how often its systems revisit the homepage. Even a valid favicon is not guaranteed to appear.

Once the live homepage contains the correct tag and the file is crawlable, inspect the homepage in Search Console and request indexing. Do not submit repeated requests while the underlying file remains blocked or incorrect. If Google crawls the site but still excludes important pages, follow the crawled-but-not-indexed diagnostic.

A practical acceptance test

• The preferred homepage returns 200 and is indexable.

• Its HTML contains one intentional favicon setup.

• The favicon URL opens publicly and returns an image.

• The image is square, recognizable at small size and uses a stable URL.

• Robots rules allow the homepage and image crawlers.

• HTTP, HTTPS, www and non-www versions resolve consistently.

• Browser and CDN caches have been cleared after the final change.

• The homepage—not a random blog post—has been submitted for recrawling.

Fix the evidence, then wait for Google

A missing favicon is rarely solved by uploading the same logo again. The durable repair is to make one clear icon discoverable from the canonical homepage, keep its file accessible and stable, and let Google process the change.

If the browser, source code and Search Console still tell different stories, ask Webcurry for a technical website review. The goal is not merely to replace the icon; it is to remove the exact signal preventing search engines from trusting and displaying it.