Google Fixes Favicon Bug and Data Glitch in Crawl Stats Report

Google closed out the weekend of August 22 and 23 by fixing two bugs that had been bothering anyone following technical SEO closely. According to Search Engine Roundtable, the first affected the display of favicons in search snippets; the second, Google Search Console's crawl stats report. Neither one hurts rankings, but both get in the way of exactly the part of the job that depends on observation: what shows up for the user and what the tool reports back to you.

The Favicon Bug

About a week before the fix, Google stopped displaying the favicon set by many sites in search results. In place of the brand's icon, the generic globe appeared, the same placeholder the search engine uses when it can't find any favicon at all. In other words: sites that had the icon correctly configured started to look like they didn't.

The important detail is that this wasn't a problem on the site, it was on Google's end. Rajan Patel, from Google, confirmed on Saturday, August 22 that the fix was on the way: "Not fixed yet, but should be in the next 12 hours or so." Given that window, the favicon should already be back to normal for most sites.

Why does this matter? The favicon in search results is one of the few visual brand elements that show up on mobile SERPs, right next to the site's name. A generic globe in place of the icon reduces recognition and, potentially, click-through rate, even without any change in ranking position. It's the kind of thing that, if you had changed something on your site that same week, would trigger hours of investigation chasing a cause that didn't exist.

The Lesson: Not Every Anomaly Is Your Fault

This episode reinforces a practical diagnostic principle in technical SEO: before redoing your implementation, it's worth confirming whether the behavior is isolated to your site or widespread. In the favicon case, simply observing that many different sites had the generic globe at the same time was enough to conclude the cause was on the search engine's end.

A few quick checks that avoid rework in these situations:

• Test the same search on another known domain and see if the symptom repeats.
• Check whether the favicon is still accessible and valid (/favicon.ico or the pointing to a file that returns a 200).
• Follow community sources (Search Engine Roundtable, discussions on X, Google's own status page) before assuming a local regression.

If the file responds, the markup is correct, and the problem shows up across multiple sites, the conclusion is almost always: it's a Google bug, wait for the fix.

The Crawl Stats Gap

The second bug is more subtle and more dangerous for anyone making decisions based on data. Around August 14 or 15, Search Console's crawl stats report started showing a two-day gap, days that were simply missing from the historical series. The fix only arrived on Sunday, August 23, around 5pm New York time.

The crawl stats report lives in Search Console's settings and shows the total volume of Googlebot requests, average server response time, and the breakdown by HTTP response type, crawl purpose, and Googlebot type. It's the primary source for understanding how the search engine is consuming your site: whether the server is slow, whether there's a spike in 5xx errors, whether crawl budget is being wasted on useless URLs.

A two-day gap in that chart is treacherous because it looks like a real problem. An abrupt drop in crawl volume is exactly the symptom that would trigger a legitimate alert: it can point to a server being down, an accidental block in robots.txt, or a configuration error. In this case, though, the hole was just missing reporting data, not an actual drop in Googlebot activity.

What to Check Now That It's Fixed

With the report restored, it's worth reopening crawl stats and confirming two points:

1. Whether the two missing days have been filled back in or remain a hole in the series. Reporting fixes don't always retroactively recover lost data; sometimes the period stays blank forever.
2. Whether any alert was raised or decision made during that period, review it. Anyone who saw the drop between August 14 and 23 and concluded that Googlebot had reduced its crawling may have reached the wrong diagnosis based on incomplete data.

For anyone who wants to look beyond the aggregated chart, cross-referencing with server logs is the gold standard. The log records every Googlebot hit independently of Search Console, so a gap that shows up in the report but not in the logs confirms right away that it was a reporting bug, not a real drop in crawling.

The Pattern Behind Both Cases

The two bugs have different origins (one in SERP rendering, the other in Search Console's data pipeline), but they teach the same lesson: Google's observation infrastructure is part of your monitoring stack, and it fails too. Disappearing favicons and missing days in a report are examples of noise that, without context, turn into false positives.

The defense isn't to distrust everything, it's to have more than one source. Server logs against crawl stats. Search on your own domain against search on reference domains. Community and official status against the impression that something broke on your end. As Barry Schwartz himself sums up in closing the episode, it was "quite a busy weekend for Google," and it's up to whoever's monitoring to tell apart what's a real problem from what's just the search engine recovering from an internal hiccup.