A 302 redirect is an HTTP response with status code 302 (Found). It tells the browser — and search engines — that a URL has temporarily moved to a different location. Unlike a 301 (permanent redirect), search engines keep the original URL in their index when they see a 302, because they expect the original URL to return.
How a 302 Differs from a 301
- 301 Moved Permanently — The page has moved for good. Search engines update their index to the new URL and transfer link equity. Browsers cache the redirect.
- 302 Found (Temporary) — The page has moved for now. Search engines keep the original URL indexed. Browsers do not cache the redirect.
When to Use a 302 Redirect
- A page is temporarily down for maintenance and is being served from another URL.
- Running an A/B test and sending half of traffic to a variant URL.
- Showing a localised version of a page while the original URL remains canonical.
- Redirecting during a checkout flow where the original URL must remain active.
Common Mistake: Using 302 Instead of 301
Many developers use 302 when they mean to use 301. If a page has permanently moved or been deleted and replaced, use a 301. Using a 302 in this scenario means search engines never consolidate ranking signals to the destination, causing the original (dead) URL to compete against the new one.
Checking Redirect Types
Use browser developer tools (Network tab) or an HTTP header checker tool to see the exact status code returned for any URL.