Favicon not showing on google search


Hi Webflow community,

I’ve uploaded my favicon through Site Settings → General → Favicon and also added the favicon link in Custom Code → Head, but I noticed that the favicon isnt being shown in google search. its been 1-2 months. on page its showing the favicon on the tab. but only google search results is not.

1 Like

Hi there,

For optimal favicon implementation, you should add it in a single location through Site Settings > General tab > Icons. Using multiple favicon implementations (like in both Site Settings and Custom Code) can create conflicts that prevent proper display.

To ensure your favicon works correctly:

  1. Remove any favicon code from the Head code section
  2. Keep the favicon only in Site Settings
  3. Use a 32x32 pixel favicon image for optimal display
  4. Publish your site and refresh your browser to see the changes

Hopefully this helps! If you still need assistance, please reply here so somebody from the community can help.

2 Likes

Hi Kylie,

I have a tool here where you can see what Google has indexed for your favicon;

Google Favicons

Enter your exact domain with the https;

https://www.premiumprinting.sg 

It looks like it hasn’t indexed anything useful.

You might be able to expedite that by adding an Organization JSON-LD schema;

Troubleshooting Favicons | Favicons in Webflow | Sygnal-U

3 Likes

I have the same problem. I added a favicon in the correct size of 32*32 pixels two months ago, but the favicon only appears in the browser tab, not in Google search. I have created about a hundred websites on React, WordPress, Next.js, and regular CSS/HTML/JS, and I have never had any problems. The site is indexed, robots.txt is configured correctly, Organization JSON-LD schema is added, but there is no result. The service Google Favicons shows the icon. The site is added to Google Search Console, Request indexing is completed… Does anyone have any ideas why the icon is not displayed?

2 Likes

@Volodymyr_Kosynskyi

Google uses a different process for displaying favicons in search results than browsers do for tabs. A browser can display a 32x32 pixel icon, but Google’s crawlers follow a specific set of guidelines.

Google’s minimum recommendation: To ensure your favicon displays correctly in Google search results, you must provide a version that is a multiple of 48x48 pixels (e.g., 48x48, 96x96, 144x144, 192x192). While the technical minimum is 8x8 pixels, a size of 48x48 or greater is recommended for consistent, high-quality rendering.

2 Likes

Thank you very much for your response, but I added the favicon in the standard webflow interface (Site Settings → General) with a size of 32*32px.
Also in the head I added a separate link <link rel=“icon” …69189822c862043fc0abbe26_48px-favicon.png" type=“image/png” sizes=“48x48”> with a size of 48
*48px according to the documentation.
The icon opens via a direct link, it is not blocked by robots.txt. I checked on third-party services (https://faviconcheck.tamethebots.com, Google Favicons , https://seositecheckup.com/ ) whether everything is fine with it - on all resources - the favicon is valid. When I enter my site in Google - in the “Images” section - the pictures are shown with the favicon, and in the “All” section - without it.
At the same time in other search engines, such as:
qwant
ecosia
duckduckgo - favicon is also there.
The site has been added to Google Search Console, the main page has been sent for checking request indexing of my site’s home page.
Also added script type=“application/ld+json” with “@type”: “WebSite” and “@type”: “Organization”,

EVERYTHING has been done according to the instructions and recommendations, but there is still no result

Hi all,

I’ve never encountered this issue before with Webflow. Normally I set up a project, define the favicon and webclip via Page Settings, and Google displays the favicon correctly. I have never used custom favicon code.

However, the last three client websites I built and published do not display the favicon correctly in Google. At first I assumed slow indexing, but after checking with multiple tools, the issue persists.

What I’ve verified so far:

  • Google Favicons – All domain variants work (https / www) ✓

  • Google Search Console (favicon is listed correctly there) ✓

  • <head> code is identical to older projects where the favicon works ✓

  • Connected Google Business Profile, with correct logo ✓

This makes me wonder what has changed. If this happened once, I’d assume a Google glitch — but three sites in a row seems unlikely.

The only real difference compared to older projects is that these sites include JSON-LD structured data. That leads me to suspect the issue might be related to missing logo declarations in the JSON-LD.

My current hypothesis: when Google detects <script type="application/ld+json">, a logo field may be required, otherwise the favicon is ignored — even though sites without JSON-LD work fine.

If that’s the case, it’s confusing, since favicon and search result branding are important signals, and the structured data validation tools do not flag this as an error.

I’m going to add a logo field now and see what happens. If anyone has additional insight, I’d appreciate it.

Cheers.

What I described above was all correct. I had to wait three months for the result.

Google can be very slow with this but in theory it rechecks favicon regularly.

Try creating a 48x48 version and put in the site-wide head yourself. At least historically Google has always officially required a multiple of 48x48.

I use a different tactic on especially tough sites where I have a cloudflare worker that dynamically constructs a favicon.ico from your existing Webflow favicon assets. In some cases that gets picked up faster by Google.

If your DNS is on Cloudflare, happy to set that up for you at no charge, I’m looking for sites with this problem to see how quickly and consistently it resolves favicon issues.

Ok … guys.

I can confirm: Google needs quite some time :man_facepalming: Stupidly long if you ask me.
Anyway. That means, that favicons via the Webflow interface still work as well (I guess).

Thanks for you help.