Learn | httpstatus.io

Learn

Resources to understand all relevant details about status codes and redirects.

Status codes

Understanding how different HTTP status codes work and implementing them correctly within your website's architecture plays an important role in optimizing your site for a better user experience, maintaining SEO rankings and improving overall website performance.

Successful responses

200

OK

The 200 OK status code is a standard HTTP response status code indicating that the request has succeeded.

Successful responses

204

No Content

The 204 No Content status code is an HTTP response status code that indicates a request has been successfully processed, but there is no content to send back in the response body.

Redirection responses

301

Moved Permanently

The 301 Permanent Redirect status code is an HTTP response that indicates a permanent redirection of a URL to another URL.

Redirection responses

302

Found

The 302 Found status code is an HTTP response status code used to inform the client that the requested resource has been temporarily moved to a different location.

Redirection responses

307

Temporary Redirect

The 307 Temporary Redirect is an HTTP status code that indicates a temporary redirection of a URL. It is similar to the more commonly known 302 Found redirect, with the exception that the user agent must not change the HTTP method used.

Redirection responses

308

Permanent Redirect

The 308 Permanent Redirect status code is an HTTP response code that indicates a permanent redirection of a resource. This status has the same semantics as the 301 Moved Permanently HTTP response code, with the exception that the user agent must not change the HTTP method used.

Client error responses

401

Unauthorized

The 401 Unauthorized status code is an HTTP response status code that indicates the client attempting to access a resource has not provided valid authentication credentials for that resource.

Client error responses

403

Forbidden

The 403 Forbidden status code is an HTTP response status code that indicates the server understands the request but refuses to authorize it, and informs the client that it's not allowed to proceed further.

Client error responses

404

Not Found

The 404 Not Found status code is a standard HTTP response status code indicating that the client was able to communicate with the server, but the server could not find what was requested. It is one of the most common error codes encountered on the web.

Client error responses

410

Gone

The 410 Gone status code is an HTTP response status code that indicates that the requested resource is no longer available and has been intentionally removed.

Server error responses

503

Service Unavailable

The 503 status code is a server error response indicating that the server is currently unable to handle the request due to maintenance or overload. It implies that the issue is temporary and should be resolved once the server becomes available again.

Redirects

Redirects play a crucial role in managing websites effectively by seamlessly directing users and maintaining SEO rankings during changes in URL structure or webpage locations.

Redirect checker

What is a redirect checker?

A redirect checker is a tool or software that allows users to verify and analyze the redirection of URLs. It helps in determining whether a particular URL is redirecting correctly or not, and if it is, where it redirects to.

Canonical redirects

Why should you check for canonical redirects?

Regularly monitoring canonical redirects ensures their accuracy, allows you to identify potential issues early on, and maintain optimal SEO performance across your website with multiple similar URLs.

Redirect latency

Why can redirects be slow?

When the redirect latency is high, it means that there is a significant delay in the redirection process, resulting in slow redirects.

Redirect chains

What are redirect chains?

Redirect chains are a series of multiple redirects that occur when navigating from one webpage to another.

Redirect implementation

Client-side vs server-side redirects

Client-side redirects and server-side redirects are two different methods used to redirect users from one webpage to another.

Redirect implementation

How to bulk check redirects?

Efficiently check URL redirects, either manually through the web interface or programmatically using the API.

This website uses cookies to ensure you get the best experience. By using this website, you acknowledge that you understand and agree to our Privacy Policy and Terms and Conditions.