When a page moves, a redirect signals its new address. Understanding the difference between 301 and 302 redirects helps maintain SEO value. This guide covers definitions, use cases, SEO impact, and common pitfalls.
HTTP redirect codes
HTTP uses status codes to signal page moves. Two common codes are 301 and 302.
| code | redirect type | link equity | caching |
|---|---|---|---|
| 301 | permanent move | full transfer | cached indefinitely |
| 302 | temporary move | no transfer | requires fresh request |
301 permanent redirect
A 301 redirect indicates a permanent move. It tells browsers and search engines to use the new URL going forward.
It passes almost all link equity to the new address. See what are 301 redirects for more background.
302 temporary redirect
A 302 status code signals a temporary move. Browsers request the original URL on future visits.
It does not pass full link equity. Use for testing, time-limited offers, or maintenance windows.
Redirect use cases
Permanent moves
Use a 301 redirect when a page moves long-term. Ideal for domain migrations, URL restructuring, archived content.
Keep the redirect live for at least one year.
Temporary changes
Choose a 302 redirect for brief moves. Useful for A/B testing, flash sales, or site updates.
Confirm the original URL will return.
SEO impact overview
Link equity transfer
301 redirects pass almost all link equity to the new page. That helps preserve rankings.
In contrast, 302 redirects do not transfer full value. They may split popularity between URLs.
Indexing and caching
Search bots replace old URLs when they spot a 301 redirect. That consolidates signals under the new address.
Browsers cache 301 redirects indefinitely until cache is cleared. In contrast, a 302 forces fresh server requests. That lets servers adjust the target on each hit.
It can aid analytics but increase load.
Common redirect pitfalls
Redirect chains and loops
Long redirect chains slow page loads. They hurt user experience and rankings.
Loops lock browsers in infinite redirects. Always point redirects directly to final URL.
Cache misconfigurations
Incorrect 301 setups can mislead browsers. Caches may keep stale redirects even after fixes.
Clear caches or use shorter max-age in headers. Test redirects after deployment.
Redirect best practices
Audit and monitor
Schedule regular redirect audits. Check for broken chains, loops, and outdated rules.
Use tools like crawl bots or server logs. Update redirects when site structure changes.
Provide implementation guides
Follow server best practices for your stack. See how to implement 301 redirects.
For WordPress, check how to set up 301 redirects in WordPress. Document each change in version control or CMS notes.
Key redirect takeaways
- Use a 301 redirect for permanent URL moves
- Choose a 302 redirect for temporary changes
- Expect full link equity transfer with a 301
- Watch for chains, loops, and cache issues
- Audit redirects regularly and document changes
