301 or 302? Choosing Wrong Quietly Costs You Rankings

Which redirect to use and when, what 404s really cost you, and how to clean up a site full of dead ends and redirect chains.

In this article 8 sections
  1. What the status codes actually mean
  2. When a 301 is right
  3. When a 302 is right
  4. What 404s actually cost
  5. Redirect chains: the silent tax
  6. The migration checklist (no tears edition)
  7. Keeping it clean with the redirection manager
  8. The short version

Pick the wrong one and nothing breaks loudly — which is exactly the problem. A 302 left on a permanent move keeps signals pointed at a URL you have abandoned; a 301 on a temporary move hands them away and is cached hard by browsers. Neither throws an error, and both cost you quietly for months.

The rule is simple once stated plainly: use a 301 redirect when a URL has moved permanently and you want search engines to transfer its signals to the new address; use a 302 redirect when the move is temporary and the original URL will return; and reserve 404 (or 410) for pages that are genuinely gone with no meaningful replacement. Nearly every redirect problem in the wild comes from mixing those three up, letting chains accumulate, or leaving 404s to pile up after a migration. This guide walks through when each status code is right, what 404s actually cost you, a migration checklist that prevents the tears, and how to keep it all tidy with a redirection manager.

What the status codes actually mean

HTTP status codes are the server's one-line answer to "where is this page?"

  • 301 Moved Permanently. "It lives at this new URL now, forever. Update your records." Search engines respond by transferring the old URL's accumulated signals to the new one and, over time, replacing the old URL in their index.
  • 302 Found (temporary redirect). "It's over there for now, but keep asking for this address." Search engines generally keep the original URL indexed and treat the destination as a stand-in.
  • 404 Not Found. "No such page." An honest, normal response for content that never existed or is gone without a successor.
  • 410 Gone. A firmer 404: "this existed and was deliberately removed." Search engines may drop 410 URLs from the index somewhat faster, but for most sites the practical difference is small.

When a 301 is right

Reach for a 301 whenever the change is permanent:

  • You changed a post's slug or moved it to a new category structure
  • You migrated domains, or moved from HTTP to HTTPS
  • You merged two overlapping articles into one stronger page
  • You retired a product but a close successor exists
  • You are consolidating www/non-www or trailing-slash variants (though canonical URLs should back this up)

The 301 is how the old URL's history (links from other sites, internal links, bookmark traffic) is inherited by the new one instead of evaporating. One rule of thumb prevents most equity waste: redirect to the most relevant live page, not the homepage. A blanket everything-to-homepage redirect treats a specific old page's visitors and signals as if they wanted your front door. Search engines often treat such irrelevant redirects like soft 404s anyway. If no relevant target exists, a clean 404 is more honest and more useful.

When a 302 is right

A 302 is correct when the original URL is coming back:

  • A product page redirected to a "back in stock soon" notice
  • A page temporarily pointed elsewhere during scheduled maintenance
  • A seasonal campaign URL parked between seasons
  • A/B-style routing where the canonical page remains the original

The classic mistake is the accidental permanent 302: a "temporary" redirect installed during a redesign and forgotten for two years. Search engines will eventually treat a long-lived 302 like a 301, but "eventually" is doing unpaid work you could have done deliberately. If the move turned out to be permanent, change it to a 301. If you cannot remember why a 302 exists, that is your answer.

Hydrogen SEO's redirection manager supports both 301 and 302, so choosing the correct status is a dropdown, not a server-config exercise. The full decision reference lives in the 301 vs 302 docs.

What 404s actually cost

A 404 is not an emergency in itself; every healthy site returns some. The cost comes from 404s at URLs that used to matter. Three costs, all real, none requiring invented statistics:

  1. Crawl waste. Crawlers revisit URLs they have seen before. Every request spent on a dead URL is attention not spent discovering or refreshing your live pages. On large sites, thousands of lingering 404s meaningfully dilute how often the pages you care about get crawled.
  2. Lost equity. When a page that earned external links dies without a redirect, everything those links conferred stops flowing anywhere. That authority was earned once and is simply discarded, and internal links that still point at the dead URL leak the same way. (Internal breakage is its own fixable problem; see our guide to internal linking strategy.)
  3. User trust. A visitor who followed a link from another site, an old email, or a search result and lands on "Not Found" rarely tries a second URL on your site. The error page is often the entire first impression.

Finding them is the first job: Hydrogen SEO's site audits flag broken internal links across the site, and the docs cover a full workflow to find and fix 404s, pairing each dead URL that matters with a redirect and leaving honest 404s alone.

Redirect chains: the silent tax

A redirect chain is a redirect pointing at another redirect: A → B → C. Chains happen naturally as sites age (a 2019 slug change stacked under a 2022 restructure stacked under an HTTPS migration), and they tax everything:

  • Each hop adds latency for every visitor
  • Crawlers follow a limited number of hops before giving up
  • Signals pass less cleanly through multiple hops than one

The fix is flattening: point A directly at C, and B directly at C. Whenever you add a new redirect, check whether anything already redirects to the URL you are now redirecting away from, and repoint it at the final destination. Doing this inside one redirection manager is far easier than doing it across scattered .htaccess rules, because every rule is visible in one list where chains are easy to spot. And update your own internal links to point at final URLs directly; a redirect is a patch, and a corrected link is the actual repair.

The migration checklist (no tears edition)

Site migrations lose rankings when redirect mapping is treated as a launch-day detail. Treat it as the core deliverable:

Before launch

  1. Crawl or export a complete list of current URLs, and pull your top pages from analytics and Search Console so you know which URLs carry the value.
  2. Build a one-to-one redirect map: every old URL to its most relevant new URL. Resist the homepage-dump shortcut.
  3. Decide what genuinely dies. Those URLs get a 404/410 on purpose, recorded, not by accident.
  4. Stage the redirects so they go live with the new site, not days after.

Launch day

  1. Deploy the redirect map as 301s.
  2. Spot-check your top pages by hand: old URL in, correct new page out, one hop.

After launch

  1. Watch Search Console's coverage and 404 reports for old URLs you missed, and add redirects as they surface.
  2. Update your XML sitemap to list only final, live URLs, never redirecting ones, and resubmit it. (More on that in our sitemap best practices guide.)
  3. Fix internal links still pointing at old URLs so the site stops relying on its own redirects.
  4. Keep the redirects in place long-term. Old external links never stop existing.

Keeping it clean with the redirection manager

Redirect hygiene fails when rules live in three places nobody reviews. Consolidating them into the plugin's redirection manager gives you one reviewable list: what redirects where, with which status. A quarterly pass takes minutes:

  • Flatten any chains that have crept in
  • Promote 302s that turned out to be permanent into 301s
  • Delete rules whose source URLs no longer receive any traffic or links, once they have done their job for a long while
  • Cross-check the site audit's broken-link findings and add redirects where warranted

If you would rather delegate the grunt work, Hydrogen AI, the agent in the plugin dashboard, takes plain-language instructions like "find and fix broken internal links," shows each proposed change, and asks before writing.

The short version

Permanent move: 301. Temporary move: 302. Genuinely gone: an honest 404, on purpose. Redirect to relevant targets, flatten chains, map every URL before a migration, and review the whole list a few times a year.

The Hydrogen SEO plugin includes the redirection manager and broken-link audits free, with no account needed. Install it and start free, or see pricing for the AI features when you want an agent doing the tedious parts.