Favicon seo across 27 homepages: all declare one, five have no /favicon.ico
Favicon seo advice says put a file at the root. Across 27 homepages read on 2026-08-23, all 27 declare an icon in HTML and every declaration resolved, while five return 404 for /favicon.ico.
FIELD TEST · 2026-08-23 · 27 homepages · single crawl · icon links resolved
Sample and method: the same 30-site panel in use since 2026-08-15, each homepage fetched once on 2026-08-23 with a browser user agent. We collected every <link> element carrying an icon rel, then made a second request for each site's primary icon and for /favicon.ico at the root.
Favicon seo advice usually reduces to one instruction — put a file at the root. On this panel that instruction is wrong twice over: all 27 homepages declare an icon in the HTML and every declared icon resolved, while five of the 27 return 404 for /favicon.ico. The declaration is doing the work; the root file is a fallback that a third of the newer sites have already dropped.
How we measured it
One HTTP request per homepage, no rendering, no retries. Inclusion was fixed before the run: status 200, body at least 10,000 bytes, body containing <body. Three of the 30 failed — stackoverflow.com and medium.com returned 403, www.reddit.com returned an 8,393-byte shell — leaving 27, the same three exclusions as previous batches.
From the delivered HTML we recorded every <link> whose rel contained the word icon, along with its href, sizes and type. Then two follow-up requests per site: the first declared rel="icon" or rel="shortcut icon", resolved against the final URL, and the bare /favicon.ico. We read declarations. We did not decode any image, so every size below is what the site says, not what the file is.
What favicon seo actually requires, per Google
Google's favicon documentation, last updated 2026-02-04 and read on 2026-08-23, is shorter than most of the advice written about it. Four requirements do the work.
| Requirement | Google's wording |
|---|---|
| Declare it in HTML | Add a <link> tag "to the header of your home page" |
| Shape and size | "a square (1:1 aspect ratio) that's at least 8x8px"; larger than 48x48px recommended |
| Crawlable | "Googlebot-Image must be able to crawl the favicon file" |
| Stable URL | "The favicon URL must be stable (don't change the URL frequently)" |
Two details in that page get lost in retellings. The old "multiple of 48px" phrasing is gone — the current floor is 8x8 and 48 is a recommendation. And there is exactly one favicon per hostname: "Google Search only supports one favicon per site, where a site is defined by the hostname." Declaring eighteen of them does not give you eighteen.
The root file is a habit. The link element is the instruction.
Nobody is missing a favicon, and five are missing the root file
All 27 homepages declare at least one icon link, 122 across the panel, a median of three per site. Three sites declare exactly one — nextjs.org, news.ycombinator.com and slack.com — and supabase.com declares 18, all pointing into one /favicon/ directory.
| Check | Sites | Detail |
|---|---|---|
| Declares an icon link | 27 of 27 | 122 link elements total |
| Primary icon returns 200 | 27 of 27 | No broken declarations |
| /favicon.ico returns 404 | 5 of 27 | notion, figma, discord, supabase, framer |
| Declares a size at all | 18 of 27 | 9 ship no sizes attribute |
| Largest declared size under 48 | 3 of 27 | mozilla, netlify, substack at 32x32 |
The five with no root file are all product sites built in the last few years, and all five declare a working icon in the HTML, so none of them has a problem — supabase.com points at /favicon/favicon.ico, which returns a 417-byte icon, while the bare root path 404s. It is a reminder that the two paths are unrelated. If your only favicon plan is dropping a file at the root and never mentioning it, that plan is one deployment change away from silence.
Sizes: what sites declare versus what Google reads
Nine of 27 ship no sizes attribute at all, which is legal and tells Google nothing. Of the 18 that do declare, the largest declared square ranges from 32 to 512 pixels, with www.theverge.com at the top. Three sites top out at 32x32, below the size Google recommends.
One site declares its sizes with a character that is not x. www.nytimes.com ships sizes="144×144" and sizes="114×114" using the multiplication sign U+00D7 rather than the letter, on two apple-touch-icon-precomposed elements. That is not a valid size list, so those two declarations carry no size information at all. Its other icons are fine, and this is a typo in a generated template rather than a live problem — which is precisely the kind of thing that survives for years because nothing reports it.
Three rel values Google does not list
Google names four values it supports: icon, shortcut icon, apple-touch-icon and apple-touch-icon-precomposed. The panel also ships three it does not name — mask-icon on github.com, www.theverge.com and www.bbc.com, alternate icon on github.com and www.bbc.com, and fluid-icon on github.com alone.
None of those are mistakes. mask-icon is a Safari pinned-tab feature and fluid-icon belongs to a macOS app wrapper; they exist for reasons that have nothing to do with search. Worth knowing only so that a site audit does not report them as errors: GitHub declares four icon links and exactly one of them is the kind Google reads.
What this means for your site
Three checks, in the order they fail.
- Declare
<link rel="icon">on the home page and confirm the href returns 200 from outside your network. Every site in this panel passes this, which makes failing it conspicuous. - Keep the URL stable across deploys. Google asks for this explicitly, and build tooling that fingerprints asset filenames works against it.
- Do not rely on
/favicon.icoalone. Five of 27 large sites no longer serve it, and nothing in Google's documentation promises it will be found without a declaration.
The favicon is the smallest of the things that decide how a result looks in a list. The two larger ones are the title and the snippet, and the method for those is written up in how to write a meta description. For the machine-readable side of the same question — who the site says it is — see which homepages declare organization schema. If you want the whole diagnosis path rather than one element at a time, start here.
Common questions
How did you measure this?
One homepage request per site on 2026-08-23, plus two follow-up requests per site for the primary declared icon and for /favicon.ico. Declarations were read from the delivered HTML; no JavaScript ran, and no image file was decoded.
Does the favicon affect rankings?
Google's documentation presents it as a search appearance feature, not a ranking factor, and adds that a favicon "isn't guaranteed to appear in Google Search results, even if all guidelines are met". Nothing in this crawl speaks to rankings either way.
What size should the file be?
Square, at least 8x8, with anything above 48x48 recommended so it holds up on different surfaces. We cannot tell you what these 27 sites actually ship, because we read the declared sizes and never decoded the images — nine of them declare no size at all, and their files could be any dimension.
Do I need separate icons for Apple devices?
Google reads apple-touch-icon and apple-touch-icon-precomposed as favicon sources, so they are not wasted. Whether you need them at all is an iOS home-screen question rather than a search one.
