Server connectivity errors
1] Due to Googlebot couldn’t access your site because the request timed out or because your site is blocking Google
2] It is important to choose the fast server - If the server takes long time to load the page, or server returns busy this may return overload status and makes the Google bot to crawl the site more slowly
3] The server should be capable to handle traffic
4] Here are the different issues in the server due to misconfiguration of your server or server overload issue faced by Google bot while fetching the content. If your website facing such a error we can use "Fetch as Google" from Webmaster tool and find the response form Google Bot while fetching your server
-
Server error: Connect timeout
- Google was unable to connect to your server. -
Server error: Connect failed
- Google wasn’t able to connect to your server because the network is unreachable or down. -
Server error: Connection refused -
Server refused the connection. Your hosting provider may be blocking Googlebot, or there may be a problem with the configuration of their firewall. -
Server error: No response
- Google was able to connect to your server, but the connection was closed before the server sent any data. -
Server error: Truncated response
- Your server closed the connection before we could receive a full response, and the body of the response appears to be truncated. -
Server error: Connection reset -
Your server successfully processed Google’s request, but isn't returning any content because the connection with the server was reset. Please check back later. -
Server error: Truncated headers -
Google was able to connect to your server, but it closed the connection before full headers were sent. Please check back later. -
Server error: Timeout -
The server timed out waiting for the request
Many very high secure server restricts some un-usual request, as Google bot makes more request than human user so some servers may block the request from Google
No comments:
Post a Comment