Redirection
301 301 Moved Permanently
The resource has a new permanent home. Browsers cache this aggressively and search engines pass almost all ranking signal to the target, which makes it the correct redirect for a real move — and painful to undo.
Common causes
- A site migration, an HTTPS switch, or a www/non-www canonical rule.
- Chains of several 301s where each rule was added separately over the years.
How to fix it
- Use 301 only when the move is genuinely permanent.
- Collapse chains so visitors reach the final URL in one hop — every extra hop is a full round trip.
- If you might reverse it, use 302 instead: browsers remember a 301 for a very long time.
See what a site actually returns
Run a live check and read the real status code, headers and timings.
Other status codes
200 OK
201 Created
204 No Content
206 Partial Content
302 Found
303 See Other
304 Not Modified
307 Temporary Redirect
308 Permanent Redirect
400 Bad Request
401 Unauthorized
403 Forbidden
404 Not Found
405 Method Not Allowed
408 Request Timeout
410 Gone
413 Payload Too Large
418 I'm a Teapot
429 Too Many Requests
451 Unavailable For Legal Reasons
500 Internal Server Error
501 Not Implemented
502 Bad Gateway
503 Service Unavailable
504 Gateway Timeout
507 Insufficient Storage
508 Loop Detected
521 Web Server Is Down
522 Connection Timed Out
523 Origin Is Unreachable
525 SSL Handshake Failed