Google Webmaster Tools Bug: No Crawl Error Details

Apr 12, 2012 • 8:21 am | comments (5) by twitter Google+ | Filed Under Google Search Engine Optimization
 

Google Webmaster ReportA Google Webmaster Help thread has one webmaster complaining that the crawl errors report in Google Webmaster Tools is not showing him the details of those errors.

Specifically, Google is telling him he has 54 errors related to page not found (404 status codes). He wants to review those specific pages to see if it an issue with the site or server or if it is done right. Having 404s are not bad if it is done on purpose.

But when the webmaster looks for the details it is missing. Here is a screen shot:

Google Crawl Errors Bug

Google's John Mueller confirmed the bug in the thread and said:

Just a short update -- it looks like this is a bug, the team has been working on a fix for this, but it might be a few weeks before it's live. Thanks for your patience & sorry for the inconvenience.

I personally do not see this issue but I am sure it is happening to others.

Forum discussion at Google Webmaster Help.

Previous story: Google+ Redesign
 

Comments:

Andrea Pernici

04/12/2012 01:02 pm

Sometimes happen after fixing some errors via the new feature.

Robert Meinke

04/12/2012 03:58 pm

Thank goodness it's a bug. This happened to me yesterday - I wanted to check a client's 404 errors and GMT wouldn't list any URLs. I thought Google was playing its "let's restrict data for no good reason" game again. I just checked again and it's been fixed.

Allen James

04/13/2012 11:22 am

Hi, Since last two months some products like google webmaster central showing unrecognized language insted of english in their crawler errors sections have anybody noticed that thing???  

Franziska Bischoff

04/17/2012 08:06 pm

Thank you very much for this post and good to know, that i´m not the only one with this problem.

g1smd

05/26/2012 09:56 am

To this day, there is still no Crawl Errors data for 2012 April 11th. The data jumps from April 10th to April 12th.

blog comments powered by Disqus