Google Search is dropping site favicons from result snippets and showing a generic globe icon instead, according to a wave of reports collected by Search Engine Roundtable’s Barry Schwartz. He counted roughly seven complaints sent to him directly, plus many more surfacing across Google’s Webmaster Help forum, X, and Bluesky over the past several days.
The pattern predates Google’s August 2026 spam update by a couple of days, which Schwartz says makes a connection unlikely. That timing matters for anyone tempted to treat this as a spam-update side effect: it points instead to a change on Google’s rendering or caching side rather than a ranking action tied to site quality.
One affected site owner described a case that rules out the usual culprits. Both favicon.ico and favicon.png returned 200 responses, met the 128x128 square-image requirement, were referenced directly in the homepage HTML, and were not blocked by robots.txt. Repeated reindexing requests through Search Console did not restore the icon. That checklist covers nearly every documented favicon requirement Google publishes, which is what turned an isolated glitch into a forum thread worth watching.
Google’s Rajan Patel replied publicly that the team is investigating. Schwartz also reported that one of the broken examples he had flagged began working again shortly after he published his post, a signal, though not confirmation, that a fix might already be moving through Google’s systems.
For a search team, the practical read is narrow but not trivial. A missing favicon strips a visual anchor that helps a result stand out in a crowded SERP, particularly on mobile where brand icons do heavier work distinguishing a listing from surrounding ads and competitors. Click-through rate is the metric to watch here, not rankings: nothing in the reports suggests position is affected, only how the result is presented.
The right response while Google investigates is restraint, not remediation. Site owners chasing this bug should resist re-uploading, resizing, or re-hosting a favicon that already passes every documented check, since that only adds noise to a problem Google itself has now acknowledged. Confirm your favicon file still serves correctly and is still linked in the page head, then wait rather than iterate.
There is a reporting-noise angle worth flagging too. Bugs that surface within days of a named algorithm update tend to get folded into that update’s narrative by site owners searching for an explanation, even when a publication tracking the pattern closely, as Schwartz was here, sees no real correlation. That conflation matters for anyone auditing a traffic or appearance change this month: check timestamps against Google’s own update rollout window before attributing a symptom to the wrong cause.
Search Engine Roundtable’s coverage does not include a resolution timeline or an official statement from Google beyond Patel’s short reply, so teams should treat this as monitored rather than fixed. Sites currently missing their favicon should recheck the SERP snippet over the next few days rather than assume the issue is site-side, and should hold off on Search Console reindex requests beyond a single confirmation check once Google reports the bug closed.
Barry Schwartz reported the favicon complaints for Search Engine Roundtable on August 20, 2026.
