Quick answer
NOTABIS reports a missing favicon when no icon link is declared in the crawled document head. Favicons identify a site in browser tabs, bookmarks, and some device interfaces; they are not a substitute for a page title or a direct search-ranking signal. Add an appropriate icon when the site needs one and check that the URL is reachable.
What the issue means
The audit looks for link elements whose rel contains icon, including the common shortcut icon form. A site can still render normally without one. The finding means the declaration was absent from the measured HTML, not that a particular icon file was corrupt or that every browser failed to load it.
Why it matters for SEO
A recognisable icon can make a result or saved page easier to identify after a visit, especially for repeat users. It does not determine whether a page is crawled, indexed, or ranked. Treat it as a site identity and usability detail alongside, rather than instead of, core page metadata.
How NOTABIS detects it
For each crawled HTML page, NOTABIS counts link[rel~="icon"] and link[rel="shortcut icon"]. If the count is zero, it creates the low-severity favicon-missing finding. It does not fetch the icon, validate dimensions or MIME type, compare light and dark variants, or judge the artwork.
How to check it yourself
- View the page source and search the
<head>for an icon link. - Request the declared URL and inspect its final status and
Content-Type. - Test the icon in a private browser window and on the device classes that matter to your site.
- Check that the declaration is emitted by the shared layout rather than only one page.
- Confirm that changing the icon does not break cache-busting or the asset path.
How to fix it
Declare a suitable icon from the shared document head, for example:
<link rel="icon" href="/favicon.ico">
Serve the file from the intended origin, use an appropriate image format, and update the cache or filename when replacing it. Re-crawl representative page types and inspect the browser result.
When this is intentional or does not need fixing
A private application, prototype, or branded environment may intentionally omit a favicon. The omission is low impact; record the decision and prioritise public page access, content, and accessibility work first.
Related issues
Read title tags present, social metadata, and image SEO and accessibility. When an audit finding does not need fixing helps prioritise low-severity review items.
Run a NOTABIS audit
Run a NOTABIS SEO audit to check icon declarations across the page types the crawler can measure.