Research Guides
A Favicon Change Needs a Verification Record
A small brand update can leave a surprisingly confusing trail: the new icon appears in one browser, the old one appears elsewhere, and someone reports that Google still shows a generic globe. Before repeatedly replacing files, collect evidence about which surface is actually wrong.
This practical review separates the published asset, the page declaration and the search result. It is a manual workflow, not a claim that Colquhoun AI performs these checks automatically.
Establish the search requirements
Google discovers favicon information from the homepage’s link declaration. It treats a hostname as a site for favicon purposes, so a subdirectory does not get an independent search favicon. The homepage must be accessible to Googlebot and the image to Googlebot-Image. Its guidance calls for a square image, a stable asset URL and recognizable branding. Meeting the requirements does not guarantee display, and changes require recrawling and processing. Google favicon guidance.
Start by recording the exact hostname you are investigating. Do not silently substitute the apex domain for www, or a product subdomain for the corporate site.
Build a compact evidence record
Use one row per hostname. Suggested columns:
| Field | What to save |
|---|---|
| Homepage tested | Requested URL and final URL after redirects |
| Declaration | Actual icon link element observed in the page |
| Asset | Resolved image URL, response and dimensions |
| Visual check | Screenshot at a small display size |
| Browser result | Browser name, test time and screenshot |
| Search observation | Result URL, query, date and screenshot |
| Decision | Fix needed, passed locally, or search follow-up pending |
This table is an audit recommendation, not a search-engine requirement. Its purpose is to make a disagreement reproducible.
Inspect all declared icons
A page can declare several icons. Browser selection can depend on attributes such as type, sizes and media; when equally suitable icons exist, document order can affect selection. That makes inspecting only the first icon declaration an incomplete browser check. MDN: icon link relationships.
In your review, list the declarations before deciding which one is obsolete. Ask the site maintainer to explain intentional alternatives. An old-looking asset may serve a particular context, so do not delete it simply because another file is newer.
Diagnose the narrowest failure
If the declaration points to the wrong file, record a declaration defect. If the URL returns an error or a non-image response, record an asset-delivery defect. If the correct image is unreadable at small size, send the designer a small-size screenshot rather than an abstract request to improve branding.
If your browser check passes but search still differs, keep those outcomes separate. Repeatedly changing filenames makes the investigation harder to compare. Preserve the successful local test and schedule a later search observation instead of declaring the release broken from one screenshot.
Close with a bounded statement
A useful completion note reads: “The homepage declares the approved icon, the asset loads, and the icon is recognizable in the tested browser. Search appearance has not yet been confirmed.”
That statement gives the next reviewer a clear starting point. It also avoids promising rankings, traffic or an immediate search refresh from a cosmetic update.