Skip to content

Favicon not showing in Google Search: causes and fixes

Favicon shows in your browser tab but not in Google Search? Check Google's requirements, robots.txt rules for Googlebot-Image, the link tag and redirects.

By Crawlito · Updated 8 min read

In short

  • Google's documentation requires a link tag in the head of your home page, a home page Googlebot can crawl, and a favicon file that Googlebot-Image can crawl, not blocked by robots.txt.
  • The favicon must be square, at least 8x8 px, in BMP, GIF, ICO, PNG, JPEG, PPM or TIFF format, and Google recommends larger than 48x48 px.
  • A favicon in your browser tab proves only that your browser found an icon; it does not prove that Google's crawlers can fetch the same file.
  • Google supports one favicon per hostname, so www.example.com and example.com are separate sites for this purpose.
  • Google says recrawling can take several days to several weeks and that a favicon is not guaranteed to appear even when every guideline is met.
On this page

If your favicon shows in the browser tab but not next to your result in Google, one of Google's requirements is probably not met. The usual culprits are a robots.txt rule that blocks the icon file from Googlebot-Image, a missing or wrong <link rel="icon"> tag on the home page, an icon that is too small or in an unsupported format, or a home page that sits behind a redirect Googlebot cannot follow. Fix those, request a recrawl of the home page, and then wait: Google says the change can take days to weeks.

One caveat first. Google's documentation says a favicon is not guaranteed to appear in search results even when every guideline is met. This guide removes the technical reasons it could be missing. It cannot make Google show it.

What Google requires for a favicon in search results

Google's favicon guidelines are short. At the time of writing, they say:

RequirementWhat Google says
Link tagAdd a <link> tag with rel="icon" to the header of your home page
Crawlable home pageGooglebot must be able to crawl the home page and follow any redirects to the page that specifies the favicon
Crawlable icon fileGooglebot-Image must be able to crawl the favicon file; the URLs must not be blocked by robots.txt
Shape and sizeSquare (1:1 aspect ratio) and at least 8x8 px; larger than 48x48 px is recommended
FormatBMP, GIF, ICO, PNG, JPEG, PPM or TIFF
Stable URLThe favicon URL must be stable, so do not change it often
One per siteOne favicon per site, where a site is defined by the hostname
AppropriateGoogle does not show a favicon it considers inappropriate, such as pornography or hate symbols

The href can be a relative path or an absolute URL, and the file does not have to live on your own domain, so a CDN is fine.

Work through the table in order. Most missing favicons fail on the crawlable rows.

Why it shows in the browser tab but not in Google

The tab icon and the search icon come from different fetches. Your browser finds an icon for the tab by itself, using your own connection, as a visitor. Google's search favicon is processed from your home page by Google's crawlers, and Google documents its own conditions for it.

That is why "I can see it in my tab" is not a test. Two cases explain most of the gap:

  • Robots.txt applies to crawlers, not visitors. Google's robots.txt introduction describes the file as telling crawlers which URLs they can access. A rule that blocks the folder holding your icon does not affect a person's browser, but it does affect Googlebot-Image.
  • Google reads a specific place. Google's guidelines name the <link> tag in the head of your home page. If your icon only works in the tab because of how the browser looks for it, and the home page has no link tag, Google has nothing documented to read. Add the tag instead of relying on defaults, which Google's page does not describe.

Check that the favicon URL is crawlable

This is the check to do first, because it is both common and easy to miss.

Google's list of common crawlers says that crawling preferences addressed to the Googlebot-Image user agent affect Google Images, Discover, Video mode and all features in Google Search where images, logos and favicons are presented. It also says these common crawlers always obey robots.txt rules when crawling automatically. So a robots.txt rule that blocks your icon from Googlebot-Image can keep it out of results.

Find the favicon URL

Open your home page source and find the link tag.

bash
curl -s https://example.com/ | grep -io '<link[^>]*rel="[^"]*icon[^>]*>'

Take the href and make it absolute. For example, /assets/icons/favicon.png becomes https://example.com/assets/icons/favicon.png.

Look for rules that cover it

Fetch your robots.txt and look at the rules that apply.

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

Rules like these block an icon that lives in a folder you meant to hide:

User-agent: *
Disallow: /assets/
Disallow: /static/
Disallow: /wp-content/

Two details matter:

  • Google's crawlers use one group: the one with the most specific user agent that matches. If you have a Googlebot-Image group, only that group applies to it, and your * rules do not. If you have none, it follows your Googlebot group: Google lists Googlebot as a second token for Googlebot-Image and says you need to match only one token for a rule to apply. Only if there is no Googlebot group either does it use *. See Googlebot-Image, Video and News tokens.
  • Rules apply only to the host, protocol and port that serve the file. If your icon is on a CDN or asset subdomain, that host needs its own correct robots.txt.

The fix is to allow the icon file explicitly or move it outside the blocked path:

User-agent: *
Disallow: /assets/
Allow: /assets/icons/favicon.png

