01 — OverviewWhat Is a 308 Permanent Redirect?
A 308 redirect is beneficial when you're permanently modifying URLs or moving resources. It's also useful when you're rebuilding a website. Effective execution of redirects is also an essential component of technical SEO services, which helps to keep URL structures clean as well as reduce unneeded crawling difficulties.
02 — MechanicsHow Does a 308 Permanent Redirect Work?
If an individual or search engine tries to access a URL that has permanently been transferred, the server will display a 308 status code and the new destination URL. The browser or client then proceeds with the redirect and demands the resource at the updated location.
For example:
Old URL: https://example.com/old-page
New URL: https://example.com/new-page
The server may return:
HTTP/1.1 308 Permanent Redirect
Location: https://example.com/new-page
The important thing about a 308 redirect is that it keeps the original HTTP method and request body. For example, a POST request continues to be a POST after the redirect. This makes 308 especially useful for APIs and applications where you must preserve request protocols.
03 — Use CasesWhen Should You Use a 308 Redirect?
Use a 308 redirect when a URL has been moved permanently and maintaining the primary request method is essential.
Common situations include:
- Permanently moving an API endpoint
- Changing URLs while preserving POST or PUT requests
- Restructuring website URLs
- Moving resources to a new location
- Standardizing URL formats
- Permanently redirecting application endpoints
- Moving a website or resource to a new address
Correct redirect planning can be included in wider SEO Services, especially when it involves website migration, URL changes, and major website redesigns.
04 — Comparison308 Permanent Redirect vs. Other Redirects
A 308 Permanent Redirect is similar to a 301, as both signify that the URL has permanently changed. But a 308 keeps the original HTTP method and request body.
Additionally, a 302 and 307 are brief redirects, but a 307 also keeps the original request method, so in technical terms it is similar to a 308.
301 and 308 redirects also tell search engines that a page has been moved to a newly created website address permanently.
The appropriate redirect is determined by whether the move is permanent or temporary and whether it is important to preserve the original request method.
| Redirect | Type | Method Preserved | Common Use |
|---|---|---|---|
| 301 | Permanent | Not strictly preserved | Permanent URL changes |
| 302 | Temporary | Not strictly preserved | Temporary URL changes |
| 307 | Temporary | Yes | Temporary method-sensitive redirects |
| 308 | Permanent | Yes | Permanent method-sensitive redirects |
05 — SEO ImpactDoes a 308 Redirect Affect SEO?
A well-implemented 308 redirect can be useful for SEO when a URL has moved forever. Search engines recognize that the old URL has been replaced by a fresh URL through the redirect. Google considers a 308 redirect a permanent redirect, just like a 301.
But a 308 redirect doesn't instantly enhance your rankings. The landing page should be relevant to the original URL, crawlable by search engines, and technically competent.
Website owners should also prevent unneeded redirect chains. A clean way to do this is to set up a simple redirect from the old URL to its final destination, which makes it easier for users and search engine crawlers to follow.
06 — PitfallsCommon 308 Redirect Mistakes
Avoiding common redirect mistakes helps with proper crawling, indexing, website navigation, and user experience.
- Using 308 for Temporary Changes: If you use a permanent redirect for a temporary change, you can send the wrong signals to search engines and visitors.
- Creating Redirect Chains: Several redirections between the initial and the final URL can add additional delays and make crawling less effective.
- Creating Redirect Loops: Redirect loops are problematic because they stop users and search engines from accessing the page they are trying to reach.
- Redirecting to Irrelevant Pages: Redirecting users to irrelevant pages may result in bad experiences and decrease the value of the redirect.
- Retaining Old Internal Links: Such internal links to redirected URLs result in needless redirects and usually make the navigation of the website less efficient.
- Failing to Test Redirects: Untested redirects can lead to wrong destinations, broken pages, redirect loops, or unexpected status code errors.
07 — How-ToHow to Check a 308 Permanent Redirect
You can test a 308 redirect by looking at the HTTP response from the old URL. With SEO tools, browser developer tools, and HTTP header inspection tools, you can see the status code and destination URL.
When looking for a 308 redirect, make sure:
- The old URL returns a 308 status code.
- The destination URL is correct.
- The new URL loads successfully.
- There are no redirect chains or loops.
- Internal links point directly to the final URL.
- The destination page is relevant to the original content.
- Search engines can access the destination.
08 — TakeawayFinal Thoughts
A 308 Permanent Redirect is a way of permanently redirecting a URL while keeping the primary HTTP request method and its body. This is especially helpful for APIs, forms, and applications where modifications to the request method can lead to unexpected behavior.
A well-implemented 308 can help convey a permanent URL change and assist in preserving a clean website layout for SEO purposes. Great SEO Content Writing and redirects also have the potential to keep new destination pages relevant, useful, and in line with search intent.
09 — FAQsFrequently Asked Questions
What is a 308 permanent redirect in simple words?
It's an HTTP status code telling browsers and search engines that a URL has been permanently moved to a new address, while passing on the original request method and request body to the new URL.
What's the difference between a 301 and a 308 redirect?
Both are permanent and tell search engines the page has moved for good. The difference is that a 308 keeps the original HTTP method and request body, while a 301 does not strictly preserve the method.
What's the difference between a 307 and a 308 redirect?
Both preserve the original request method. A 307 is temporary and a 308 is permanent, so a 308 tells browsers and search engines that the move is permanent.
Does a 308 redirect affect SEO?
A well-implemented 308 can help SEO when a URL has moved permanently, as Google treats it like a 301. It doesn't instantly improve rankings, and the destination page should be relevant and crawlable.
When should I use a 308 redirect?
Use a 308 when a URL has moved permanently and preserving the original request method matters, such as moving API endpoints, keeping POST or PUT requests, or restructuring URLs.