Info Missing favicon link

Why a page should link its own favicon, and what happens in the browser tab and bookmarks when it's missing.

The validator flags a document with no <link rel="icon"> (or the older rel="shortcut icon") anywhere in <head>.

Example

<head>
  <link rel="icon" href="/favicon.ico" sizes="any">
  <link rel="icon" href="/icon.svg" type="image/svg+xml">
  <link rel="apple-touch-icon" href="/apple-touch-icon.png">
</head>

A single <link rel="icon" href="/favicon.ico"> is enough to satisfy this check — the extra SVG and Apple touch icon lines above are common companions, not requirements.

Why it matters

Without an explicit favicon link, browsers still request /favicon.ico at the domain root by default — so a missing link tag isn't fatal, but it means you have no control over the icon and, if that default path 404s (as it does on most single-page apps and API-driven sites), the tab shows a blank or generic icon. It's a small detail, but a missing or broken favicon is one of the more visible signs of an unfinished site, showing up in every open tab, bookmark, and browser history entry.

Frequently asked questions

Does a missing favicon hurt SEO?

Not directly as a ranking factor, but Google does display a page's favicon next to its result on mobile search — a missing or broken one makes a listing look less polished next to competitors that have one.

What format should a favicon be?

A .ico file is the safest baseline for broad compatibility, but modern browsers also support .png and .svg via rel="icon". Multiple <link rel="icon"> tags with different sizes/formats is the current best practice.