Most 301 redirect damage comes from four avoidable mistakes: sending old pages to the homepage, stacking long redirect chains, retiring redirects too early, and using a temporary (302) redirect for a permanent move. Each one leaks the ranking signals Google would otherwise pass from your old URLs to your new ones, and the loss usually surfaces weeks later as a quiet drop in organic traffic.
The short version
- A 301 tells Google a move is permanent and consolidates ranking signals onto the new URL. A 302 says temporary, so Google keeps the old URL indexed.
- Redirecting a batch of old pages to your homepage reads as a soft 404, so those pages lose their rankings instead of passing them on.
- Redirect chains waste crawl budget and dilute signals. Point every old URL straight at its final destination in one hop.
- Google recommends keeping redirects in place for at least a year. Pull them early and you throw away the equity you just migrated.
- Timing matters. A botched redirect before Q4 costs you traffic during the highest-intent giving weeks of the year.
Why this lands hardest in Q4
The worst time to discover a redirect mistake is the week your year-end campaign goes live.
Nonprofits spin up new pages this time of year: a fresh year-end landing page, a refreshed donate page, a campaign microsite, a rebrand that finally ships before the December push. Every one of those involves retiring or moving a URL that already ranks. GivingTuesday falls on December 1 this year, and the organic traffic that feeds it builds through October and November. If a redirect quietly drops a page that ranked for a term like your city plus food bank, you lose that visibility in the exact window it matters most. I treat any redirect work between now and mid-November as change-frozen by default: map it, test it, ship it early, and then leave it alone through the campaign.
Mistake 1: Redirecting old pages to the homepage
The single most expensive redirect mistake is pointing a pile of retired URLs at your homepage.
It feels tidy. The old program pages, last year's campaign landing pages, and deprecated blog posts all resolve to a live URL, so nothing throws a 404. But Google's own guidance is explicit that redirecting many URLs to an irrelevant destination, like the homepage, is treated as a soft 404, which means the redirect passes almost none of the original page's ranking signals. You have effectively deleted those pages from search. The fix is a one-to-one map: each old URL redirects to its closest equivalent new page, and only genuinely orphaned URLs with no equivalent are allowed to return a 404 or 410. When I score URLs for a migration, I rank them by organic value first, so the highest-traffic pages get a real destination instead of a homepage catch-all.
Mistake 2: Building redirect chains
Redirect chains are the silent tax on a migration that nobody notices until crawl stats slip.
A chain is when URL A redirects to B, which redirects to C, which finally redirects to D. They accumulate naturally: an http-to-https rule, then a www rule, then a trailing-slash rule, then the actual page move, each added by a different person at a different time. Googlebot follows a limited number of hops (Google documents up to 10) before it gives up and treats the URL as an error, and every extra hop slows crawling and can dilute the signals you are trying to consolidate. Users feel it too, as a slower redirect on mobile. Flatten every chain so the original URL points directly at the final destination in one hop. Audit for this after any protocol or domain change, because chains almost always get created by stacking rules rather than replacing them.
Mistake 3: Using a 302 when you mean a 301
A 302 tells Google the move is temporary, so it keeps the old URL in the index and holds the signals there.
301 and 308 are permanent. 302 and 307 are temporary. For a permanent move you want a permanent, server-side redirect, because Google treats a 301 as a strong signal that the new URL is the canonical one and consolidates ranking signals onto it. A 302 does the opposite: it keeps the old URL as the canonical, which is exactly wrong when you have retired that page. This mistake hides easily, because a 302 looks identical to a visitor. It only shows up in the crawl. The most common cause I see is a platform default: some CMS and hosting setups issue a 302 unless you explicitly configure a permanent redirect. Check the actual status code with a header check or a crawler, not the label in the plugin.
What a clean redirect map looks like in practice
A redirect map is a spreadsheet, not a server config, and it gets built before anyone touches the CMS.
When I ran the consolidation for a state association that was folding two legacy brand sites into one, we started with a full crawl of both old sites, exported every indexed URL, and matched each one to its destination on the new site by hand. High-value pages, the ones pulling organic traffic and inbound links, got individual attention. Low-value near-duplicates were grouped. Anything with no real home was flagged for a deliberate 410 rather than a lazy homepage redirect. We shipped the 301s server-side in one batch, verified the status codes with a crawler before launch, and kept a monitoring view on the highest-traffic old URLs for the first month. Rankings held on the priority pages and recovered on the rest within a few weeks. The spreadsheet did the work. The server config just executed it. If you are planning a move, my replatform checklist walks through the sequencing.
Mistake 4: Retiring redirects too soon
Redirects are not a launch task you delete once traffic looks stable.
Google's guidance on site moves is to keep redirects in place for at least a year, and Google's search team has said the same publicly: leave them live for at least a year so Google has time to fully transfer signals and update its index, and so inbound links and bookmarks pointing at the old URLs keep working. Organizations get burned here because a redirect rule gets swept up in a later cleanup, a hosting migration, or a plugin change, and nobody connects the traffic dip to the removed redirect. Document your redirects as infrastructure. Put a reminder on the calendar a year out, and even then, keep any redirect that still gets traffic. There is no upside to removing a working redirect that costs you nothing.
What this does not cover
This covers the redirect mistakes that cost the most organic traffic in a standard site move or consolidation. It leaves out a few adjacent problems worth naming so you do not assume they are solved. International sites, where hreflang and per-language redirects interact, are a separate and more involved workstream. Client-side redirects in single-page apps, where you generally want the redirect handled at the edge or on the server rather than in the browser, need their own handling. And analytics or campaign tracking parameters, which you should decide to preserve or intentionally strip, are a distinct decision from the redirect map itself. If any of those are in scope for your project, treat each as its own task rather than folding it into the redirect rules.
Frequently asked questions
Does a 301 redirect pass all of my SEO value to the new page?
A 301 consolidates ranking signals onto the destination URL and Google treats it as a strong canonical signal, so the large majority of the value transfers. It is not instant. Google has to recrawl the old and new URLs and process the change, which can take days to weeks depending on how often those pages get crawled.
Is a 301 or a 302 better for a permanent move?
A 301. Use it for anything permanent. Reserve a 302 or 307 for genuinely temporary situations, like a page down for maintenance or a short-term promotional redirect, where you want to keep the original URL indexed.
How long should I keep redirects in place?
At least a year, per Google's site move guidance, and longer for any old URL that still receives traffic or holds inbound links. Treat removing a redirect as a deliberate decision, not routine cleanup.
Can I just redirect my old site to the new homepage?
No. Redirecting many URLs to the homepage is treated as a soft 404 and passes almost none of the original ranking signals. Map each old URL to its closest equivalent page instead.
How do I check what redirect type my site is actually using?
Look at the HTTP response header for the URL, or run a crawler that reports status codes. Do not trust the label in a CMS or plugin, since many platforms issue a 302 by default unless you configure a permanent redirect.
If you are consolidating sites or launching year-end campaign pages, I can audit your redirect map before it ships: flag the chains and homepage catch-alls, confirm every high-value URL lands where it should, and check the actual status codes rather than the labels. Book a 20-minute redirect review and I will walk you through what I find.