Langues

Guide Favicon SEO

Ce que a favicon is, Google's and Bing's réel requirements pour showing un in résultats de recherche (notamment the dead "multiple of 48px" myth), how to implement un correctement, and Comment corriger a favicon que isn't showing.

Première publication : 2 juil. 2026 · Dernière mise à jour : 3 août 2026 · Advanced
Langues
AIRédigé parAI v2
1 indice probant sur cette page

A favicon is the petit square site icon affiché in navigateur tabs, bookmarks, and — quand the requirements are met — suivant to votre listing in Google and Bing résultats de recherche. It's declared with <link rel="icon"> in the <head> (plus apple-touch-icon pour iOS and manifest icons pour PWAs). The unique la plupart important chose to obtenir correct: Google's old 'doit be a multiple of 48x48px' rule is DEAD as of the October 2024 docs mettre à jour — the current requirement is seulement square and au moins 8x8px, with larger-than-48px a recommendation, pas a rule. To apparaître in Google, the favicon fichier and the homepage doit les deux be crawlable (pas blocked in robots.txt), the image doit be square in a pris en charge format (SVG, ICO, PNG, GIF), and it doit live on a stable URL Google peut refetch. A favicon n’est pas a ranking factor — it's a search-appearance and brand-recognition detail, pas a documented click-through lever. Aussi worth knowing: a favicon rendering correctement in votre navigateur tab isn't proof Google accepted it — navigateur selection and Google's search eligibility are separate checks. Quand un disappears, it's a technical or policy problème, jamais a core mettre à jour. Ce deep dive sits in the meta-tags cluster alongside the title tag and meta description.

TL;DR — The favicon in the SERP is a search-appearance fonctionnalité, pas a ranking factor — it lives sous Google’s “Search appearance” docs suivant to title liens and sitelinks, and Google’s propre documentation neither establishes it as a ranking signal nor promises a click-through effect. A favicon rendering correctement in votre navigateur tab is aussi pas proof Google accepted it — navigateur selection and Google’s search eligibility are independent checks. Current Google requirements (2026): square, au moins 8×8px (the old “multiple of 48×48px” rule was killed in the Oct 2024 docs mettre à jour; “plus grand que 48×48px” is now a recommendation), quelconque valid favicon format (SVG, ICO, PNG, GIF), and two explorer gates que les deux doit réussir — Googlebot doit be able to explorer the homepage and Googlebot-Image the favicon fichier. L’URL doit be stable but besoin pas be on votre propre domain (a CDN is fine). Favicons are scoped per hostname (domain/subdomain), pas per subdirectory. Declare <link rel="icon"> in server-rendered HTML, pas via JavaScript. Quand a favicon disappears it’s usually a technical or policy problème. Expect days-to-weeks of latency pour 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? (Aucun.)

Let me obtenir the biggest question out of the façon premier, parce que a surprising amount of “favicon SEO” content is vague à propos de it. A favicon n’est pas a ranking factor. The tell is où Google fichiers the documentation: Define a favicon to montrer in résultats de recherche sits sous Search Central → Documentation → Appearance, alongside title liens, sitelinks, and the visual elements gallery — pas sous quelconque ranking-systems documentation. The favicon is partie of the attribution line of a result (favicon + site nom + URL), and it’s reasonable to think a recognizable icon helps a scanning reader spot votre listing — but Google’s propre documentation doesn’t quantify or promise quelconque click-through effect, and it dit nothing à propos de votre position. That’s the whole story on ranking.

Google’s favicon requirements (2026)

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

Ce is the unique la plupart important chose to obtenir correct, parce que la plupart competing content encore obtient it incorrect. Google’s current wording:

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

And, separately:

“Pendant que the minimum size requirement is 8x8px, we recommend en utilisant a favicon that’s plus grand que 48x48px so que it semble bon on various surfaces.”

So: square + au moins 8×8px is the requirement; larger-than-48px is a recommendation. The old wording — “Votre favicon doit be a multiple of 48px square, Par exemple: 48x48px, 96x96px, 144x144px and so on” — was replaced on 2024-10-24. Moteur de recherche Journal covered the modifier, reporting Google’s stated raison as being to reflect the réel requirements pour favicons. Yet plenty of 2026-dated guides encore repeat “multiple of 48×48px” as current fact. It isn’t. Ship a crisp square icon comfortably ci-dessus 48px and you’re fine.

Pris en charge formats

