---
title: "HTTP 301 Moved Permanently — What It Means & How to Fix It"
description: "HTTP 301 Moved Permanently: The requested resource has been permanently moved to a new URL. Common causes, fixes and how to monitor it."
url: https://uptrack.app/http/301
---

# HTTP 301 Moved Permanently

The requested resource has been permanently moved to a new URL. The server includes the new location in the Location header. Browsers and search engines will update their references to use the new URL.

## What does HTTP 301 mean?

The requested resource has been permanently moved to a new URL. The server includes the new location in the Location header. Browsers and search engines will update their references to use the new URL.

## Common causes

1. 1  
The website moved to a new domain (e.g., example.com to newexample.com) and set up permanent redirects.
2. 2  
URL structure changed — pages moved from /old-path to /new-path and the server redirects old URLs.
3. 3  
HTTP-to-HTTPS migration: the server permanently redirects all HTTP requests to HTTPS.

## How to fix it

1. 1  
Update your links and bookmarks to the new URL from the Location header. Browsers cache 301 redirects aggressively, so the old URL will auto-redirect.
2. 2  
If you control the server, ensure the Location header points to a valid destination. Avoid redirect chains (A -> B -> C) — redirect directly to the final URL.
3. 3  
For SEO, 301 is the correct redirect for permanent moves. Search engines transfer link equity to the new URL. Verify redirects with curl -I or browser dev tools.

## Monitor for HTTP 301 errors

Uptrack follows redirects by default and checks the final destination. If your redirect chain breaks or leads to an error page, Uptrack alerts you. You can also monitor the original URL to verify the redirect stays in place.

## Catch HTTP errors before your users do

Start free, or choose a plan, for 30-second monitoring and alert confirmation.

[See plans](https://uptrack.app/pricing)

from $3/mo · 30-day money-back guarantee

## Other HTTP status codes

- [HTTP 302 Found](https://uptrack.app/http/302)
- [HTTP 304 Not Modified](https://uptrack.app/http/304)
- [HTTP 204 No Content](https://uptrack.app/http/204)
- [HTTP 400 Bad Request](https://uptrack.app/http/400)
- [HTTP 201 Created](https://uptrack.app/http/201)
- [HTTP 401 Unauthorized](https://uptrack.app/http/401)
- [HTTP 200 OK](https://uptrack.app/http/200)
- [HTTP 403 Forbidden](https://uptrack.app/http/403)
- [HTTP 404 Not Found](https://uptrack.app/http/404)
- [HTTP 405 Method Not Allowed](https://uptrack.app/http/405)
- [HTTP 408 Request Timeout](https://uptrack.app/http/408)
- [HTTP 409 Conflict](https://uptrack.app/http/409)
- [HTTP 410 Gone](https://uptrack.app/http/410)
- [HTTP 413 Payload Too Large](https://uptrack.app/http/413)
- [HTTP 415 Unsupported Media Type](https://uptrack.app/http/415)
- [HTTP 422 Unprocessable Entity](https://uptrack.app/http/422)
- [HTTP 429 Too Many Requests](https://uptrack.app/http/429)
- [HTTP 451 Unavailable For Legal Reasons](https://uptrack.app/http/451)
- [HTTP 500 Internal Server Error](https://uptrack.app/http/500)
- [HTTP 502 Bad Gateway](https://uptrack.app/http/502)
- [HTTP 503 Service Unavailable](https://uptrack.app/http/503)
- [HTTP 504 Gateway Timeout](https://uptrack.app/http/504)
- [HTTP 520 Web Server Returns Unknown Error](https://uptrack.app/http/520)
- [HTTP 522 Connection Timed Out](https://uptrack.app/http/522)
