All HTTP status codes

HTTP 301 Moved Permanently

Redirection

The resource has permanently moved to the URL in the Location header. Browsers cache it and search engines transfer ranking signals to the new URL.

Defined in RFC 9110

Common causes

  • Domain or path migrations (http→https, apex→www, renamed slugs)
  • Trailing-slash normalization

How to fix it

  1. Make sure the Location target is the final URL (avoid redirect chains)

  2. Method may be rewritten to GET by legacy clients — use 308 if the method must be preserved

  3. Remember browsers cache 301s aggressively; use 302 while still testing

Related status codes

302 Found

The resource temporarily lives at another URL. Search engines keep the original URL indexed; browsers don't cache the redirect.

308 Permanent Redirect

Permanent counterpart of 307: the resource moved for good and the method/body must be preserved when following the redirect.

Want to explore status codes interactively? Try the free HTTP Status Code Reference — search, categories and example responses, right in your browser.