HTTP status code 301 — Moved Permanently
Quick answer
Status code 301 (Moved Permanently): Resource has a new permanent URI. Clients and SEO should update to the Location URL.
Clients and SEO should update to the Location URL.
301 tells caches and search engines the move is permanent. Prefer 301 over 302 when the old URL should never come back.
Common causes
- A page/route was renamed or merged elsewhere
- HTTP→HTTPS or www→apex canonicalization at the edge/CDN
How to fix it
Update the link/bookmark to the Location URL — browsers cache 301s aggressively, so hard-refresh if it seems stuck on the old one.
Frequently asked questions
What is status code 301?
301 Moved Permanently: Resource has a new permanent URI. Clients and SEO should update to the Location URL.
When should I expect HTTP 301?
301 tells caches and search engines the move is permanent. Prefer 301 over 302 when the old URL should never come back.
What usually causes HTTP 301?
A page/route was renamed or merged elsewhere; HTTP→HTTPS or www→apex canonicalization at the edge/CDN.
How do I fix HTTP 301?
Update the link/bookmark to the Location URL — browsers cache 301s aggressively, so hard-refresh if it seems stuck on the old one.
Where can I see all status codes?
Open the HTTP status codes hub on TryDevSnip for the full reference list.
Does TryDevSnip log my API traffic?
No. These pages are static reference. TryDevSnip does not proxy or inspect your HTTP calls.