---
title: "302 Found (Temporary Redirect)"
canonical: "https://lemwatch.com/http-status-codes/302"
category: "redirection"
last_verified: "2026-08-11"
source: "https://lemwatch.com"
---

# HTTP 302 Found (Temporary Redirect)

**TL;DR** — A 302 means "temporary detour, keep using the original URL next time." Use it for genuine short-term redirects: A/B tests, login flows, geo redirects, brief maintenance. Don't use it for permanent moves — Google will eventually treat long-standing 302s as 301s, but until it does, you're leaking ranking equity. If method preservation matters (POST stays POST), use 307 instead.

## What it means

HTTP 302 Found is the "temporary redirect" code. Unlike 301, it tells search engines that the original URL should remain canonical — they should keep indexing it and not transfer ranking signals to the new URL. This makes 302 the correct choice when the move genuinely is temporary: A/B testing, geolocation-based redirects, login flows that send users to /auth and back, or short maintenance windows where the URL will return. Historically, some old HTTP clients changed POST requests to GET during a 302 redirect (a spec-versus-practice mismatch). When method preservation matters, use 307 (temporary) or 308 (permanent) instead.

## Common causes

- A/B testing redirect to a variant page
- Geolocation: /pricing → /pricing/uk for UK visitors
- Login required: /dashboard → /auth?return=/dashboard
- Short-term maintenance redirect to a status page
- Mobile/desktop split when serving different URLs per device
- Default behaviour of Express.js res.redirect() (sends 302 unless you specify 301)
- Marketing campaign URL temporarily pointing to a landing page

## How to fix

- If the move is actually permanent, switch to 301 — Google will transfer ranking signals
- If you need POST/PUT/DELETE to survive the redirect, use 307 instead of 302
- Make sure the redirect destination returns 200 OK — a 302 pointing to a 404 wastes both clicks and crawl budget
- Don't leave a 302 in place for years if the original URL will never return — Google's reclassification to 301 is slow and unreliable
- For login redirects, include a return parameter so users land on the page they wanted after authenticating
- Limit redirect chains: a 302→302→200 still drops crawl efficiency at each hop

## SEO impact

Google does not transfer ranking signals through a 302 — the original URL stays canonical and keeps its rankings. This is correct behaviour when the move is genuinely temporary. When it is not temporary, you are leaking ranking equity until Google decides to treat the 302 as a 301 (which it does, eventually, for redirects that have been in place for a long time — but the delay can be months). Always use 301 for permanent moves.

## Monitoring tip

LemWatch flags long-running 302 redirects (in place for more than 30 days) and recommends switching to 301 if the move is permanent. We also track 302 chains, which dilute ranking signals at every hop.

**Related:** [301](https://lemwatch.com/http-status-codes/301.md), [303](https://lemwatch.com/http-status-codes/303.md), [307](https://lemwatch.com/http-status-codes/307.md), [308](https://lemwatch.com/http-status-codes/308.md)

_Canonical HTML page: https://lemwatch.com/http-status-codes/302_