Favicon Not Showing in Yandex? Fix Browser and Search Icons

If your icon appears in Chrome but not in Yandex, or a result has no icon in Yandex Search, you may be looking at two separate systems. A favicon not showing in Yandex can mean Yandex Browser cannot load the image, or Yandex Search has not refreshed an indexed page's icon.

Quick fix: favicon not showing in Yandex

First decide where the icon is missing: the tab, address bar, bookmarks, or search results. Browser and search surfaces have different refresh paths, so a working tab does not prove that the search listing is current.

1. Find the declaration. View the page source and search for a link whose rel contains icon. If none exists, add one in the document head.
2. Test the exact file URL. Open the href value in a new tab. It must return the image itself, not a 404 page, login screen, or HTML error document.
3. Use a root-relative fallback. Put a valid ICO file at /favicon.ico and reference that path explicitly. This removes route ambiguity on nested pages.
4. Bypass an old cached copy. Close the tab, reload with caching disabled, and open the page again. A temporary value such as /favicon.ico?v=2 can confirm whether caching caused the mismatch.
5. Refresh search separately. If the direct file works but Yandex Search still has no icon, confirm the page is indexed under the expected URL. If you use Yandex Webmaster, submit the corrected URL for reindexing instead of changing the icon repeatedly.

A small, predictable declaration is enough for the first pass:

<link rel='icon' href='/favicon.ico'>

You can add an SVG candidate if it is part of your supported setup:

<link rel='icon' type='image/svg+xml' href='/favicon.svg'>

The HTML standard defines the icon link relation for an external resource and its optional sizes attribute. Keep any declared dimensions aligned with the file you serve.

Root causes behind a Yandex-only failure

1. The path looks right but resolves elsewhere

Relative icon URLs resolve against the page's base URL. On https://example.com/products/item/, href='favicon.ico' can point under the current path rather than at the site root. A base element or framework-generated URL can change that result.

Open the Network panel, filter for the icon request, and inspect its final URL. /products/item/favicon.ico and /favicon.ico are different resources, even if both names look familiar in the project tree.

2. The server does not return an image

A file in a build folder may still fail on the live site. Check for a stale deployment, case-sensitive filename mismatch, blocked CDN path, redirect loop, or authentication rule.

Inspect the response status, final URL, and content type. An ICO needs an icon media type, while SVG and PNG need their matching image types. If the response body is HTML, the browser received an error page rather than an icon.

3. Search results and browser tabs use different state

A tab loads the icon from the page you are visiting. A Yandex Search listing may reflect information obtained during an earlier crawl, so the live tab can look correct while the result shows no icon or an old one.

Check the result's destination URL first. If it points to an old URL, staging page, redirect, or different indexed version, changing only the current page may not repair that listing. Keep the icon public and stable, then request a refresh through the available webmaster tools.

4. Caches or duplicate links mask the right file

Yandex Browser can retain an icon it already fetched, while a server or CDN can retain an older deployment. A versioned filename such as /favicon-v2.ico can expose a stale request path, provided you update the HTML link simultaneously.

Inspect every injected icon link too. A CMS theme, plugin, or template may add another rel='icon' declaration, leaving two candidates with different paths. Remove accidental duplicates instead of relying on selection order.

Prevention: make the icon predictable

• Keep one fallback at a stable URL. Store the ICO at /favicon.ico on the same origin as the page. Do not put the only icon behind a login, cookie wall, or JavaScript-only URL.
• Use a site-root reference. Start the href with / so the file does not depend on the current route.
• Check the public response. A crawler and a signed-out visitor must be able to fetch the icon without cookies or JavaScript.
• Version deliberate replacements. If you replace the artwork under the same filename, change the path as well as the file so browser and CDN caches cannot silently return the previous image.
• Audit both surfaces. Test the live icon in Yandex Browser and inspect the corresponding Yandex Search result after a recrawl.

Final check

If the direct request fails, fix delivery before worrying about Yandex. If it succeeds but the search result is wrong, work on the indexed URL and recrawl path. That split usually turns a vague favicon problem into two checks you can finish.

For a broader browser-side checklist, see Favicon Not Showing? 7 Causes and Quick Fixes. If you are comparing search engines, Google's rules are separate; review the Google favicon checklist instead of assuming Yandex uses the same gates.

You can use Mzu favicondl to prepare a clean ICO or PNG fallback before publishing it at the root path. The decisive details are the final URL, response, and refresh path that Yandex can use.