301 Redirects: When to Use Them and SEO Pitfalls

301 Redirects: When to Use Them and How Not to Hurt SEO

A retailer we know moved to a new CMS over a weekend. Monday morning, organic traffic was down 40%. The pages still existed, the content was the same, but every old URL returned a 404. Google had thousands of indexed addresses pointing at empty space, and the rankings those URLs carried went with them.

Most of that damage came from one missing step: redirects. A 301 redirect is the instruction that tells a browser and a search engine "this page moved permanently, go here instead." Done right, it passes almost all of a page's accumulated ranking signals to the new address. Done wrong, or skipped, it throws those signals away.

This guide covers when a 301 is the correct tool, when something else fits better, and the specific mistakes that quietly cost rankings during URL changes and site migrations.

What a 301 actually does

When a server returns a 301 status code, it's making a permanent statement. The old URL is gone for good, and the new URL replaces it. Browsers update bookmarks. Search engines transfer the indexed page, its backlinks, and its ranking history to the destination.

That transfer is the whole point. A page that took two years to earn its position on page one of Google holds real equity: links from other sites, internal links, click history, age. Move the content to a new URL without a 301 and you start from zero. Add the 301 and you keep most of what you built.

Google has said for years that 301s pass full PageRank, and that the small loss once attributed to redirects no longer applies. Treat that as the working assumption, with one caveat: the redirect has to point to a genuinely equivalent page. Redirect an old product page to your homepage and Google often treats it as a soft 404, passing little or nothing.

When to use a 301

A 301 is correct any time a URL changes permanently and a real replacement exists. The common cases:

  • You changed a URL. Renamed a page, restructured a folder, cleaned up a messy slug. The old /services/ppc-management-2019 becomes /services/ppc-management. Redirect the old to the new.
  • You merged two pages. Two thin blog posts on the same topic become one strong guide. Redirect both old URLs to the combined page.
  • You moved to HTTPS. Every http:// URL should 301 to its https:// version. This is non-negotiable and usually handled at the server level.
  • You switched domains. Rebrand, acquisition, or a .net to .com move. Every old URL maps to its new-domain equivalent.
  • You consolidated www and non-www. Pick one canonical version and 301 the other so Google does not see two copies of every page.
  • You retired a page that has a clear successor. An old pricing page becomes the new plans page. Redirect it.

The thread running through all of these: the destination genuinely serves the same intent as the source. That is what makes the redirect "relevant" in Google's terms, and relevance is what lets the equity flow.

When a 301 is the wrong choice

Not every change is permanent, and forcing a 301 where it does not belong creates its own problems.

Use a 302 (temporary redirect) when the move is genuinely short-term: a page down for maintenance, a seasonal landing page that will return to its normal URL, an A/B test routing traffic between two live versions. A 302 tells Google to keep the original URL indexed because it is coming back. Use a 302 for a permanent move and you risk Google holding onto the old URL far longer than you want.

Skip redirects entirely when a page is simply gone with no replacement. A discontinued product with no equivalent should return a 410 Gone (or a 404). Redirecting dead pages to your homepage to "save" their traffic is a known anti-pattern. Google labels these soft 404s, passes no equity, and you end up with a homepage that confuses users who expected a product.

Here is how the main options compare:

Status Meaning Passes ranking signals? Use when
301 Moved permanently Yes, nearly all URL changed for good, equivalent page exists
302 Found / temporary Keeps old URL indexed Short-term move, A/B test, maintenance
307 Temporary (strict) Keeps old URL indexed Temporary, method-preserving (mostly technical)
410 Gone No, removes from index Page deleted, no replacement
Meta refresh Client-side redirect Weak, slow, unreliable Avoid for SEO

Avoid meta refresh and JavaScript redirects for anything SEO matters to. They are slower, search engines interpret them inconsistently, and a server-side 301 is both faster and clearer.

The mistakes that hurt rankings

A 301 is simple in theory. The damage shows up in the details.

Redirect chains

A chain is when URL A redirects to B, which redirects to C, which finally lands on D. Each hop adds latency, and long chains slow crawling and frustrate users. Google follows a limited number of hops before it may give up entirely.

Chains build up over years. Each site change adds a layer, and nobody flattens the old ones. The fix is to point every redirect at the final destination directly: A goes straight to D, not through B and C.

Redirect chain versus a direct redirect The top row shows URL A redirecting through B and C to reach D. The bottom row shows A redirecting straight to D. Chain (slow): A B C D Direct (fast): A D

Redirect loops

URL A redirects to B, and B redirects back to A. The browser bounces between them and gives up with an error. Loops usually come from conflicting rules, often a www rule fighting an HTTPS rule. Test redirects after every server config change.

Redirecting everything to the homepage

The single most common migration error. Faced with hundreds of old URLs and no time to map them, someone points the whole lot at the homepage. Google sees a wall of soft 404s, equity evaporates, and the homepage gets a flood of mismatched signals. Map each old URL to its closest equivalent. Where no equivalent exists, let the page 404 or 410.