Google’s line is simply: quelconque valid favicon format is pris en charge. Plutôt que enumerate les, Google liens out to the liste of formats — En pratique ICO, PNG, GIF, and SVG are tout acceptable. There’s aucun format vous devez fight pour ici.

Crawlability — two gates, les deux doit réussir

Ce un trips personnes up parce que là are two separate explorer requirements:

“Googlebot-Image doit be able to explorer the favicon fichier and Googlebot doit be able to explorer the home page; ils ne peut pas be blocked pour exploration.”

Si soit the favicon fichier or the homepage is disallowed in robots.txt (or sinon blocked), Google won’t montrer votre favicon. Ce is the même crawl-vs-serve logic que governs the rest of the meta-tags cluster: a resource Google can’t récupérer is a resource Google can’t utiliser. Google tightened ce wording in an October 2023 docs mettre à jour, qui Moteur de recherche Land covered at the temps, naming les deux utilisateur agents explicitly.

Stable URL (and pourquoi a CDN is fine)

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

Remarque ce que ce fait pas dire: it doesn’t dire the favicon has to live on votre propre domain. It peut sit on a CDN or a separate host — Google simplement nécessite l’URL to stay constant so it peut garder refetching the même emplacement. Modifier l’URL and Google has to rediscover and re-cache the icon, qui is exactly the kind of churn que rend a favicon disappear après a migration.

Scope — un favicon per hostname

Favicons are pris en charge at the domain and subdomain level, pas the subdirectory level. Vous pouvez’t définir example.com/us/ and example.com/uk/ to montrer différent favicons in the SERP — Google treats it as un favicon per hostname. Ce matters pour multi-brand sites and subfolder international setups: si vous besoin distinct favicons per region, vous besoin distinct subdomains, pas subfolders.

Content policy

Google won’t montrer a favicon it deems inappropriate — its named exemples are pornography and hate symbols tel as swastikas — and it swaps tel imagery pour a par défaut icon. Danny Sullivan décrit the enforcement mechanism back in 2019:

“We have automated signifie and déjà peut prendre reports by ceux who utiliser the Feedback lien at the bottom of lune page or via our spam reporting page.”

So there’s les deux automated detection and a manual reporting chemin.

Aucun guarantee

Même with everything correct, Google is explicit:

“A favicon isn’t guaranteed to apparaître dans la recherche Google results, même si tout guidelines are met.”

Do the fonctionner, alors accept there’s aucun 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 Outils aider and Microsoft Q&A guidance line up closely:

  • Declare it with <link rel="icon">; accepted formats inclure .ico, .png, .gif, .jpg, and modern guidance now aussi accepts .svg.
  • Minimum 16×16px, with Bing preferring 32×32 or plus grand pour higher-resolution surfaces.
  • The favicon and homepage doit pas be disallowed in robots.txt, and le serveur doit retourner the correct Content-Type header pour the image.

Le sitemap myth. Older Bing advice (and community threads) told vous to liste votre favicon URL in votre XML sitemap. Don’t. Current meilleur pratique is to garder votre sitemap to indexable content pages seulement — moteur de recherches découvrir the favicon via the <link> tag, pas le 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 façon Google’s docs state a general crawl-freshness range. Fondé on Bing Webmaster Outils aider content and Microsoft Q&A threads, practitioners report a few days to several weeks to refresh a favicon, with complet regional propagation après a fix commonly taking roughly 1–4 weeks — treat ces as reported ranges, pas documented guarantees. Worth knowing que Bing rolled out site noms + favicons in its result snippets in April 2023, mirroring Google’s précédent rollout — and it garde iterating on favicon afficher prominence, so treat ce as an actively evolving surface, pas a solved un.

How to implement a favicon correctement

Here’s the modern stack I’d ship. Chaque line fait a spécifique 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 chaque:

  • <link rel="icon"> (and legacy shortcut icon). Ce is the load-bearing tag pour search. Google’s documented rel valeurs are icon, the legacy shortcut icon, apple-touch-icon, and apple-touch-icon-precomposed. Declare it une fois, cleanly — duplicate or conflicting favicon declarations are a courant causer of the incorrect icon (or aucun icon) showing.
  • SVG favicons, sizes="any", and dark mode. A unique SVG scales to quelconque size, so un fichier peut cover the whole range. SVGs peut aussi carry a prefers-color-scheme media requête internally, letting the icon adapt to dark mode. Pair it with a PNG fallback (commonly 32×32 or 96×96) pour older contexts que don’t prise en charge SVG favicons.
  • Web app manifest icons are pas votre SEO favicon. The icons array in manifest.json (typically 192×192 and 512×512 PNGs, and on Android généralement requis as PNG plutôt que SVG) drives the icon affiché quand a site is installed as a PWA. That’s a separate concern from the <link rel="icon"> favicon Google reads pour search. Don’t conflate les — getting votre manifest icons perfect ne fait pashing pour the SERP favicon si the <link rel="icon"> is broken.
  • Put it in server-rendered HTML, pas JavaScript. Ce is the tip la plupart competing posts omit. John Mueller has advised implementing the favicon <link> tag directement in the HTML template plutôt que injecting it client-side via JavaScript, to supprimer a possible point of échec. Si votre icon seulement apparaît après JS runs, you’ve ajouté a fragile dependency que quietly breaks the SERP favicon.

