Cookies disclaimer

I agree Our site saves small pieces of text information (cookies) on your device in order to deliver better content and for statistical purposes. You can disable the usage of cookies by changing the settings of your browser. By browsing our website without changing the browser settings you grant us permission to store that information on your device.

4XX Pages

4xx pages - Raptor SEO Data

4XX pages are pages that return a status code beginning with 4, which means that they are inaccessible typically due not it not being found or not existing. These are errors and need to be resolved.

 

Check out the video below to understand what this data means and how you can use it in any time of SEO analysis or technical audit. At Raptor we have a huge suite of SEO tools that scrape data from sites using our advanced SEO web crawler, this video and geode is one of many that are designed to help you not only understand the SEO web data, but how we collect and analyse it.

 

 

Although this does not affect SEO directly large numbers of 4XX errors can cause issue and if your content needs to rank, this will have an impact as the page will not appear in the search results.

There are 33 types of 4XX error (come of which were essentially made as jokes and some are never used) and all of them are errors, any of these response codes identified during a crawl should be fixed. There are two components to fixing these errors:

Remove all links to 4XX Pages

The only way these URLs are found are by following links to them, often the intended page exists but the link has a typo. Use the broken link report provided by Raptor to identify where all the broken links are and then fix them by using the correct link URL.

 

Fix the Page Ensuring That They Are Accessible

If a page should exist but returned a status code of 4XX, the page should be fixed or created.

 

Types of 4XX Error

4XX response codes are inaccessible pages and are an error by definition.

400: Bad Request

Due to an apparent client error the either will not or cannot process the request,

401: Unauthorized

Similar to a 403 error, the server is essentially saying you do not have the right to access this page.

402: Payment Required

Originally  intended to digital cash or micropayment scheme this is not currently used.

403: Forbidden

This is where the server refuses access to the resources which could be due to a permissions issue.

404: Not Found

The resource was not found. This the most common type of 4XX error and simply states that what you are trying to access does not exist

405: Method Not Allowed

Examples of this error are a PUT request on a read-only resource or a GET request on a form that requires data to be presented via POST.

406: Not Acceptable

Although capable of delivering the content, the content is not acceptable according to the Accept headers.

407: Proxy Authentication Required

The user has not first authenticated itself with the proxy.

408: Request Timeout

The time to make the request exceeded the time limit set on server.

409: Conflict

Due to the conflict current in the state of the request, the request could no be processed.

410: Gone

The resource has been permanently removed.

411: Length Required

Because the length of the request must be specified, but was not, the request was refused.

412: Precondition Failed

This is when the server did not meet a precondition (of potentially multiple) that the requester put on the request header fields.

413: Request Entity Too Large

Server  is unwilling to process a request  this large and so is refused / denied.

414: Request-URI Too Long

The server will not process an URI (Uniform Resource Identifier) this long

415: Unsupported Media Type

The media type is not supported by the server.

416: Requested Range Not Satisfiable

The client requested a part of the file that the server cannot supply a portion of, thus refusing the whole request.

417: Expectation Failed

The server cannot meet the requirements of the Expect request-header field.

418: I'm a teapot (RFC 2324)

This is a comical response code that is never Actually returned!

420: Enhance Your Calm (Twitter)

420 Enhance Your Calm: Returned by the Twitter Search and Trends API when the client is being rate limited. I assume this is a reference to the marijuana (calm) component as ‘420’ is synonymous with this!

422: Un-processable Entity (WebDAV)

Due to semantic error the request could not be processed.

423: Locked (WebDAV)

Due the resource being locked; it cannot be requested.

424: Failed Dependency (WebDAV)

A prior dependant request failed, resulting in this (a subsequent) request failure.

425: Reserved for WebDAV

This error indicates an unwillingness to process a request that may be replayed.

426: Upgrade Required

The client should switch to a different protocol such as TLS/1.0, given in the Upgrade header field.

428: Precondition Required

This arises from a conflict from a conditional request that GETs a resources stat, modifies it, and PUTs it back to the server. However, whilst this happened the server state was modified by a third party leading to the aforementioned conflict.

429: Too Many Requests

Servers use time limiting schemes, if you exceed this with requests you will be unable to access the resource.

431: Request Header Fields Too Large

If collectively the header fields are considered too large, the server will be unwilling or unable to process the request.

444: No Response (Nginx)

444 Connection Closed Without Response. A non-standard status code used to instruct NginX to close the connection without sending a response to the client, most commonly used to deny malicious or malformed requests.

449: Retry With (Microsoft)

This indicates that the request cannot be processed because insufficient information was provided by the client.

450: Blocked by Windows Parental Controls (Microsoft)

This error is given when Windows Parental Controls are turned on and are blocking access to the given webpage.

451: Unavailable for Legal Reasons

For legal reasons the server is unable to process the request

499: Client Closed Request (Nginx)

A non-standard status code introduced by NginX for the case when a client closes the connection while NginX is processing the request.