: Google Webmaster Tools - Crawl errors with 500 status code I will try to explain the situation: In December 2012 I deployed a website with a sitemap.xml, etc... there were circa 2000 URLs.

@Odierno851

Google webmasters will tell you the source of the error....
if this is simply pointing to a file in a directory, you may consider preventing anyone, including Google from browsing that folder and find such files, this can be done by creating a default php file in that folder:

Step 1- create a file called: index.php
step 2- add the following code to it:

<? php

// Silence is golden.

?>


(remove spaces)
If you then browse this folder again you no longer be able to see the contents of the folder, including the file which Google found.

Vote Up Vote Down

@Pierce454

In Google webmaster tool when it shows 500 status code error, it indicates that web pages have internal server error while trying to process the request. Let’s glance as to when the error appears:


If there is a DNS issue.
Once you have completed the process of 301 redirect and blocked the old web pages in robots.txt file.
If you have excessive page load time due to the site's hosting server getting overloaded or misconfigured.


Find out the possible ways which are responsible for showing the 500 error and solve the issue.

You can also find a complete list of various status code definition and why they showing erros from www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

Vote Up Vote Down

@Ogunnowo487

The problem with 500 (Internal Server) Errors are that they are generic errors when the server is unable to return a valid response and no other error is appropriate. It does not actually tell us anything about the error, other than there was an error! It could be anything.

In order to find the cause you need to examine your server error logs. And find out what was happening on your server at the time. Have these errors continued to occur?

However, your old URLs should be 301 redirecting to the new URLs, so there should no longer be any processing going on at the old URL to cause an error to begin with.

Vote Up Vote Down