📚 Quick Definition

The target resource resides temporarily under a different URI. Since the redirection might be changed, the client should continue using the original URI for future requests. Unlike 301, this redirect signals that the move is not permanent and the original URL should remain the canonical location.

⏱ When It Occurs

A 302 Found response is returned when the server wants to temporarily redirect the client to a different URL. The key distinction from 301 is that this is a temporary situation - the original URL is still considered the correct, canonical location. Search engines will keep the original URL in their index.

⚠ Common Causes

  • Temporary maintenance redirect - Traffic rerouted during server maintenance or updates
  • A/B testing - Users redirected to different page variants for testing
  • Login redirect - Unauthenticated users sent to the login page temporarily
  • Geo-based routing - Users redirected to region-specific content

🛠 How to Fix

  1. Use 301 if permanent - If the redirect will never revert, switch to 301 for SEO benefit
  2. Check server configuration - Verify the redirect is intentional and not a misconfiguration
  3. Avoid caching issues - Browsers may cache 302s unexpectedly; set proper Cache-Control headers
  4. Test redirect destination - Ensure the temporary target URL is working correctly

🛠 Common Use Cases

  • A/B testing redirects (sending some users to variant pages)
  • Maintenance page redirect (temporarily sending users to a maintenance notice)
  • Login redirect (redirecting unauthenticated users to a login page, then back)
  • Language or locale redirect (sending users to their regional version)
  • Temporary promotional redirect (holiday sale page, limited campaign)
  • Load balancing between servers

✅ Best Practices

  • Use 302 only for genuinely temporary redirects - use 301 for permanent moves
  • Search engines keep the original URL indexed, which is the desired behavior for temporary situations
  • Be aware that 302 may change POST to GET - use 307 to guarantee method preservation
  • Don't use 302 for permanent URL changes - this can confuse search engines and waste link equity
  • Consider user experience when using redirect chains - each hop adds latency

📡 HTTP Example

Request
GET /promo HTTP/1.1
Host: www.example.com
Response
HTTP/1.1 302 Found
Location: https://www.example.com/sale-page
Cache-Control: no-cache

❓ Frequently Asked Questions

Does 302 affect SEO? +
A 302 redirect has less SEO impact than a 301. With a 302, search engines keep the original URL indexed because the redirect is temporary. Link equity is not fully transferred to the new URL. If you accidentally use 302 for a permanent move, search engines may eventually treat it like a 301, but it is best to use the correct status code from the start.
When should I use 302 vs 307? +
Both 302 and 307 are temporary redirects, but 302 may change the request method from POST to GET when following the redirect. If you need to guarantee that the HTTP method (such as POST) is preserved during the redirect, use 307 Temporary Redirect instead. For simple GET redirects, 302 and 307 behave identically.
Can too many 302s cause problems? +
Yes, redirect chains (multiple 302s in sequence) can slow page loading, consume bandwidth, and confuse search engines. Each redirect adds a round-trip to the server, increasing latency. Search engines may also stop following chains after a few hops. Keep redirect chains to a minimum and aim for direct redirects whenever possible.