Check the delivery path as carefully as the artwork
A missing favicon can be a file, markup, crawl, hostname, or processing issue. Start by checking what the home page actually declares and what Google can retrieve. The icon visible in your browser tab is only one observation.
Google's 28 August documentation update clarified supported file formats; it did not announce a change in support. That distinction matters when diagnosing a missing brand asset. Do not assume a new algorithm removed the icon before checking the existing implementation.
Prepare an icon that survives a small canvas
The favicon guide lists BMP, GIF, ICO, PNG, JPEG, PPM, and TIFF. It requires a square icon of at least 8 by 8 pixels and recommends a size larger than 48 by 48. An SVG used elsewhere in the brand system should not be assumed to be a supported Search favicon.
My design recommendation is to test the mark at the small sizes where a person will recognise it. Remove unnecessary detail through an approved small-scale brand variant rather than letting an image model redraw the logo. A technically valid asset can still look like an unreadable speck.
Use a symptom-to-check table
| Symptom | Check first | Evidence to retain |
|---|---|---|
| Icon works only in one browser | Cached asset and actual declared URL | Fresh request and rendered head |
| File loads but Search omits it | Format, crawl access, and recrawl timing | Response, rules, and change date |
| Wrong icon on a subdomain | That hostname's home-page declaration | Hostname-specific check |
| Artwork is hard to recognise | Approved small-size mark and contrast | Actual-size previews |
Google treats the hostname as the site for favicon purposes. A subdirectory does not get an independent favicon in Search. The home page and icon must be crawlable by the relevant Google crawlers, and the icon URL should remain stable. Inspect these conditions individually instead of changing several files at once.
Keep the implementation easy to inspect
A typical declaration is <link rel="icon" href="/favicon.png"> in the home page's head. Use the actual approved path for your site. Request it directly and verify that it returns the intended image, not an HTML error page, login screen, or challenge response with a successful status code.
Record the deployed filename, pixel dimensions, format, declaration, and response result. If the site redirects between hostnames, inspect the final home page too. A local source file is not evidence that the same file reached production.
Close the handoff with a follow-up date
Google says processing can take days to weeks and does not guarantee appearance. Record when the home page and asset changed, then recheck rather than repeatedly renaming the file. Keep “implementation verified” separate from “observed in Search.”
The complete handoff includes approved artwork, a small-size preview, technical checks, and a follow-up owner. For a brand-led website, that is part of the design delivery, alongside readable copy and a working enquiry path. The purpose is recognisable presentation, not a promised ranking increase.
Link Map
Sources and editorial review
Sources reviewed on 14 September 2026. The practical workflows and illustrative examples are JQ AI SYSTEMS analysis unless explicitly attributed.
- Google Search Central: Define a favicon to show in search results (Updated 28 August 2026).
- Google Search Central: Documentation updates (Relevant entries: 24 July, 28 August and 8 September 2026).