301 vs 302 Redirects: When to Use Each and Why It Matters for SEO
Redirects tell the browser and search engines that a URL has moved. The difference between 301 and 302 tells Google whether the move is permanent or temporary - and this has significant SEO implications for how PageRank is transferred.
301 Moved Permanently
A 301 tells Google the page has permanently moved to a new URL. Google transfers almost all the PageRank (link equity) from the old URL to the new URL. Google deindexes the old URL and indexes the new one. This is what you should use for: URL restructuring, migrating from HTTP to HTTPS, changing a page slug permanently, moving a site to a new domain, and consolidating duplicate content. Use 301 for any redirect you intend to keep permanently - more than a few weeks.
302 Found (Temporary Redirect)
A 302 tells Google the page has temporarily moved. Google keeps the original URL in its index and does not fully transfer PageRank to the destination. Use 302 for: A/B testing where you temporarily redirect users to a test page, maintenance pages, temporarily redirecting a seasonal page during off-season, and short-term promotional redirects. The key word is temporary - if the redirect will exist for more than a few weeks, use 301.
What Happens If You Use 302 Instead of 301
If you use a 302 for a permanent move, Google keeps indexing the original URL instead of the destination. Any PageRank from links pointing to the original URL stays on the original page rather than flowing to the new destination. Over time Google may treat a long-standing 302 as a 301 (this behavior varies), but relying on this is risky. Using 302 for HTTP to HTTPS migration is a particularly common mistake that prevents the full transfer of link equity to the HTTPS version.
Other Redirect Types Worth Knowing
307 Temporary Redirect: The modern equivalent of 302, preserves the HTTP method (POST stays POST). Use for temporary API redirects. Google treats it the same as 302.
308 Permanent Redirect: The modern equivalent of 301, preserves the HTTP method. Use for permanent API redirects. Google treats it the same as 301.
410 Gone: Not a redirect - tells Google the page was intentionally deleted and is not coming back. Google removes 410 pages from the index faster than 404 pages. Use 410 for permanently deleted content that had backlinks or indexed status.
Sitemaps and Redirects
Your sitemap should never contain URLs that redirect. If a URL in your sitemap returns a 301 or 302, Google Search Console reports it as an error under "Submitted URL has redirect." Update your sitemap to contain only the final destination URLs that return 200. After any URL migration, audit your sitemap to replace all old URLs with their new canonical destinations.
Related Guides
- Technical SEO Checklist 2025
- Canonical Tags: How to Use Them Correctly for SEO
- Structured Data & Schema Markup: Complete Guide
- Core Web Vitals: LCP, INP, CLS Explained
- Page Speed Optimization: Make Your Site Faster
- URL Canonicalization: Fix Duplicate URLs
- Meta Refresh Redirect: SEO Impact & Better Alternatives
- Meta Tag Redirect: Why It Hurts SEO and What to Use Instead
- 307 Redirect SEO: Temporary Redirect vs 301 and 302
- SEO Migration Checklist: Don't Lose Rankings When You Migrate
- WWW vs Non-WWW: How to Set Up the Correct Redirect