308 Permanent Redirect
3xx redirect
The resource has permanently moved to another URL and the request method and body must be preserved, the permanent counterpart to 307.
Common causes
- An API path was permanently renamed during a version bump.
- A host consolidation moves write endpoints to a canonical domain.
- A route map was rewritten permanently in the reverse proxy.
How to fix it
- Send clients straight to the final URL so the chain has one hop.
- Update documentation, SDKs, and internal callers to the new endpoint.
- Keep the rule for as long as old clients may still call the path.
What it means for redirects and SEO
Permanent and method preserving, so it is the safe choice for redirecting POST endpoints during a permanent migration. Browsers cache it aggressively, which makes mistakes hard to undo. Search engines treat it as a permanent move and pass signals to the target.
Trace a link that returns 308 →