Incorrect crawl errors

[LiamMcArthur]

A crawl of my websites has indicated that there are some 5XX server errors on my website:

Error Code 608: Page not Decodable as Specified Content Encoding
Error Code 803: Incomplete HTTP Response Received
Error Code 803: Incomplete HTTP Response Received
Error Code 608: Page not Decodable as Specified Content Encoding
Error Code 902: Network Errors Prevented Crawler from Contacting Server

The five pages in question are all in fact perfectly working pages and are returning HTTP 200 codes. Is this a problem with the Moz crawler?

[LiamMcArthur]

Thanks for this! I didn't think to check the server logs. I'll have them checked and make sure that it's not blocking Moz out from the crawl. We have thousands of URL's on our website and quite a strict security policy on the server - so I imagine Moz has probably been blocked out.

Thanks,

Liam

[DirkC]

Hi,

These error code's are Moz custom codes to list errors it encounters when crawling your site - it's quite possible that when you check these pages in a browser that they load fine (and that google bot is able to crawl them as well).

You can find the full list of crawl errors here: https://mza.bundledseo.com/help/guides/search-overview/crawl-diagnostics/errors-in-crawl-reports.  You could try to check these url's with a tool like web-sniffer.net to check the responses and check the configuration of your server.

• 608 errors: Home page not decodable as specified Content-Encoding
  The server response headers indicated the response used gzip or deflate encoding but our crawler could not understand the encoding used. To resolve 608 errors, fix your site server so that it properly encodes the responses it sends.

• 803 errors: Incomplete HTTP response received
  Your site closed its TCP connection to our crawler before our crawler could read a complete HTTP response. This typically occurs when misconfigured back-end software responds with a status line and headers but immediately closes the connection without sending any response data.

• 902 errors: Unable to contact server
  The crawler resolved an IP address from the host name but failed to connect at port 80 for that address. This error may occur when a site blocks Moz's IP address ranges. Please make sure you're not blocking AWS.

Without the actual url's it's impossible to guess what is happening in your specific case.

Hope this helps,

Dirk