Pourquoi votre favicon isn’t showing in résultats de recherche

Ce is the highest-value utiliser cas pour la plupart personnes who land on a favicon article — the troubleshooting un, usually après a redesign, CMS migration, or CDN déplacer. The disappearance is almost jamais an algorithm mettre à jour. John Mueller has been clair que broad core updates don’t faire favicons disappear; quand un goes manquant it’s a technical or policy problème à la place. Glenn Gabe’s Favi-gone troubleshooting deep dive is the definitive rundown of the technical variations.

Premier, separate the two consumers. An icon rendering correctement in votre propre navigateur tab is pas evidence que Google accepted it. Navigateur tab/bookmark selection and Google’s search eligibility are two independent consumers of the même <link rel="icon"> markup, chaque with its propre resolution logic — votre navigateur peut montrer a mis en cache or locally-resolved icon fine pendant que Googlebot-Image has jamais successfully récupéré the même fichier, or the reverse. Don’t diagnose from “it semble correct quand I ouvrir le site” — tester chaque chemin on its propre terms: vérifier the tab locally, alors separately vérifier the explorer/eligibility conditions ci-dessus (robots.txt accès, size/format, stable URL) plutôt que treating un as proof of the autre.

The usual suspects, une fois you’ve confirmed ce is genuinely a search-side problème and pas simplement a navigateur cache:

  • A robots.txt block on the homepage or the favicon fichier (remember, two gates).
  • A broken, vide, or manquant href on the <link rel="icon"> tag.
  • Duplicate or conflicting favicon declarations à travers templates.
  • Incorrect dimensions or format (pas square, or ci-dessous the minimum).
  • A déplacé or unstable favicon URL après a CDN or host modifier.
  • A JavaScript-injected tag Google’s rendering didn’t pick up reliably.
  • CMS/platform bugs que strip or rewrite the tag.
  • A stale mis en cache par défaut persisting après a legitimate modifier.

How to force a refresh. Fix the underlying causer, alors nudge discovery: run the homepage via Search Console → Inspection d’URL → Requête Indexation pour Google, and resubmit le sitemap / requête a homepage re-crawl in Bing Webmaster Outils pour Bing. Si Bing encore won’t mettre à jour, its documented chemin is to contact prise en charge with the domain, favicon URL, and screenshots.

How long it en réalité takes. Même a entièrement correct fix peut prendre days to a few weeks pour 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”) s’applique, and a Inspection d’URL requête on the homepage is the meilleur lever vous have to speed it up. Pour Bing, expect up to roughly a month fondé on practitioner reports plutôt que an official publié timeline.

Fait a favicon en réalité affecter SEO?

Seulement in the sense que brand recognition matters. In une page of results, the favicon is partie of how a utilisateur recognizes a source ils trust avant ils lire the title. It’s plausible que peut earn vous clicks, but Google doesn’t publish données quantifying quelconque click-through effect from a favicon, so don’t treat it as a mesuré lever — it’s pas a ranking signal, and aucun amount of favicon polish va lift une page que doesn’t deserve to rank. Treat it as a branding detail with an unmeasured but plausible click-through upside — the même bucket as a well-written meta description, whose click effect is aussi widely assumed but pas something Google quantifies.

Où ce sits

The favicon <link rel="icon"> is un of le navigateur-and-appearance-facing tags in the head, so it belongs in the on-page meta-tags cluster suivant to the title tag and meta description — the autre elements que shape how votre listing semble in the SERP plutôt que how it ranks. Its crawlability requirement is a direct application of the même robots.txt crawl-control logic que runs via the whole cluster: a resource Google can’t explorer is a resource Google can’t montrer. Pour the complet map of head elements and qui ones en réalité matter, voir the Meta Tags pour le SEO hub.

Add an expert note

Pin an expert quote

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