Definition
A 302 redirect is a temporary server-side redirect that tells search engines the move is provisional and the original URL should remain indexed. Unlike a 301, a 302 does not transfer PageRank to the new URL because Google expects the original URL to return. A 302 redirect is appropriate for temporary maintenance pages, A/B tests, seasonal redirects, or pages under construction. The most common mistake is using a 302 instead of a 301 for permanent changes, which prevents SEO value transfer. It is recommended to regularly check your 302 redirects to ensure they should not have been converted to 301s over time, as this misuse can significantly dilute site authority.
Key Points
- Does not transfer SEO value (PageRank)
- The original URL remains indexed by Google
- Use only for genuinely temporary changes
Practical Examples
Seasonal redirect
An e-commerce site temporarily redirects its 'Winter Sale' page to 'Summer Sale' with a 302 during the summer season, keeping the winter page indexed.
Planned maintenance
During a 2-hour maintenance window, the site redirects via 302 to a temporary information page, avoiding 500 errors.
Frequently Asked Questions
Only for temporary changes: maintenance, A/B tests, seasonal redirects. If the change lasts more than a few weeks, use a 301.
Yes, if Google detects a 302 has been in place for a very long time, it may treat it as a 301. But this is unpredictable and it is better to use the correct code immediately.
Go Further with LemmiLink
Discover how LemmiLink can help you put these SEO concepts into practice.
Last updated: 2026-02-07