Our guides on robots.txt mistakes and testing robots.txt against each crawler show how to confirm which group a crawler follows.

Check the status code

Request the icon and look at the response.

bash
curl -sI https://example.com/assets/icons/favicon.png

You want a 200 and an image content type. Google's favicon page does not say how Google treats an icon that returns an error, but an icon that returns 403, 404 or a login page cannot be read as an image. If the icon redirects, follow the chain with curl -sIL and keep it short. How crawlers treat each code is covered in status codes and redirects. A firewall or CDN rule that refuses Google's crawlers is a separate cause of the same symptom: see fixing Googlebot 403 blocks.

A valid setup is one line in the <head> of the home page:

html
<link rel="icon" href="/favicon.png" type="image/png">

Google lists icon as the standard rel value. It says shortcut icon is supported for historical reasons, and that apple-touch-icon and apple-touch-icon-precomposed are also accepted for iOS-style icons. Use rel="icon" unless you have a reason not to.

Then check the file itself:

  • Square. A 1:1 ratio. A wide logo squeezed into a favicon slot fails this.
  • Large enough. At least 8x8 px is the minimum. Google recommends larger than 48x48 px so it looks good on different surfaces. A common safe choice is a square PNG or ICO file well above that size.
  • A listed format. BMP, GIF, ICO, PNG, JPEG, PPM or TIFF. SVG is not in Google's list at the time of writing, so if your site only offers an SVG icon, add a PNG or ICO as well.

If a script or framework adds your link tag, check the raw HTML, not just the browser's Elements panel, because the tag has to be there when Googlebot fetches the page. Raw HTML vs rendered HTML shows how to compare the two.

Homepage duplicates: http, www and redirects that confuse the icon

Google's guidelines tie the favicon to the home page and to the hostname. That makes duplicated home pages a plausible cause of a missing icon.

  • Hostnames count separately. Google says one favicon is supported per site, where a site is the hostname. www.example.com and example.com are different hostnames. A subdirectory such as example.com/news cannot have its own favicon and falls under the hostname's.
  • Redirects must be followable. Googlebot has to be able to follow redirects to the page that specifies the favicon. A redirect loop, a chain that ends on an error, or a redirect to a login page defeats that. Pick one version of your home page (https, with or without www) and redirect the others to it with a single 301.
  • Put the tag on the page that finally loads. If http://example.com/ redirects to https://www.example.com/, the link tag must be in the HTML of the final page. Check it with curl -sL.

Google's favicon page does not describe how it chooses between duplicate home pages. So do not rely on it to pick for you. Make every version agree on one canonical home page, using the approach in canonical tags and duplicate URLs, and make sure the hostname you see in search results is the one whose home page carries the tag.

How long a change takes and how to request a recrawl

After you fix the problem, Google has to recrawl and reprocess your home page. Google says crawling can take anywhere from several days to several weeks. It does not give a firm date.

To nudge it along:

  1. Confirm the fixes with curl first, so you do not request a recrawl of a page that is still broken.
  2. In Search Console, open the URL Inspection tool, enter your home page URL and choose Request indexing. Google's favicon page names this as the way to request it.
  3. Leave the favicon URL unchanged afterwards. Google's guidelines ask for a stable URL and say not to change it frequently.

Google's URL Inspection help says a request does not guarantee indexing and that there is a daily limit on index requests, so one request for the home page is enough. If you changed only the image behind an unchanged URL, expect the same several-days-to-weeks window.

If everything checks out after a few weeks, Google's favicon page offers a feedback form for favicon handling. It says feedback helps improve Search but does not promise action on individual sites.

Frequently asked questions

The browser fetches the tab icon as a visitor, while Google reads your home page and the icon file with its own crawlers. A robots.txt block on Googlebot-Image, a missing link tag on the home page or a failed redirect can affect Google and leave your tab untouched.

How big should my favicon be for Google?

Square and at least 8x8 px, per Google's guidelines, with larger than 48x48 px recommended. Use one of the supported formats: BMP, GIF, ICO, PNG, JPEG, PPM or TIFF.

Does Google use my /favicon.ico file automatically?

Google's favicon documentation does not say it does. It names the <link> tag in the head of the home page, so add that tag and point it at your icon.

Can I have a different favicon for each subdirectory?

No. Google supports one favicon per hostname. A path such as example.com/news falls under the favicon of example.com, while a different hostname such as news.example.com can have its own.

The favicon passes every check and still does not show. Why?

Google says a favicon is not guaranteed to appear even when all guidelines are met, and recrawling can take several weeks. Keep the setup stable, avoid changing the URL, and give it time.

Check your own pages

The free check reads one page the way crawlers do, with no account needed: the robots.txt rules for named crawlers, response headers and whether key content is in the raw HTML. For the favicon-specific checks, use the commands above. If you suspect a site-wide problem with blocked paths or redirects, an audit runs the checks across up to 500 pages with evidence and prioritized fixes.

Filed under Structure and schema. Topics: metadata, google, troubleshooting, robots-txt