Status Codes

Status codes allow you to set the HTTP status code of a page.

If you need to create multiple status codes at once use the bulk modification.

For a more in-depth view on robots.txt please read this article from MOZ.

Creating a Status Code modification

Status Codes

To create a HTTP status code modification simply follow the below steps;

  1. Enter the local URL that you wish to set the status code for.
  2. Select which status code you would like to implement.

HTTP status code list

2XX - Success

These codes indicate success. The body section if present is the object returned by the request. It is a MIME format object. It is in MIME format, and may only be in text/plain, text/html or one fo the formats specified as acceptable in the request.

3XX - Redirection

The codes in this section indicate action to be taken (normally automatically) by the client in order to fulfill the request.

4XX - Client side errors

The 4xx codes are intended for cases in which the client seems to have erred, and the 5xx codes for the cases in which the server is aware that the server has erred. It is impossible to distinguish these cases in general, so the difference is only informational.

The body section may contain a document describing the error in human readable form. The document is in MIME format, and may only be in text/plain, text/html or one for the formats specified as acceptable in the request.

5XX - Server side error

This means that even though the request appeared to be valid something went wrong at the server level and it wasn’t able to return anything.

Redirect Type Description Type
100 - Continue Client should continue with request. Informational
101 - Switching Protocols Server is switching protocols. Informational
102 - Processing Server has received and is processing the request. Informational
103 - Processing Server has received and is processing the request. Informational
122 - Request-uri too long URI is longer than a maximum of 2083 characters. Informational
200 - Ok The request was fulfilled. Success
201 - Created Following a POST command, this indicates success, but the textual part of the response line indicates the URI by which the newly created document should be known. Success
202 - Accepted The request has been accepted for processing, but the processing has not been completed. The request may or may not eventually be acted upon, as it may be disallowed when processing actually takes place. There is no facility for status returns from asynchronous operations such as this. Success
203 - Partial Information When received in the response to a GET command, this indicates that the returned meta information is not a definitive set of the object from a server with a copy of the object, but is from a private overlaid web. This may include annotation information about the object, for example. Success
204 - No Response Server has received the request but there is no information to send back, and the client should stay in the same document view. This is mainly to allow input for scripts without changing the document at the same time. Success
205 - Reset Content Request processed, no content returned, reset document view. Success
206 - Partial Content partial resource return due to request header. Success
207 - Multi-Status XML, can contain multiple separate responses. Success
208 - Already Reported results previously returned. Success
226 - Im Used request fulfilled, response is instance-manipulations. Success
301 - Moved The data requested has been assigned a new URI, the change is permanent. (N.B. this is an optimisation, which must, pragmatically, be included in this definition. Browsers with link editing capabiliy should automatically relink to the new reference, where possible) Redirection
302 - Found The data requested actually resides under a different URL, however, the redirection may be altered on occasion (when making links to these kinds of document, the browser should default to using the Udi of the redirection document, but have the option of linking to the final document) as for "Forward". Redirection
303 - Method Like the found response, this suggests that the client go try another network address. In this case, a different method may be used too, rather than GET. Redirection
304 - Not Modified If the client has done a conditional GET and access is allowed, but the document has not been modified since the date and time specified in If-Modified-Since field, the server responds with a 304 status code and does not send the document body to the client. Redirection
305 - Use Proxy Content located elsewhere, retrieve from there. Redirection
306 - Switch Proxy Subsequent requests should use the specified proxy. Redirection
307 - Temporary Redirect Connect again to different URI as provided. Redirection
308 - Permanent Redirect Connect again to a different URI using the same method. Redirection
400 - Bad Request The request had bad syntax or was inherently impossible to be satisfied. Client side error
401 - Unauthorized The parameter to this message gives a specification of authorization schemes which are acceptable. The client should retry the request with a suitable Authorization header. Client side error
402 - Payment Required The parameter to this message gives a specification of charging schemes acceptable. The client may retry the request with a suitable ChargeTo header. Client side error
403 - Forbidden The request is for something forbidden. Authorization will not help. Client side error
404 - Not Found The server has not found anything matching the URI given. Client side error
405 - Method Not Allowed Request method not supported by that resource. Client side error
406 - Not Acceptable Content not acceptable according to the Accept headers. Client side error
407 - Proxy Authentication Required Client must first authenticate itself with the proxy. Client side error
408 - Request Timeout Server timed out waiting for the request. Client side error
408 - Conflict Request could not be processed because of conflict. Client side error
410 - Gone Resource is no longer available and will not be available again. Client side error
411 - Length Required Request did not specify the length of its content. Client side error
412 - Precondition Failed Server does not meet request preconditions. Client side error
413 - Request Entity Too Large Request is larger than the server is willing or able to process. Client side error
414 - Request URI Too Large URI provided was too long for the server to process. Client side error
415 - Unsupported Media Type Server does not support media type. Client side error
416 - Requested Rage Not Satisfiable Client has asked for unprovidable portion of the file. Client side error
417 - Expectation Failed Server cannot meet requirements of Expect request-header field. Client side error
418 - I'm a teapot I'm a teapot. Client side error
420 - Enhance Your Calm Twitter rate limiting. Client side error
421 - Misdirected Request Server is not able to produce a response. Client side error
422 - Unprocessable Entity Request unable to be followed due to semantic errors. Client side error
423 - Locked Resource that is being accessed is locked. Client side error
424 - Failed Dependency Request failed due to failure of a previous request. Client side error
426 - Upgrade Required Client should switch to a different protocol. Client side error
428 - Precondition Required Origin server requires the request to be conditional. Client side error
428 - Too Many Requests User has sent too many requests in a given amount of time. Client side error
431 - Request Header Fields Too Large Server is unwilling to process the request. Client side error
444 - No Response Server returns no information and closes the connection. Client side error
448 - Retry With Request should be retried after performing action. Client side error
450 - Blocked By Windows Parental Controls Windows Parental Controls blocking access to webpage. Client side error
451 - Wrong Exchange Server The server cannot reach the client's mailbox. Client side error
498 - Client Closed Request Connection closed by client while HTTP server is processing. Client side error
500 - Internal Error The server encountered an unexpected condition which prevented it from fulfilling the request. Server side error
501 - Not Implemented The server does not support the facility required. Server side error
502 - Service temporarily overloaded The server cannot process the request due to a high load (whether HTTP servicing or other requests). The implication is that this is a temporary condition which maybe alleviated at other times. Server side error
503 - Gateway timeout This is equivalent to Internal Error 500, but in the case of a server which is in turn accessing some other service, this indicates that the respose from the other service did not return within a time that the gateway was prepared to wait. As from the point of view of the client and the HTTP transaction the other service is hidden within the server, this maybe treated identically to Internal error 500, but has more diagnostic value. Server side error
504 - Gateway Timeout Gateway did not receive response from upstream server. Server side error
505 - Http Version Not Supported Server does not support the HTTP protocol version. Server side error
506 - Variant Also Negotiates Content negotiation for the request results in a circular reference. Server side error
507 - Insufficient Storage Server is unable to store the representation. Server side error
508 - Loop Detected Server detected an infinite loop while processing the request. Server side error
508 - Bandwidth Limit Exceeded Bandwidth limit exceeded. Server side error
510 - Not Extended Further extensions to the request are required. Server side error
511 - Network Authentication Required Client needs to authenticate to gain network access. Server side error
598 - Network Read Timeout Error Network read timeout behind the proxy. Server side error
598 - Network Connect Timeout Error Network connect timeout behind the proxy. Server side error