308 Permanent Redirect
A permanent redirect that preserves the original request method.
What it means
HTTP 308 Permanent Redirect is like 301 but guarantees the request method and body are preserved. The resource has permanently moved to the Location URL, and clients must not change a POST into a GET when following it.
When it happens
It happens when permanently moving an endpoint that must keep its method — such as a permanently relocated API route that receives POST requests.
How to fix it
- Use 308 for permanent redirects where preserving the method matters; use 301 for ordinary page redirects.
- Point it straight at the final destination to avoid chains.
- Update internal references to the new URL.
SEO impact
Strong and positive, like a 301. Search engines treat 308 as a permanent move and transfer ranking signals to the new URL.
Find out which of your URLs return 308
Paste a list of URLs and Sitewell checks the status code of every one at once — free and without signup.
Related codes
The resource has permanently moved to a new URL.
302 FoundThe resource is temporarily at a different URL.
303 See OtherThe response to the request can be found at another URL using a GET request.
304 Not ModifiedThe cached version of the resource is still valid, so no body is sent.
305 Use ProxyA deprecated code telling the client it must reach the resource through a specified proxy.
306 Switch ProxyA reserved, unused status code that no longer carries any meaning.
Related guides
The difference between 301 and 302 redirects, when to use each, how they affect SEO and link equity, and how to verify a redirect is doing what you intended.
HTTP status codes explained: a practical primer for SEOsA plain-English primer on HTTP status codes for SEOs: what the 2xx, 3xx, 4xx, and 5xx families mean, which ones affect rankings, and the codes worth knowing.