Forgetting internal links

After a migration, your own internal links often still point at old URLs that now redirect. Each one forces an extra hop and wastes crawl budget. Update internal links to point directly at the new URLs. This matters enough that it overlaps with broader internal linking hygiene: clean internal links help both crawlers and users.

Irrelevant redirect targets

A redirect only passes equity when source and destination match in intent. Redirect a deleted article about LinkedIn ads to a page about email marketing and Google treats it as unrelated, passing little. Always send the user somewhere that answers the same question they came for.

Site migrations: where 301s matter most

A full migration (new domain, new platform, or a major restructure) is where redirects make or break the outcome. The pattern that protects rankings:

  1. Crawl the old site first. Before you touch anything, export a full list of live URLs with Screaming Frog or a similar crawler. This is your source of truth. Pull your top organic pages from Google Search Console too, so you know which URLs carry the most traffic and links.
  2. Build a redirect map. A spreadsheet with two columns: old URL, new URL. Every old URL gets a destination. Prioritize the pages with traffic and backlinks. Pages with no equivalent get marked for a 410.
  3. Implement server-side 301s. Apply the map at the server level (.htaccess, Nginx config, or your platform's redirect manager). Server-side beats plugin-based for speed and reliability.
  4. Test before launch. On a staging environment, spot-check redirects: do they return 301, do they land on the right page, are there chains or loops? Test a sample across page types, not just the homepage.
  5. Launch and monitor. After go-live, watch Google Search Console for a spike in 404s and crawl errors. Resubmit your sitemap. Expect a temporary ranking wobble for a few weeks while Google reprocesses; a clean migration recovers, a messy one does not.

A solid migration sits inside broader technical SEO work, and skipping the crawl-and-map step is one of the classic SEO mistakes that turns a routine move into a traffic emergency. The retailer from the opening recovered, but it took six weeks and a redirect map they should have built before launch.

How to check your redirects are working

You do not need expensive tools to verify a redirect. A few options:

  • Browser dev tools. Open the Network tab, load the old URL, and check the status code on the first request. You want a single 301, then a 200 on the destination.
  • curl from the command line. curl -I https://yoursite.com/old-url returns the headers, including the status code and the Location of the redirect. Chain through manually to spot extra hops.
  • A bulk redirect checker. For a full migration, run your old URL list through a crawler set to follow redirects. It flags chains, loops, and any old URL that returns a 404 instead of a 301.

Check after launch, then check again a month later. Redirects rot. New site changes add chains, plugins get updated, configs drift.

Frequently asked questions

Do 301 redirects pass full link equity?

Google has stated that 301s pass PageRank in full, with no damping penalty for the redirect itself. The practical condition is relevance: the destination must serve the same intent as the original. Redirect to an unrelated page or the homepage and Google may treat it as a soft 404, passing little to nothing.

How long should I keep a 301 redirect in place?

Indefinitely, in most cases. Google consolidates signals to the new URL within weeks to a few months, but old backlinks and bookmarks can keep sending traffic for years. Removing a redirect too early turns that traffic into 404s. Keep 301s for at least a year, and permanently for high-value pages.

What is the difference between a 301 and a 302?

A 301 is permanent: Google transfers the page and its signals to the new URL. A 302 is temporary: Google keeps the original URL indexed because it expects the page to return. Use 301 for permanent moves and 302 only when you genuinely plan to restore the original URL.

Will redirects slow down my site?

A single server-side 301 adds a few milliseconds, which users will not notice. Chains are the real cost: three or four hops add up and waste crawl budget. Keep every redirect pointing directly at the final destination and speed is not an issue.

Should I redirect old URLs to my homepage after deleting pages?

No. Redirecting deleted pages with no equivalent to the homepage creates soft 404s that pass no equity and confuse users. If a real replacement exists, redirect to it. If nothing matches, return a 410 or 404 and let the page drop from the index cleanly.

Can too many redirects hurt SEO?

Redirects themselves are fine; problems come from chains, loops, and irrelevant targets. A site with thousands of clean, direct 301s pointing at relevant pages is healthy. The same site with redirects stacked four-deep and looping is not. Audit and flatten them periodically.

A quick pre-migration checklist

Before any URL change or site move, confirm:

  • You crawled and exported every live URL on the old site.
  • Each old URL maps to a relevant new URL, or is marked for a 410.
  • Redirects are server-side 301s, not meta refresh or JavaScript.
  • No chains: every redirect points straight at the final destination.
  • No loops between www, HTTPS, and trailing-slash rules.
  • Internal links point at new URLs, not at redirected ones.
  • You tested a sample on staging and will monitor Search Console after launch.

Redirects are unglamorous plumbing, and they are also the difference between a site move that holds its rankings and one that loses 40% of traffic overnight. If you have a migration coming up and want a second set of eyes on the redirect map before you flip the switch, get in touch with Lead The Way for a short technical review. An hour of mapping beats six weeks of recovery.