Start here
Before You Fix It: What This Check Means
Favicons are small signals, but missing icons often indicate metadata/template hygiene gaps. In plain terms, this checks whether browsers can find a site icon for tabs and bookmarks. Scavo looks for icon links in page HTML, then falls back to probing `/favicon.ico`.
Why this matters in practice: operational drift here often causes hard-to-debug regressions across environments.
How to use this result: treat this as directional evidence, not final truth. This result reflects what was observable at scan time and should be verified in your own production context. First, confirm the issue in live output: verify directly in live production output with browser/network tools Then ship one controlled change: Add explicit icon link declarations in shared layout head. Finally, re-scan the same URL to confirm the result improves.
Background sources
TL;DR: Your site lacks a favicon, so browser tabs and bookmarks show a generic icon that makes your site harder to identify.
A favicon appears in browser tabs, bookmarks, browser history, and Google's search results. Without one, your site looks unfinished and is harder for users to find among open tabs. It's also a trust signal — professional sites have favicons, and their absence can make visitors question legitimacy.
What Scavo checks (plain English)
Scavo looks for icon links in page HTML, then falls back to probing /favicon.ico.
Current logic:
Pass: one or more<link rel="...icon..." href="...">declarations foundPass: no declaration found, but/favicon.icoreturns200Warning: neither declarations nor fallback icon are available
How Scavo scores this check
Scavo assigns one result state for this check on the tested page:
- Pass: baseline signals for this check were found.
- Warning: partial coverage or risk signals were found and should be reviewed.
- Fail: required signals were missing or risky behavior was confirmed.
- Info: Scavo could not gather enough reliable evidence on this run to score pass/fail confidently.
In your scan report, this appears under What failed / What needs attention / What is working for favicon, followed by Recommended next steps and Technical evidence (for developers) when needed.
- Scan key:
favicon - Category:
TECHNICAL
Why fixing this matters
Missing icons are a small but visible quality signal. Tabs, bookmarks, and browser UI become less recognizable, which can hurt perceived polish and trust.
It also often reveals asset-pipeline drift after frontend/CDN refactors.
If you are not technical
- Open your site in a browser tab and confirm brand icon appears.
- Ask your developer to verify icon links in page source.
- Confirm fallback icon path is publicly reachable.
- Re-run Scavo after fixes.
Technical handoff message
Copy and share this with your developer.
Scavo flagged Favicon (favicon). Please add valid icon link tags in shared head templates (or restore /favicon.ico fallback) and verify public accessibility in production.If you are technical
- Add explicit icon link declarations in shared layout head.
- Keep
/favicon.icoas compatibility fallback. - Verify CDN/static routing does not block icon paths.
- Bust cache correctly when icon assets are replaced.
How to verify
- View source for icon
<link>tags. curl -I https://your-domain/favicon.icoreturns200(if fallback used).- Browser tab and bookmark show expected icon.
- Re-run Scavo and confirm pass.
What this scan cannot confirm
- It does not assess icon design quality.
- It does not validate full PWA icon manifest set.
- Browser caching may delay visual confirmation after changes.
Owner checklist
- [ ] Assign owner for icon asset delivery.
- [ ] Keep icon links in shared templates.
- [ ] Validate icon paths after CDN or build-pipeline changes.
- [ ] Include favicon in pre-release smoke checks.
FAQ
Can we pass without explicit icon tags?
Yes, if /favicon.ico is reachable. Explicit tags are still recommended.
Why does this sometimes regress after redesigns?
Head template refactors and asset path changes commonly remove icon declarations.
Do we need multiple icon sizes?
For best cross-platform support, yes; this check only validates baseline discoverability.
Is favicon relevant for SEO?
Indirectly, as a quality/brand signal, but this is mostly UX and trust hygiene.
Sources
Need an icon asset matrix for browser, PWA, and social surfaces? Send support your current files.
