Reviewed November 11, 2026

Favicon 404s: The One Missing Icon Flooding Your Error Logs

Every page load on your store generates a request for /favicon.ico, whether you declared a favicon or not, because browsers fetch it automatically from the root before they process your HTML. If the file does not exist, the server returns a 404, and that 404 lands in your error logs, your browser console, and your Search Console coverage report. One missing icon, requested on every page, on every visit, can become the single largest source of 404s in your logs, and it buries the real broken links underneath it. The fix takes five minutes: upload a square image in Theme Settings, under Favicon, confirm it loads at yourstore.com/favicon.ico, and request reindexing in Search Console. The checkout page is the one exception: Shopify hosts checkout separately, and only Plus stores can set a checkout favicon.

The request you never made

A favicon.ico 404 error occurs when a browser requests a favicon file, the small icon displayed in browser tabs and bookmarks, that either does not exist or cannot be located at the expected path. Most web browsers automatically attempt to fetch /favicon.ico from your website's root directory, regardless of whether you have explicitly declared one in your HTML. When the file is missing or misconfigured, you see warnings like "Warning: not found favicon.ico" in your server logs and browser console. The error is a 404 because the server returns Not Found when the resource does not exist. While it does not break functionality or directly impact SEO rankings, it clutters server error logs, creates unnecessary 404 entries, and adds a small amount of wasted server processing for every single page request. And because the request happens on every page, on every visit, one missing icon can become the single largest source of 404s in your logs.

Why it buries the real problems

The cost of a favicon 404 is not the icon. It is the noise. A store with a missing favicon generates a 404 on every page load, and those 404s fill the error log, the Search Console coverage report, and the browser console, until the real broken links, the product page that was deleted without a redirect, the collection URL that changed, the image that was renamed, are buried underneath hundreds of identical favicon entries. A merchant who opens the log to find broken links sees favicon, favicon, favicon, and concludes the log is useless, which is exactly the wrong conclusion. The log is useful; it is just full of one fixable entry. Fix the favicon first, and the real 404s become visible. That is the whole point of the fix: not the icon, but the signal-to-noise ratio of the error log.

The five-minute fix, and the theme trap

The fix on Shopify is to go to Online Store, then Themes, then Customize, then Theme Settings, then Favicon, and upload a square image, 32 by 32 or 48 by 48 pixels, in .png, .ico, or .svg. Then verify it loads at yourstore.com/favicon.ico, and request reindexing of the homepage in Google Search Console so Google picks up the new icon. One merchant's fix required changing the favicon manually from .svg or .png to a .ico file in theme.liquid, with the .ico at 48 by 48, 96 by 96, or 144 by 144 pixels, and Google updated the favicon within an hour of the reindex request. The trap is the theme that declares the favicon three times: one store's theme had three favicon links in the code, the second one broken, and the console showed a 404 for /favicon.ico even though the .png version loaded fine. Remove the broken links and keep one. And check the case: Linux file systems distinguish case, so Favicon.ICO and favicon.ico are different files, and a path that is misspelled or mis-cased returns a 404 even when the file exists.

The one 404 you cannot fix

The checkout page is the exception. Shopify hosts checkout pages on a separate secure server, and the store favicon cannot be used there. All Shopify stores on standard plans see a favicon 404 on checkout, and only Plus accounts can customize the checkout favicon. It is a platform limitation, not a theme bug, and it does not affect the storefront. Do not chase it by editing the theme; the checkout page does not read the theme's favicon. The same applies to the favicon that Google shows in search results: Google needs the favicon on the same domain as the site, and it can take a few days to a few weeks for search results to reflect a change after reindexing. Fix the storefront favicon, accept the checkout one, and move on to the broken links the clean log now reveals.

Frequently asked questions

Why is my error log full of favicon.ico 404s?

Because every browser automatically requests /favicon.ico from your domain root on every page load, whether you declared a favicon in your HTML or not. If the file does not exist, the server returns a 404 for every visit, and that 404 lands in your logs. One missing icon, requested on every page, becomes the largest source of 404s in the log, and it buries the real broken links underneath it.

How do I fix a favicon 404 on Shopify?

Go to Online Store, then Themes, then Customize, then Theme Settings, then Favicon, and upload a square image, 32 by 32 or 48 by 48 pixels, in .png, .ico, or .svg. Then verify it loads at yourstore.com/favicon.ico, and request reindexing of the homepage in Google Search Console. If the theme has multiple favicon links in theme.liquid, remove the broken ones, because a second link to a missing file generates a second 404.

Why does my favicon 404 on the checkout page?

Because Shopify hosts checkout pages on a separate secure server, and the store favicon cannot be used there. All Shopify stores on standard plans see a favicon 404 on checkout, and only Plus accounts can customize the checkout favicon. It is a platform limitation, not a theme bug, and it does not affect the storefront. Do not chase it by editing the theme; the checkout page does not read the theme's favicon.

Does a favicon 404 hurt SEO?

Not directly, but it costs you in two ways. It wastes server resources and clutters error logs, which makes real 404s harder to find, and it affects the professional appearance of the site in search results, because Google shows the favicon next to the listing. A missing favicon is also a signal that the store's basic setup is incomplete, and the fix is five minutes of work.