Skip to content

301 vs 308

Moved Permanently vs Permanent Redirect

301Moved Permanently

We've moved! Like forwarding your mail after moving to a new house. Update your bookmarks!

HTTP Response
HTTP/1.1 301 Moved Permanently
Location: https://new-site.com/page

308Permanent Redirect

Permanent new address, same attitude! The resource moved forever but you can keep doing your thing the same way.

HTTP Response
HTTP/1.1 308 Permanent Redirect
Location: /new-permanent-endpoint
πŸ“¦301Moved Permanently
🏠308Permanent Redirect

Redirect Codes: Permanent vs Temporary

Permanent Redirects

301
Moved Permanently
πŸ“¦
Old-Style Permanent

Classic redirect

Resource has permanently moved. Browsers and search engines will update their bookmarks and indexes.

  1. POST /old-url
  2. Server responds with new location
    301 β†’ /new-url

⚠️ May change to GET

Key behavior:
  • Browser caches the redirect
  • SEO: Link juice transferred
  • ⚠️ May change POST to GET
308
Permanent Redirect
πŸ”’
Modern Permanent

Method-preserving

Like 301, but guarantees the HTTP method and body won't change during redirect.

  1. POST /old-url
  2. Server responds with new location
    308 β†’ /new-url

βœ“ Keeps POST method

Key behavior:
  • Browser caches the redirect
  • SEO: Link juice transferred
  • βœ“ Preserves HTTP method

Temporary Redirects

302
Found
πŸ”„
Old-Style Temporary

Classic temporary

Resource is temporarily at another location. Original URL should still be used in the future.

  1. POST /temp-moved
  2. Server responds with temp location
    302 β†’ /temp-url

⚠️ May change to GET

Key behavior:
  • No browser caching
  • SEO: Original URL preserved
  • ⚠️ May change POST to GET
307
Temporary Redirect
πŸ”ƒ
Modern Temporary

Method-preserving

Like 302, but guarantees the HTTP method and body won't change during redirect.

  1. POST /temp-moved
  2. Server responds with temp location
    307 β†’ /temp-url

βœ“ Keeps POST method

Key behavior:
  • No browser caching
  • SEO: Original URL preserved
  • βœ“ Preserves HTTP method

Quick Decision Guide

Use Permanent (301/308) when:
  • URL has changed forever
  • You want search engines to update their index
  • Domain migration or restructuring
  • Old URL should never be used again
Use Temporary (302/307) when:
  • Resource is temporarily unavailable
  • A/B testing or maintenance mode
  • You want to keep the original URL active
  • Redirect might change or be removed soon
Use Modern (307/308) when:
  • Redirecting POST/PUT/DELETE requests
  • Request body must be preserved
  • Working with REST APIs
  • Modern application with strict HTTP semantics
πŸ’‘

Key Insight

Permanent vs Temporary controls caching and SEO, while Old vs Modern controls HTTP method preservation. For APIs and POST requests, prefer 307/308. For simple page redirects, 301/302 are widely supported and sufficient.

Description

The URL of the requested resource has been changed permanently. The new URL is given in the response.

When to Use
  • The resource URL has changed permanently and will never return
  • You want search engines to update their index to the new URL
  • Consolidating multiple URLs to a canonical URL for SEO
Common Causes
  • Website restructured with new URLs
  • Domain name changed
  • Page permanently relocated
Description

The resource has permanently moved to another URI, specified in the Location header. Method and body unchanged.

When to Use
  • Permanent redirect that must preserve the HTTP method (POST stays POST)
  • API endpoints that have moved permanently
  • Preferred over 301 when method preservation is critical
Common Causes
  • API endpoint permanently moved
  • Maintaining POST method during redirect
  • Permanent URL restructuring

Decision Tree

Is this redirect permanent?

Yes

Must the HTTP method be preserved (e.g., POST stays POST)?

Yes

Use 308 Permanent Redirect

Status Code: 308

No

Use 301 Moved Permanently

Status Code: 301

No

Use 302 or 307 (see 302-307 decision tree)

Status Code: 302