Developer
Encoders, converters & dev utilities
301 Moved Permanently
HTTP 301 Moved Permanently. The resource has permanently moved to the URL in the Location header. Search engines transfer ranking/link equity to the new URL, and the redirect is cacheable by default. When to use it: Use for a permanent URL change you want indexed and cached — the canonical way to move a page for SEO. It is a redirection (3xx) status, so the client is expected to follow the Location header to another URL. (Reference: RFC 9110 §15.4.2.)
The resource has permanently moved to the URL in the Location header. Search engines transfer ranking/link equity to the new URL, and the redirect is cacheable by default.
- When to use: Use for a permanent URL change you want indexed and cached — the canonical way to move a page for SEO.
- How to handle: Update bookmarks, links, and canonical references to the new URL from the Location header.
- Reference: RFC 9110 §15.4.2
- Category: 3xx Redirection
Frequently asked questions
What does HTTP 301 mean?
HTTP 301 Moved Permanently: The resource has permanently moved to the URL in the Location header. Search engines transfer ranking/link equity to the new URL, and the redirect is cacheable by default. It is a redirection (3xx) status, so the client is expected to follow the Location header to another URL. It is defined in RFC 9110 §15.4.2.
What is the difference between 301 and 302?
301 Moved Permanently signals a permanent move: search engines transfer ranking to the new URL and the redirect is cacheable, so use it when a page has moved for good. 302 Found is a temporary redirect — clients should keep using the original URL and search engines do not pass ranking. Historically both could rewrite the method to GET; if you must preserve the method use 308 (permanent) or 307 (temporary).