301 Redirects: The Complete Guide to Moving Pages Without Losing Rankings
Redirects are how sites change without losing what they've earned — and redirect mistakes are how years of equity evaporate in an afternoon. The rules are few and unforgiving: right type, one hop, relevant destination, left in place long enough.
Here's the complete working guide to 301s.
Key takeaways
- 301 = permanent move and passes ranking signals; 302 = temporary — using the wrong one delays or splits consolidation.
- Redirect to the most relevant live page, not the homepage — bulk homepage redirects get treated as soft 404s.
- Chains and loops waste crawl and dilute signals: every redirect should resolve in one hop.
- Keep redirects live for the long haul — a year minimum, realistically as long as anything links to the old URL.
Choosing and mapping
Use 301 (or 308) when the move is permanent — deleted pages with a successor, renamed URLs, domain or HTTPS migrations, consolidated duplicates. Use 302/307 only for genuinely temporary states. For anything beyond a page or two, build a redirect map first: every old URL paired to its best-matching new destination, judged by content equivalence — the page a visitor wanting the old content should land on. No equivalent exists? A relevant category page beats the homepage; a clean 404/410 beats an irrelevant redirect that confuses users and engines alike.
Implementation that holds up
Implement at the server or edge (htaccess, nginx, CDN rules) rather than meta refreshes or JavaScript — those pass signals unreliably and slow users. Order rules so specific patterns fire before broad ones, and test the map before launch: crawl the old URL list and confirm every entry returns a single 301 to a 200 destination. After launch, watch Search Console for 404 spikes and crawl the old URLs again — migrations leak through forgotten parameters, casing variants, and trailing-slash mismatches that only testing catches.
Hygiene over time
- Update internal links to point at final destinations — internally linking through redirects wastes every crawl.
- Audit for chains quarterly: each hop added by successive site changes compounds until equity dribbles away.
- Never expire migration redirects on a schedule alone — external links and bookmarks reference old URLs for years.
- Keep the redirect map documented; the next migration starts from it instead of from archaeology.
Frequently asked questions
How much ranking value does a 301 pass?
Google treats proper 301s as passing full signals to a relevant destination. Losses come from irrelevant targets, chains, and broken implementations — not the redirect itself.
How long until rankings transfer after a redirect?
Individual pages often within weeks; full migrations can take months as the site is recrawled and reassessed. Stability of the new URLs matters — don't move twice.
Should I redirect expired product pages?
To the closest relevant alternative or category if one exists; otherwise a 410 with helpful navigation. Mass-redirecting everything to the homepage reads as soft-404 behavior.