Google corrige bug que apagou favicons dos resultados de busca

For nearly a week in August 2026, many sites saw their favicons disappear from Google search results, replaced by the generic little globe icon. The problem began early that week, gained volume in complaints, and was only confirmed as a bug by Google itself on Friday the 21st. According to reporting by Barry Schwartz for Search Engine Land, the issue was declared fully resolved on Sunday the 23rd.

The confirmation came from Rajan Patel, VP of search engineering at Google: "This is an issue on our end. We've identified the issue and are working to fix it as quickly as possible. Sorry for the inconvenience this has caused." In other words: it wasn't a configuration error on the sites' part, and nothing needed to be changed in anyone's HTML for the icon to come back.

What actually happened

The favicon is the icon that appears next to the site name in the mobile search snippet and, increasingly, on desktop as well. When Google can't pull the correct file, it displays a default gray globe. That's exactly what happened en masse: sites that had always had their favicon correctly configured started showing the generic icon, including cases like LinkedIn, which according to Search Engine Land was still appearing broken when part of the rest had already normalized.

The fix was gradual. Search Engine Land reported that the bulk of the problem was already resolved by Saturday the 22nd, and Patel indicated full closure on Sunday the 23rd. Since indexing and favicon caching aren't instantaneous, it's normal for the return to normal to appear in waves as Google reprocesses the results.

Why a broken icon affects CTR

It may seem like a cosmetic detail, but the favicon is one of the few visual elements a site controls within the snippet. In a search result page crowded with nearly identical blue links, a recognizable brand icon helps the user's eye fix on that result, which translates into clicks. The reasoning Search Engine Land itself sums up is straightforward: a unique favicon helps the snippet stand out, and falling back to the generic globe "can lead to fewer clicks on the listing."

The effect is more noticeable for well-known brands, where the icon's visual recognition reinforces trust, and in competitive niches, where several competitors fight for the same screen. For those who depend on branded organic traffic, a week with the gray little globe may have meant a small erosion in CTR precisely on the most valuable searches, the navigational ones.

What changes for publishers in Brazil

On the technical side, the main lesson is about diagnosis. When a favicon disappears from search, a dev's reflex is to open the code and look for what broke. In this episode, touching the site would have been a waste of time, because the failure was in Google's infrastructure. Before going and changing , it's worth checking whether the problem is isolated (just your site) or widespread, by following channels like Search Engine Roundtable and Google's own Search Central.

The case serves as a reminder that the cause of a search anomaly isn't always on your server. Before rushing to investigate the code, the right step is to confirm whether other sites are experiencing the same symptom. If the answer is yes, the recommended action is to wait for Google's fix, not rewrite the favicon markup.

What remains open

The episode exposes a dependency that usually goes unnoticed: branding elements in the snippet don't live on your server, they live in Google's pipeline, and can break without any action on your part. There's no SLA for favicons in search, nor a Search Console panel that shows the icon's status in real time. When something like this happens, the publisher is at the mercy of Google's fix speed, which in this case took nearly a week between the start of complaints and the closure.

It's also worth noting the timing of the communication: complaints started at the beginning of the week, but the official confirmation only came on Friday. For those monitoring CTR closely, that interval is enough time to generate false diagnoses and unnecessary adjustments. The practical recommendation is to build the habit of correlating sudden CTR drops with announcements of known bugs before attributing the problem to your own site. Measuring before and after is still worthwhile, but identifying the right cause is what avoids rework.