Check Server Headers

[TavoxPeru 0]

The Check Server Headers tool is another helpful online tool that you can use to check and verify HTTP status codes of any page. Server headers and HTTP status codes are a matter of particular importance in ensuring that search engines see your content. But checking them can be a bit tricky.

The Check Server Headers tool is very simple and easy to use, you just need to enter a valid URL, and the tool will give you one of seven HTTP status codes. It will also -and this is important- give you an interpretation of the code.

Check server headers and verify HTTP status codes. There are seven HTTP status codes that we are primarily interested in from an indexing and search engine marketing perspective. It is recommended that you verify your URIs are returning the proper Status-Code in the Server Header.

Best regards,

[tansqrx 0]

In the HTTP 1.1 specification there are actually 40 different response codes that you might receive (http://forums.xisto.com/no_longer_exists/). Most you will never encounter. The codes are broken down further by the following:

1xx â Informational
2xx â Success
3xx â Redirection
4xx â Client Error
5xx â Server Error

The complete list follows and the section number is the HTTP specification section.

Status-Code = "100" ; Section 10.1.1: Continue
| "101" ; Section 10.1.2: Switching Protocols
| "200" ; Section 10.2.1: OK
| "201" ; Section 10.2.2: Created
| "202" ; Section 10.2.3: Accepted
| "203" ; Section 10.2.4: Non-Authoritative Information
| "204" ; Section 10.2.5: No Content
| "205" ; Section 10.2.6: Reset Content
| "206" ; Section 10.2.7: Partial Content
| "300" ; Section 10.3.1: Multiple Choices
| "301" ; Section 10.3.2: Moved Permanently
| "302" ; Section 10.3.3: Found
| "303" ; Section 10.3.4: See Other
| "304" ; Section 10.3.5: Not Modified
| "305" ; Section 10.3.6: Use Proxy
| "307" ; Section 10.3.8: Temporary Redirect
| "400" ; Section 10.4.1: Bad Request
| "401" ; Section 10.4.2: Unauthorized
| "402" ; Section 10.4.3: Payment Required
| "403" ; Section 10.4.4: Forbidden
| "404" ; Section 10.4.5: Not Found
| "405" ; Section 10.4.6: Method Not Allowed
| "406" ; Section 10.4.7: Not Acceptable
| "407" ; Section 10.4.8: Proxy Authentication Required
| "408" ; Section 10.4.9: Request Time-out
| "409" ; Section 10.4.10: Conflict
| "410" ; Section 10.4.11: Gone
| "411" ; Section 10.4.12: Length Required
| "412" ; Section 10.4.13: Precondition Failed
| "413" ; Section 10.4.14: Request Entity Too Large
| "414" ; Section 10.4.15: Request-URI Too Large
| "415" ; Section 10.4.16: Unsupported Media Type
| "416" ; Section 10.4.17: Requested range not satisfiable
| "417" ; Section 10.4.18: Expectation Failed
| "500" ; Section 10.5.1: Internal Server Error
| "501" ; Section 10.5.2: Not Implemented
| "502" ; Section 10.5.3: Bad Gateway
| "503" ; Section 10.5.4: Service Unavailable
| "504" ; Section 10.5.5: Gateway Time-out
| "505" ; Section 10.5.6: HTTP Version not supported
| extension-code
extension-code = 3DIGIT
Reason-Phrase = *<TEXT, excluding CR, LF>

[iGuest 3]

The Check Server Headers tool is another helpful online tool that you can use to check and verify HTTP status codes of any page. Server headers and HTTP status codes are a matter of particular importance in ensuring that search engines see your content. But checking them can be a bit tricky.The Check Server Headers tool is very simple and easy to use, you just need to enter a valid URL, and the tool will give you one of seven HTTP status codes. It will also -and this is important- give you an interpretation of the code.Can some one explain all about what this post means what it does etc thank you so much lolalso whats all thisStatus-Code ="100" ; Section 10.1.1: Continue| "101" ; Section 10.1.2: Switching Protocols| "200" ; Section 10.2.1: OK| "201" ; Section 10.2.2: Created| "202" ; Section 10.2.3: Accepted| "203" ; Section 10.2.4: Non-Authoritative Information| "204" ; Section 10.2.5: No Content| "205" ; Section 10.2.6: Reset Content| "206" ; Section 10.2.7: Partial Content| "300" ; Section 10.3.1: Multiple Choices| "301" ; Section 10.3.2: Moved Permanently| "302" ; Section 10.3.3: Found| "303" ; Section 10.3.4: See Other| "304" ; Section 10.3.5: Not Modified| "305" ; Section 10.3.6: Use Proxy| "307" ; Section 10.3.8: Temporary Redirect| "400" ; Section 10.4.1: Bad Request| "401" ; Section 10.4.2: Unauthorized| "402" ; Section 10.4.3: Payment Required| "403" ; Section 10.4.4: Forbidden| "404" ; Section 10.4.5: Not Found| "405" ; Section 10.4.6: Method Not Allowed| "406" ; Section 10.4.7: Not Acceptable| "407" ; Section 10.4.8: Proxy Authentication Required| "408" ; Section 10.4.9: Request Time-out| "409" ; Section 10.4.10: Conflict| "410" ; Section 10.4.11: Gone| "411" ; Section 10.4.12: Length Required| "412" ; Section 10.4.13: Precondition Failed| "413" ; Section 10.4.14: Request Entity Too Large| "414" ; Section 10.4.15: Request-URI Too Large| "415" ; Section 10.4.16: Unsupported Media Type| "416" ; Section 10.4.17: Requested range not satisfiable| "417" ; Section 10.4.18: Expectation Failed| "500" ; Section 10.5.1: Internal Server Error| "501" ; Section 10.5.2: Not Implemented| "502" ; Section 10.5.3: Bad Gateway| "503" ; Section 10.5.4: Service Unavailable| "504" ; Section 10.5.5: Gateway Time-out| "505" ; Section 10.5.6: HTTP Version not supported| extension-codeextension-code = 3DIGITReason-Phrase = *<TEXT, excluding CR, LF>Cheers

[TavoxPeru 0]

As i said in my first post, this tool will help you to verify the status of any page by checking its HTTP status code.

 

For example, when you are updating a website you usually make things like changing file names, add, delete or update page content, move inside another folder a page or group of pages located at your root folder, delete a page, etc., so, with this tool you can verify that every thing is fine and any search engine can be able to view your changes.

 

Check server headers and verify HTTP status codes. There are seven HTTP status codes that we are primarily interested in from an indexing and search engine marketing perspective. It is recommended that you verify your URIs are returning the proper Status-Code in the Server Header.

200 OK: The request has succeeded. The information returned with the response is dependent on the method used in the request.

301 Moved Permanently: The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs.

302 Found: The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests.

304 Not Modified: If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. The 304 response MUST NOT contain a message-body, and thus is always terminated by the first empty line after the header fields.

307 Temporary Redirect: The requested resource resides temporarily under a different URI. Since the redirection MAY be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.

404 Not Found: The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

410 Gone: The requested resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent.

And thanks to tansqrx to post the complete list of HTTP status codes.

 

Best regards,