Favicon SEO

What a favicon is, Google's and Bing's real requirements for showing one in search results (including the dead "multiple of 48px" myth), how to implement one correctly, and how to fix a favicon that isn't showing.

First published: Jul 2, 2026 · Last updated: Jul 18, 2026 · Advanced
demand #1 in Meta Tags#1 in On-Page#7 in Technical SEO#12 on the site
AIAuthored byAI v2
1 evidence signal on this page

A favicon is the small square site icon shown in browser tabs, bookmarks, and — when the requirements are met — next to your listing in Google and Bing search results. It's declared with <link rel="icon"> in the <head> (plus apple-touch-icon for iOS and manifest icons for PWAs). The single most important thing to get right: Google's old 'must be a multiple of 48x48px' rule is DEAD as of the October 2024 docs update — the current requirement is only square and at least 8x8px, with larger-than-48px a recommendation, not a rule. To appear in Google, the favicon file and the homepage must both be crawlable (not blocked in robots.txt), the image must be square in a supported format (SVG, ICO, PNG, GIF), and it must live on a stable URL Google can refetch. A favicon is NOT a ranking factor — it's a search-appearance and brand-recognition detail, not a documented click-through lever. Also worth knowing: a favicon rendering correctly in your browser tab isn't proof Google accepted it — browser selection and Google's search eligibility are separate checks. When one disappears, it's a technical or policy issue, never a core update. This deep dive sits in the meta-tags cluster alongside the title tag and meta description.

