Common http Status Codes (Header Codes) | Gordon Choi

Common http Status Codes (Header Codes)

HTTP Status (Header Codes)

A HTTP status code is returned by your server in response when a request is made to your server for a web page on your website. Examples are:

HTTP status codes are of 5 different categories:

The first digit of the status code represents one of five classes of response.

HTTP Status Codes

Google provides a list of HTTP status codes to webmasters, in which the most common and important status codes are below:

200 (Successful) - The server successfully processed the request. Generally, this means that the server provided the requested page. If you see this status for your robots.txt file, it means that Googlebot retrieved it successfully.

301 (Moved permanently) - The requested page has been permanently moved to a new location. When the server returns this response (as a response to a GET or HEAD request), it automatically forwards the requestor to the new location. You should use this code to let Googlebot know that a page or site has permanently moved to a new location.

302 (Moved temporarily) - The server is currently responding to the request with a page from a different location, but the requestor should continue to use the original location for future requests. This code is similar to a 301 in that for a GET or HEAD request, it automatically forwards the requestor to a different location, but you should not use it to tell the Googlebot that a page or site has moved because Googlebot will continue to crawl and index the original location.

400 (Bad request) - The server didn’t understand the syntax of the request.

403 (Forbidden) - The server is refusing the request. If you see that Googlebot received this status code when trying to crawl valid pages of your site (you can see this on the Web crawl page under Diagnostics in Google Webmaster Tools), it’s possible that your server or host is blocking Googlebot’s access.

404 (Not found) - The server can’t find the requested page. For instance, the server often returns this code if the request is for a page that doesn’t exist on the server. If you don’t have a robots.txt file on your site and see this status on the robots.txt page of the Diagnostic tab in Google Webmaster Tools, this is the correct status. However, if you do have a robots.txt file and you see this status, then your robots.txt file may be named incorrectly or in the wrong location. It should be at the top-level of the domain and named robots.txt. If you see this status for URLs that Googlebot tried to crawl (on the HTTP errors page of the Diagnostic tab), then Googlebot likely followed an invalid link from another page (either an old link or a mistyped one).

500 (Internal server error) - The server encountered an error and can’t fulfill the request.

503 (Service unavailable) - The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.

HTTP Status Codes for SEO

For the purpose of search engine optimization, webmasters can regularly review the HTTP status codes and search engine spiders in IIS log files (i.e. Assuming if sites are running on Internet Information Services).

HTTP Status Code 301

This test shows that Google recognizes 301 redirects and passes link juice from the redirecting web page to the redirected web page, as Google SEO traffic is not lost.

To set up 301 redirects on Microsoft's Internet Information Server ( MS IIS ):

To set up 301 redirects on Apache:

HTTP Status Code 404

How Google prefers webmasters to handle 404 errors:

To improve user-friendliness, webmasters can set up the servers to return a friendly designed 404 error pages with the appropriate messages.

Developed by Gordon Choi
Copyright @ 2006-2017
Analytics Powered by Folks Analytics