What Is 308 Permanent Redirect

Content on WhatAnswers is provided "as is" for informational purposes. While we strive for accuracy, we make no guarantees. Content is AI-assisted and should not be used as professional advice.

Last updated: April 15, 2026

Quick Answer: A 308 Permanent Redirect is an HTTP status code introduced in 2015 with RFC 7538, indicating that a resource has permanently moved to a new URL and that future requests should use the new URI without changing the method or body.

Key Facts

The 308 status code was standardized in 2015 via RFC 7538
It preserves the original HTTP method and request body
Unlike 301, 308 does not allow method changes from POST to GET
Search engines treat 308 as a permanent redirect for SEO
It improves security and consistency in API and form handling

Overview

The 308 Permanent Redirect is an HTTP status code that signals a resource has permanently moved to a new URL. It ensures clients, including browsers and search engines, update their records and use the new address for all future requests.

Unlike earlier redirect types, 308 strictly maintains the original HTTP method and request body, making it ideal for APIs and form submissions. This prevents unintended behavior when redirecting POST or PUT requests.

Introduced in 2015 via RFC 7538, the 308 status code was created to resolve ambiguities in how clients handled permanent redirects with non-GET methods.
Preserves HTTP methods such as POST, PUT, or DELETE, ensuring the redirected request uses the same method as the original, unlike 301 redirects.
Requires exact URL updates — when a server returns 308, clients must change their bookmarks, links, and API endpoints to the new location permanently.
Search engines interpret 308 as a signal to transfer SEO equity, including rankings and indexing authority, from the old URL to the new destination.
Prevents data loss in form submissions by ensuring POST data is not dropped during redirection, a known issue with 301 redirects in older browsers.

How It Works

When a client requests a URL that has been permanently moved, the server responds with a 308 status and includes a Location header pointing to the new URL. The client must then repeat the request using the new URL and the same HTTP method.

HTTP Method Preservation: The 308 status requires that the client use the same HTTP method — such as POST or PUT — on the new URL, preventing silent downgrades to GET.
Request Body Retention: Unlike 301 redirects, 308 ensures that large payloads, like file uploads or JSON data, are not lost during redirection.
Location Header: The server must include a Location header specifying the new URI; otherwise, the redirect is invalid and may cause client errors.
Client Compliance: Modern browsers and HTTP clients like cURL or Axios support 308, but legacy systems may not handle it correctly without updates.
SEO Continuity: Google treats 308 redirects the same as 301s for crawling and indexing, transferring link equity and preserving search rankings.
Security Implications: By maintaining method integrity, 308 reduces risks of unintended data exposure, especially in authenticated or sensitive API transactions.

Comparison at a Glance

Below is a comparison of 308 with other common redirect types:

Redirect Type	Status Code	Method Preserved?	SEO Handled?	Introduced
301 Moved Permanently	301	No — often changes POST to GET	Yes	1999 (HTTP/1.1)
308 Permanent Redirect	308	Yes — strictly preserves method	Yes	2015 (RFC 7538)
302 Found	302	Historically inconsistent	No — temporary	1999
307 Temporary Redirect	307	Yes — preserves method	No — temporary	2015
303 See Other	303	No — forces GET	Limited use cases	1999

The table highlights how 308 fills a critical gap: permanent redirection with method integrity. While 301 has been widely used, its tendency to convert POST requests to GET made it unreliable for modern web applications. The 308 status, alongside 307, was introduced to bring clarity and consistency to HTTP redirects, especially for APIs and form processing.

Why It Matters

Understanding the 308 Permanent Redirect is essential for developers, SEO specialists, and system administrators managing web infrastructure. Its strict rules ensure reliability and security in data-sensitive environments.

API Stability: Services relying on RESTful APIs use 308 to redirect endpoints without breaking client integrations or losing request payloads.
SEO Optimization: Migrating websites with 308 ensures search engines transfer ranking signals, minimizing traffic drops during domain or URL changes.
Form Handling: E-commerce and login forms benefit from 308 by safely redirecting submissions without losing user data.
Security Compliance: Financial and healthcare platforms use 308 to maintain audit trails and prevent unintended method changes in transactions.
Modern Browser Support: Chrome, Firefox, Safari, and Edge have supported 308 since 2016, making it safe for production use.
Future-Proofing: As legacy 301 usage declines, 308 is becoming the standard for permanent redirects in web development best practices.

As web applications grow more complex, precise control over HTTP behavior becomes critical. The 308 Permanent Redirect offers a reliable, standardized solution for permanent moves, combining SEO friendliness with technical robustness.