TL;DR — The faviconA favicon (\"favorite icon\") is the small square image that represents a website — shown in browser tabs, bookmarks, and history, and (when the requirements are met) next to a site's listing in Google and Bing search results. It's declared with an HTML <link rel=\"icon\"> tag in the <head>. It is not a ranking factor, but it affects brand recognition and click-through rate. in the SERP is a search-appearance feature, not a ranking factor — it lives under Google’s “Search appearance” docs next to title linksThe title tag is the HTML title element in a page's head that specifies the document's title. It's the primary source for the SERP title link and a confirmed light ranking factor — but since August 2021 Google doesn't always show it verbatim. and sitelinksSitelinks are extra links from the same domain that Google clusters together under a single search result, usually for branded or navigational queries. They're generated entirely algorithmically — there's no way to add, edit, or guarantee them., and Google’s own documentation neither establishes it as a ranking signal nor promises a click-through effect. A favicon renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. correctly in your browser tab is also not proof Google accepted it — browser selection and Google’s search eligibility are independent checks. Current Google requirements (2026): square, at least 8×8px (the old “multiple of 48×48px” rule was killed in the Oct 2024 docs update; “larger than 48×48px” is now a recommendation), any valid favicon format (SVG, ICO, PNG, GIF), and two crawl gates that both must pass — GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer. must be able to crawl the homepage and GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer.-Image the favicon file. The URL must be stable but need not be on your own domain (a CDN is fine). Favicons are scoped per hostname (domain/subdomain), not per subdirectory. Declare <link rel="icon"> in server-rendered HTML, not via JavaScript. When a favicon disappears it’s usually a technical or policy issue. Expect days-to-weeks of latency for a fix to propagate.

Evidence for this claim Google Search favicon eligibility requires a crawlable favicon and home page, a square icon, and a stable URL; Google recommends sizes larger than the 8x8 minimum. Scope: Current Google Search favicon requirements and recommendations. Confidence: high · Verified: Google Search Central: Define a favicon Evidence for this claim HTML defines link rel=icon for associating an icon resource with a document; browser selection behavior is separate from Google Search display eligibility. Scope: Current HTML link-type definition. Confidence: high · Verified: WHATWG HTML: Link type icon

Is a favicon a ranking factor? (No.)

Let me get the biggest question out of the way first, because a surprising amount of “favicon SEO” content is vague about it. A favicon is not a ranking factor. The tell is where Google files the documentation: Define a favicon to show in search results sits under Search Central → Documentation → Appearance, alongside title links, sitelinksSitelinks are extra links from the same domain that Google clusters together under a single search result, usually for branded or navigational queries. They're generated entirely algorithmically — there's no way to add, edit, or guarantee them., and the visual elements gallery — not under any ranking-systems documentation. The favicon is part of the attribution line of a result (favicon + site name + URL), and it’s reasonable to think a recognizable icon helps a scanning reader spot your listing — but Google’s own documentation doesn’t quantify or promise any click-through effect, and it says nothing about your position. That’s the whole story on ranking.

Google’s favicon requirements (2026)

Size and shape — the “multiple of 48px” myth, corrected

This is the single most important thing to get right, because most competing content still gets it wrong. Google’s current wording:

“Your favicon must be a square (1:1 aspect ratio) that’s at least 8x8px.”

And, separately:

“While the minimum size requirement is 8x8px, we recommend using a favicon that’s larger than 48x48px so that it looks good on various surfaces.”

So: square + at least 8×8px is the requirement; larger-than-48px is a recommendation. The old wording — “Your favicon must be a multiple of 48px square, for example: 48x48px, 96x96px, 144x144px and so on” — was replaced on 2024-10-24. Search Engine Journal covered the change, reporting Google’s stated reason as being to reflect the actual requirements for favicons. Yet plenty of 2026-dated guides still repeat “multiple of 48×48px” as current fact. It isn’t. Ship a crisp square icon comfortably above 48px and you’re fine.

Supported formats

Google’s line is simply: any valid favicon format is supported. Rather than enumerate them, Google links out to the list of formats — in practice ICO, PNG, GIF, and SVG are all acceptable. There’s no format you need to fight for here.

Crawlability — two gates, both must pass

This one trips people up because there are two separate crawl requirements:

“Googlebot-Image must be able to crawl the favicon file and Googlebot must be able to crawl the home page; they cannot be blocked for crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor..”

If either the favicon file or the homepage is disallowed in robots.txt (or otherwise blocked), Google won’t show your favicon. This is the same crawl-vs-serve logic that governs the rest of the meta-tags clusterMeta tags are HTML elements in a page's head that pass metadata about the page to search engines and browsers. For SEO only a few matter — the title element, the meta description, and the robots meta tag — while meta keywords and most others are ignored.: a resource Google can’t fetch is a resource Google can’t use. Google tightened this wording in an October 2023 docs update, which Search Engine Land covered at the time, naming both user agentsA user agent is the HTTP request header a client (browser, crawler, or bot) sends to identify itself. For crawlers, a short user-agent token — a substring of that string — is what robots.txt rules actually target. explicitly.

Stable URL (and why a CDN is fine)

“The favicon URL must be stable (don’t change the URL frequently).”

Note what this does not say: it doesn’t say the favicon has to live on your own domain. It can sit on a CDN or a separate host — Google just needs the URL to stay constant so it can keep refetching the same location. Change the URL and Google has to rediscover and re-cache the icon, which is exactly the kind of churn that makes a favicon disappear after a migration.

Scope — one favicon per hostname

Favicons are supported at the domain and subdomain level, not the subdirectory level. You can’t set example.com/us/ and example.com/uk/ to show different favicons in the SERP — Google treats it as one favicon per hostname. This matters for multi-brand sites and subfolder international setups: if you need distinct favicons per region, you need distinct subdomains, not subfolders.

Content policy

Google won’t show a favicon it deems inappropriate — its named examples are pornography and hate symbols such as swastikas — and it swaps such imagery for a default icon. Danny Sullivan described the enforcement mechanism back in 2019:

“We have automated means and already can take reports by those who use the Feedback link at the bottom of the page or through our spam reporting page.”

So there’s both automated detection and a manual reporting path.

No guarantee

Even with everything correct, Google is explicit:

“A favicon isn’t guaranteed to appear in Google Search results, even if all guidelines are met.”

Do the work, then accept there’s no SLA on it appearing.

Bing’s favicon requirements

Bing doesn’t publish a standalone favicon guidelines page as prominent as Google’s, but the practical requirements from Bing Webmaster ToolsMicrosoft's free portal for monitoring and improving how a site appears in Bing search — the peer to Google Search Console, plus IndexNow instant indexing, richer backlink data, and keyword volumes. Because Bing's index also feeds Microsoft Copilot, it doubles as a window into AI-search visibility. help and Microsoft Q&A guidance line up closely:

  • Declare it with <link rel="icon">; accepted formats include .ico, .png, .gif, .jpg, and modern guidance now also accepts .svg.
  • Minimum 16×16px, with Bing preferring 32×32 or larger for higher-resolution surfaces.
  • The favicon and homepage must not be disallowed in robots.txt, and the server must return the correct Content-Type header for the image.

The sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. myth. Older Bing advice (and community threads) told you to list your favicon URL in your XML sitemapAn XML sitemap is a UTF-8 file listing the canonical URLs on your site (with optional lastmod) so search engines can discover and prioritize them. It's a discovery and diagnostic aid, not a guarantee of indexing — and Google ignores its priority and changefreq tags.. Don’t. Current best practice is to keep your sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. to indexable content pages only — search engines discover the favicon through the <link> tag, not the sitemap. Multiple 2026 troubleshooting write-ups now flag the sitemap advice as stale.

How long Bing takes. Bing doesn’t publish an official refresh SLA the way Google’s docs state a general crawl-freshness range. Based on Bing Webmaster ToolsMicrosoft's free portal for monitoring and improving how a site appears in Bing search — the peer to Google Search Console, plus IndexNow instant indexing, richer backlink data, and keyword volumes. Because Bing's index also feeds Microsoft Copilot, it doubles as a window into AI-search visibility. help content and Microsoft Q&A threads, practitioners report a few days to several weeks to refresh a favicon, with full regional propagation after a fix commonly taking roughly 1–4 weeks — treat these as reported ranges, not documented guarantees. Worth knowing that Bing rolled out site names + favicons in its result snippets in April 2023, mirroring Google’s earlier rollout — and it keeps iterating on favicon display prominence, so treat this as an actively evolving surface, not a solved one.

How to implement a favicon correctly

Here’s the modern stack I’d ship. Each line does a specific job:

<!-- Primary, scalable icon (one file covers every size) -->
<link rel="icon" href="/favicon.svg" type="image/svg+xml" sizes="any">
<!-- PNG fallback for contexts without SVG favicon support -->
<link rel="icon" href="/favicon-32.png" type="image/png" sizes="32x32">
<!-- Legacy .ico for maximum browser-tab compatibility -->
<link rel="icon" href="/favicon.ico" sizes="16x16">
<!-- iOS home-screen bookmark icon -->
<link rel="apple-touch-icon" href="/apple-touch-icon.png"><!-- 180x180 typical -->
<!-- PWA install icons live in the manifest, not here -->
<link rel="manifest" href="/site.webmanifest">

A few notes on each:

  • <link rel="icon"> (and legacy shortcut icon). This is the load-bearing tag for search. Google’s documented rel values are icon, the legacy shortcut icon, apple-touch-icon, and apple-touch-icon-precomposed. Declare it once, cleanly — duplicate or conflicting favicon declarations are a common cause of the wrong icon (or no icon) showing.
  • SVG favicons, sizes="any", and dark mode. A single SVG scales to any size, so one file can cover the whole range. SVGs can also carry a prefers-color-scheme media query internally, letting the icon adapt to dark mode. Pair it with a PNG fallback (commonly 32×32 or 96×96) for older contexts that don’t support SVG favicons.
  • Web app manifest icons are not your SEO favicon. The icons array in manifest.json (typically 192×192 and 512×512 PNGs, and on Android generally required as PNG rather than SVG) drives the icon shown when a site is installed as a PWA. That’s a separate concern from the <link rel="icon"> favicon Google reads for search. Don’t conflate them — getting your manifest icons perfect does nothing for the SERP favicon if the <link rel="icon"> is broken.
  • Put it in server-rendered HTML, not JavaScript. This is the tip most competing posts omit. John Mueller has advised implementing the favicon <link> tag directly in the HTML template rather than injecting it client-side via JavaScript, to remove a possible point of failure. If your icon only appears after JS runs, you’ve added a fragile dependency that quietly breaks the SERP favicon.
TIP Audit the declared icon set and fetch paths

An SVG is optional—not a Google requirement—but this coverage finding can reveal that a site relies only on legacy raster icons. The more important checks remain a valid declaration, a crawlable stable URL, square dimensions, and a successful image response.

Run the homepage through my favicon checker to inspect declarations, formats, fetchability, and implementation gaps in one result. Favicon Checker Free

  1. Test the canonical homepage and confirm the favicon link exists in server-delivered head markup.
  2. Open each resolved icon URL and verify a successful image response, stable path, square dimensions, and crawl access.
  3. Treat SVG as modern-browser coverage, not a Search requirement; retain an appropriate fallback for the contexts you support.
This is a coverage suggestion, not a Google eligibility failure: supported raster formats can still satisfy Search requirements.

Why your favicon isn’t showing in search results

This is the highest-value use case for most people who land on a favicon article — the troubleshooting one, usually after a redesign, CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms. migration, or CDN move. The disappearance is almost never an algorithm update. John Mueller has been clear that broad core updates don’t make favicons disappear; when one goes missing it’s a technical or policy issue instead. Glenn Gabe’s Favi-gone troubleshooting deep dive is the definitive rundown of the technical variations.

First, separate the two consumers. An icon renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. correctly in your own browser tab is not evidence that Google accepted it. Browser tab/bookmark selection and Google’s search eligibility are two independent consumers of the same <link rel="icon"> markup, each with its own resolution logic — your browser can show a cached or locally-resolved icon fine while Googlebot-Image has never successfully fetched the same file, or the reverse. Don’t diagnose from “it looks right when I open the site” — test each path on its own terms: check the tab locally, then separately verify the crawl/eligibility conditions above (robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. access, size/format, stable URL) rather than treating one as proof of the other.

The usual suspects, once you’ve confirmed this is genuinely a search-side issue and not just a browser cache:

  • A robots.txt block on the homepage or the favicon file (remember, two gates).
  • A broken, empty, or missing href on the <link rel="icon"> tag.
  • Duplicate or conflicting favicon declarations across templates.
  • Wrong dimensions or format (not square, or below the minimum).
  • A moved or unstable favicon URL after a CDN or host change.
  • A JavaScript-injected tag Google’s rendering didn’t pick up reliably.
  • CMS/platform bugs that strip or rewrite the tag.
  • A stale cached default persisting after a legitimate change.

How to force a refresh. Fix the underlying cause, then nudge discovery: run the homepage through Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. → URL Inspection → Request IndexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. for Google, and resubmit the sitemap / request a homepage re-crawl in Bing Webmaster Tools for Bing. If Bing still won’t update, its documented path is to contact support with the domain, favicon URL, and screenshots.

How long it actually takes. Even a fully correct fix can take days to a few weeks for Google to reflect in the SERP — Google doesn’t publish a fixed favicon refresh interval, but its general crawl-freshness language (“several days to several weeks”) applies, and a URL Inspection request on the homepage is the best lever you have to speed it up. For Bing, expect up to roughly a month based on practitioner reports rather than an official published timeline.

Does a favicon actually affect SEO?

Only in the sense that brand recognition matters. In a page of results, the favicon is part of how a user recognizes a source they trust before they read the title. It’s plausible that can earn you clicks, but Google doesn’t publish data quantifying any click-through effect from a favicon, so don’t treat it as a measured lever — it’s not a ranking signal, and no amount of favicon polish will lift a page that doesn’t deserve to rank. Treat it as a branding detail with an unmeasured but plausible click-through upside — the same bucket as a well-written meta descriptionThe meta description is an HTML head tag — `<meta name=\"description\" content=\"…\">` — that suggests a short summary of the page for the search snippet. It's not a Google ranking factor, and Google rewrites it the majority of the time, but a good one can still lift click-through., whose click effect is also widely assumed but not something Google quantifies.

Where this sits

The favicon <link rel="icon"> is one of the browser-and-appearance-facing tags in the head, so it belongs in the on-page meta-tags cluster next to the title tagThe title tag is the HTML title element in a page's head that specifies the document's title. It's the primary source for the SERP title link and a confirmed light ranking factor — but since August 2021 Google doesn't always show it verbatim. and meta descriptionThe meta description is an HTML head tag — `<meta name=\"description\" content=\"…\">` — that suggests a short summary of the page for the search snippet. It's not a Google ranking factor, and Google rewrites it the majority of the time, but a good one can still lift click-through. — the other elements that shape how your listing looks in the SERP rather than how it ranks. Its crawlabilityCrawlability is how well search engine crawlers can discover, access, and fetch a site's pages. A crawlability issue is any technical condition — blocked access, broken links, server failures, or bloated URL inventory — that stops pages from reaching the index. requirement is a direct application of the same robots.txtMeta tags are HTML elements in a page's head that pass metadata about the page to search engines and browsers. For SEO only a few matter — the title element, the meta description, and the robots meta tag — while meta keywords and most others are ignored. crawl-control logic that runs through the whole cluster: a resource Google can’t crawl is a resource Google can’t show. For the full map of head elements and which ones actually matter, see the Meta Tags for SEO hubMeta tags are HTML elements in a page's head that pass metadata about the page to search engines and browsers. For SEO only a few matter — the title element, the meta description, and the robots meta tag — while meta keywords and most others are ignored..

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.