DevToolPal
EN
3xx Redirection

301 Moved Permanently

What it means

The resource has moved permanently to the URL in Location. Clients and search engines should use the new URL from now on.

Common causes

  • A site moved to a new domain or to HTTPS
  • URLs were restructured
  • www and non-www were consolidated

How to fix it

As a client or visitor

Follow the redirect and update stored links or bookmarks. If you see a loop, clear the browser cache: browsers cache 301 aggressively.

As the site or API owner

Redirect each old URL to its exact new equivalent, not to the home page. Use 308 if POST requests must keep their method and body.

Example response

HTTP/1.1
HTTP/1.1 301 Moved Permanently
Date: Tue, 07 Oct 2025 09:30:00 GMT
Server: nginx
Location: https://www.example.com/new-path
Content-Length: 0

Specification

RFC 9110 §15.4.2

FAQ

› Does a 301 pass SEO value?

Yes. Search engines transfer ranking signals to the target and replace the old URL in results over time.

› Why does my browser keep redirecting after I removed a 301?

Browsers cache permanent redirects. Clear the cache or test in a private window; use 302 while testing.