HTTP 3xx
301 Moved Permanently
The resource has permanently moved to a new URL. Browsers and search engines should update to the new location.
What causes it
- A URL was permanently changed, or the site redirects HTTP to HTTPS or a canonical domain.
How to fix it
Point links at the final URL to avoid an extra hop. Confirm the target is correct with a redirect checker.
Example response
A typical raw HTTP response a client receives for a 301, with the headers this code is defined around.
HTTP/1.1 301 Moved Permanently
Location: https://example.com/new-path
Content-Type: text/html; charset=utf-8Related codes
300
Multiple ChoicesThe request has more than one possible response and the client should choose one.303
See OtherThe response is at another URL and should be retrieved with a GET, regardless of the original method.302Common
FoundThe resource is temporarily at a different URL. Unlike a 301, clients keep using the original URL for future requests.304
Not ModifiedThe cached copy is still valid, so the server returned no body to save bandwidth.307
Temporary RedirectLike a 302, but the request method and body must not change on the redirected request.308
Permanent RedirectLike a 301, but the request method and body must not change.Know before your visitors do.
Sentinel checks your site around the clock from multiple regions and alerts you the moment it starts returning a 3xx error, so you can fix it before it costs you.