Check your favicon setup

SiteCurl checks for a favicon by looking for a <link rel='icon'> tag in your page's head section and verifying the referenced file returns a 200 status. It also checks the default /favicon.ico path, which browsers fall back to when no link tag is present.

If neither a link tag nor a working /favicon.ico file is found, SiteCurl flags the issue. Pages with a link tag pointing to a broken or missing file are also flagged, because a broken link tag is worse than no link tag: the browser attempts the request, gets a 404, and falls back to the generic icon anyway.

The check runs on every page in your scan to catch pages that override the site-wide favicon with a broken page-specific one. This is more common than it sounds on sites with multiple templates or content management systems that allow per-page icon overrides.

The favicon is the small icon that appears in browser tabs, bookmarks, history lists, and (on some browsers) the address bar. It is one of the smallest visual elements on your site, but one of the most frequently seen. Every time someone has your site open in a tab, they see the favicon.

A missing favicon shows a generic icon: a blank page, a globe, or nothing at all. In a browser with 15 tabs open, the favicon is the only way to identify your site. Without it, visitors cannot find your tab among the others.

When a favicon is missing, browsers repeatedly request /favicon.ico on every page load. Each request returns a 404, which fills your server logs with errors and wastes a small amount of bandwidth. On high-traffic sites, these failed requests add up.

Favicons also appear in search engine results on mobile. Google sometimes shows the favicon next to your site name in mobile search results. A missing favicon means your listing has a generic icon while your competitors show their brand. This small visual difference affects perceived trust, especially for sites in competitive markets.

The favicon is a branding touchpoint that appears in every browser tab, bookmark, and history entry. Missing it makes your site harder to find among open tabs and reduces brand recognition in bookmarks lists.

Google displays favicons in mobile search results. A clean, recognizable favicon helps your listing stand out. A generic globe icon blends in with every other site that forgot to add one. For branded queries where trust matters, this visual signal can influence which result the searcher clicks.

Repeated 404 requests for /favicon.ico clutter your server error logs and waste bandwidth. On high-traffic sites, this adds extra load to your server. Monitoring tools that track 404 rates may also generate false alarms when the majority of 404s are favicon requests.

Small business sites often skip the favicon during initial setup. It is a minor detail that gets postponed and then forgotten. Every visitor sees the missing icon in their browser tab, and bookmarked users see a generic icon in their favorites list. For local businesses competing on trust, this is an easy win to claim.

Sites that recently migrated to a new host or CMS may lose their favicon if the file was not carried over. The old favicon stops working and the default 404 takes its place. This is common after WordPress-to-custom-site migrations and platform switches where static assets are handled differently.

Multi-page web apps where users keep tabs open for extended periods suffer the most. If your app is one of 20 open tabs, the favicon is the only way to find it quickly. SaaS products, dashboards, and email clients all rely on the favicon for tab identification.

Step 1: Create a favicon file. Design a simple icon that is recognizable at 16x16 pixels. Use your logo mark or a distinctive letter from your brand name. Save it as a .ico, .png, or .svg file. Test the icon at actual display size before uploading to make sure it reads clearly at small dimensions.

Step 2: Add the link tag. In your HTML head, add <link rel='icon' href='/favicon.ico' type='image/x-icon'>. For PNG favicons, use type='image/png'. For SVG, use type='image/svg+xml'. SVG favicons scale cleanly to any size and support dark-mode media queries, but they are not supported in Safari as of early 2026.

Step 3: Place a favicon.ico at the root. Even with a link tag, place a favicon.ico file at your site's root path. Some browsers and tools check /favicon.ico directly without reading the link tag. This prevents 404 errors in your server logs and satisfies older browsers that do not process link tags.

Step 4: Add touch icons for mobile. Apple devices use <link rel='apple-touch-icon' href='/apple-touch-icon.png'> for home screen bookmarks. Create a 180x180 PNG version of your icon for this purpose. Android devices use the Web App Manifest, so include a 192x192 icon there as well.

Using an image that is too detailed. Favicons display at 16x16 or 32x32 pixels. A detailed logo becomes an unrecognizable blur at that size. Use a simplified version: a single letter, a simple shape, or your logo mark. If your full logo does not work at 16px, design a separate favicon-specific version.

Forgetting the favicon after a site migration. When moving to a new host or CMS, the favicon file may not transfer automatically. Check that /favicon.ico and any referenced icon files exist on the new server. Add favicon verification to your post-migration checklist.

Only adding the link tag without the file. A link tag that points to a nonexistent file is worse than no link tag at all. The browser tries to load the file, gets a 404, and falls back to the generic icon. Upload the file first, verify it loads, then add the link tag.

Caching issues after an update. Browsers cache favicons aggressively, sometimes for weeks. If you replace your favicon and the old one still shows, add a version query string to the href: /favicon.ico?v=2. This forces browsers to fetch the new file.

After adding your favicon, open your site in a new browser tab. The icon should appear in the tab. Clear your browser cache if you see the old generic icon, as favicons are heavily cached.

Check the file directly by visiting https://yoursite.com/favicon.ico. It should display your icon, not a 404 error. Run another SiteCurl scan to confirm the check passes. If the scan still flags a missing favicon, inspect the page source to make sure the link tag is in the <head> section and not accidentally placed inside the <body>.

A favicon is a small file with outsized visibility. It appears in every browser tab, bookmark, and mobile search result. Create a simple, recognizable icon and make sure the file loads correctly. It takes minutes to set up and never needs to be changed again.