302 Redirect
A 302 Redirect is an HTTP status code (302 Found) that tells browsers and search engines a web page's URL has temporarily moved to a different address. It directs users and crawlers to the temporary URL while signaling that the original URL will be restored. As a result, search engines keep the original URL in their index and preserve its link equity rather than transferring it to the temporary destination.
A 302 Redirect is an HTTP status code (302 Found) that tells browsers and search engines a web page's URL has temporarily moved to a different address. It directs users and crawlers to the temporary URL while signaling that the original URL will be restored. As a result, search engines keep the original URL in their index and preserve its link equity rather than transferring it to the temporary destination.
Why It Matters
Using a 302 redirect correctly protects the SEO value of your original page during temporary URL changes. When search engines receive a 302 response, they continue crawling and indexing the original URL, so once the temporary page is removed, the original page is immediately restored in search results. Conversely, misusing a 302 for a permanent URL change causes search engines to keep crawling the old URL, wasting crawl budget, while link equity never transfers to the new URL — potentially stalling or dropping your rankings. Google has stated that a 302 left in place for an extended period may eventually be reinterpreted as a 301, but because the timing of this reinterpretation is unpredictable, it is important to choose the correct status code from the start.
301 vs 302 Differences
| Attribute | 301 (Moved Permanently) | 302 (Found / Temporary) |
|---|---|---|
| Meaning | URL has permanently moved | URL has temporarily moved |
| Link equity transfer | 90–99% transferred to the new URL | Preserved on the original URL; not transferred |
| Search index | Old URL is removed from the index and replaced by the new URL | Old URL remains in the index |
| Browser caching | Cached permanently | Original URL is re-checked on every request |
| Use cases | Domain changes, URL restructuring, HTTP-to-HTTPS migration | A/B testing, maintenance pages, seasonal promotions, out-of-stock pages |
The key difference is whether link equity moves. A 301 passes the SEO value of the old page to the new URL, while a 302 keeps it on the original URL. Always use a 301 for permanent changes and a 302 for temporary ones.
When to Use a 302 Redirect
Use a 302 redirect when you plan to return to the original URL. Common scenarios include:
- A/B testing: Compare two versions of a landing page while preserving the original page's SEO value. Traffic is temporarily split to the test page, and the redirect is removed once testing concludes.
- Site maintenance: While updating or performing maintenance on your site, temporarily redirect users to an informational page. Remove the redirect once maintenance is complete.
- Seasonal or limited-time promotions: Redirect users to a special campaign landing page for the duration of a seasonal event, then restore the original URL when the promotion ends.
- Out-of-stock products: When a product is temporarily unavailable, redirect users to a similar product page, then restore the original page once the item is restocked.
- Geo-based redirects: Temporarily direct users to a localized or language-specific version of a page based on their geographic location.
Common Mistakes
- Using a 302 for permanent changes: Applying a 302 to a domain migration or URL restructuring — changes you never intend to reverse — causes search engines to keep crawling the old URL, and link equity will not transfer. Use a 301 instead.
- Leaving a 302 in place too long: If a 302 redirect remains active for several months, search engines may reinterpret it as a 301 at an unpredictable time. Once the temporary purpose is fulfilled, remove the 302 immediately or convert it to a 301.
- Skipping post-redirect monitoring: Without checking crawl status and indexing in Google Search Console after setting up a 302, you may miss the original URL being unexpectedly dropped from the index.
- Allowing redirect chains: When A redirects to B via a 302 and B redirects again to C, page load speed suffers and crawl efficiency drops. Redirect directly from A to C whenever possible.
- Redirecting to an unrelated page: Setting up a 302 to a page with entirely different content degrades user experience and may cause search engines to ignore the redirect entirely.
Sources:
- What's a 302 Redirect? And When Should You (Actually) Use It? - Semrush
- 301 vs. 302 Redirects for SEO: Which Should You Use? - Ahrefs
Related inblog Posts
How inblog Helps
inblog's dashboard supports 307 redirects (equivalent to 302) for temporary URL changes like A/B tests or maintenance pages.