301 vs 302 Redirect: When to Use Each and What Happens If You Get It Wrong

Why This Choice Matters More Than Most Technical Decisions

Choosing the wrong redirect type does not usually cause an immediate, visible problem. Your URL still redirects. Users still reach the destination. The issue builds slowly — link equity fails to pass correctly, crawl budget gets consumed by redirect chains, or Google becomes confused about which URL represents your canonical content. By the time the damage shows up in rankings data, the cause can be months old and hard to trace.

Understanding the difference between 301 and 302 redirects — and knowing exactly when to use each — is a fundamental technical SEO skill that applies every time you change a URL, migrate a page, rebuild a site, or manage a URL consolidation.

What 301 and 302 Redirects Actually Do

Both redirect types are HTTP status codes — the server's response to a browser request for a URL that no longer serves content at that address. The number tells the browser (and search engine crawler) how to interpret the redirect.

301 Moved Permanently tells the browser and search engine crawler: "This resource has moved to a new URL and is not coming back. Update your records. Treat the destination URL as the canonical location." Google consolidates the link equity from the original URL to the destination URL, typically transferring 90–99% of the original URL's ranking signals over a period of weeks to months. Browsers cache the destination URL after a 301 — future visits go directly to the destination without re-querying the original.

302 Found (sometimes seen as 302 Moved Temporarily) tells the browser and search engine: "This resource has temporarily moved to a different URL, but the original URL is still the intended destination. Do not update your records. The original URL is still canonical." Google does not consolidate link equity from a 302 — the original URL retains its signals and the destination does not receive them. Browsers do not cache a 302 — each request checks the redirect again.

The practical consequence: a 302 redirect on a permanently moved URL means that all the links pointing to the original URL continue benefiting the original URL — which no longer has content. The destination URL builds no equity from those links. Over time, the destination ranks poorly for the same terms the original URL used to rank for well.

When to Use 301

Use a 301 redirect in every situation where a URL change is permanent and you want to transfer ranking signals from the old URL to the new one.

Site migration — moving from HTTP to HTTPS, changing domain, or changing URL structure. Every old URL should 301 to its exact equivalent on the new domain or structure. Redirecting everything to the homepage (a "redirect cascade" or "redirect to root") loses the URL-specific link equity accumulated by individual pages.

Page consolidation — combining two pages about similar topics into a single, more comprehensive page. 301 both old URLs to the new consolidated URL. All link equity from both old pages flows to the new one.

Fixing canonical URL inconsistency — if your site serves content at both /page and /page/, or at both www and non-www, 301 all variants to the canonical version.

Retiring old content — blog posts, product pages, or landing pages that are being removed permanently should 301 to the most relevant alternative, not return a 404. A 404 loses all link equity from that URL. A 301 to the most relevant alternative passes most of that equity to a page that still exists.

Vanity URLs — short, memorable URLs used in offline marketing that redirect to longer tracking URLs. These are permanent redirects — the vanity URL is never going to serve content directly.

When to Use 302

Use a 302 redirect only when the original URL will genuinely return to serving its original content in the foreseeable future.

A/B testing — redirecting users to variant versions of a page while testing conversion performance. The original URL remains canonical and will serve the winning variant once the test concludes. Using a 302 here is correct — you do not want Google to consolidate signals to the test variant URL that will eventually disappear.

Maintenance mode — temporarily redirecting a URL to a maintenance page while the original content is being rebuilt. The original URL will resume serving content once maintenance is complete.

Geo or device-specific redirects — redirecting desktop users to one URL and mobile users to another, or redirecting based on geographic location, where both versions will continue to exist and serve different audiences. Though in most cases, Google recommends adaptive serving or separate URLs with proper canonical signals over redirect-based device separation.

The Most Common Mistakes

Using 302 when you mean 301. This is the most frequent error, often made by developers who treat 302 as a generic "redirect this URL" instruction without knowing the SEO implications. When a developer asks what type of redirect to use and you do not specify, they will typically default to 302 because it is simpler to implement in most frameworks. Always specify 301 for permanent redirects.

Redirect chains. A redirect chain occurs when URL A redirects to URL B which redirects to URL C. Google follows redirect chains but with reduced efficiency — crawl budget is consumed at each hop, and link equity degrades slightly at each step. The rule is to redirect directly to the final destination URL: A → C, not A → B → C. Audit redirect chains quarterly, particularly after site updates that may create new hops in existing chains.

Redirect loops. URL A redirects to URL B which redirects back to URL A. Nothing resolves. The user (and crawler) receives an error. This most commonly occurs during site migrations when redirect logic is applied to both the old and new servers without proper scoping.

Soft 404s masquerading as redirects. Redirecting a removed product page to the store homepage or a site-wide category page — rather than to the most relevant alternative product — is treated by Google as a soft 404 signal, not a meaningful redirect. The link equity is not transferred effectively. Always redirect to the closest contextually relevant live URL.

How Long Does It Take for 301 Equity to Transfer?

Google's documentation states that 301 redirects pass "most" of the link equity from the original URL, and that this transfer happens over time as Googlebot recrawls the pages. In practice, the transfer is not immediate. For a well-crawled site, you can expect 50–70% of ranking signals to have transferred within 4–6 weeks and 90%+ within 3–6 months after a properly configured 301. For sites crawled infrequently (large sites, low-authority domains), the timeline extends proportionally.

If you are tracking rankings for URLs that have been 301-redirected and see temporary ranking drops in the first few weeks, this is normal. The destination URL is building its inherited equity. Rankings typically recover and often improve once the 301 is fully processed, particularly if the destination URL has better content or more authoritative domain context.

For a complete technical SEO review of your site's redirect structure, see our technical SEO service.