301 SEO
Stop redirecting old URLs to the homepage. I lost 60% of organic traffic that way. Map each URL to the closest relevant page instead.
What I’d do first
- Map every old URL to its closest equivalent page, never the homepage.
- Update all internal links to point directly to the final URLs to avoid redirect chains.
- Clean up your XML sitemap so it lists only final URLs.
- Use a crawler to check for redirect loops and chains quarterly.
- Use 302 for temporary moves and 301 for permanent ones.
The path I'd take
I start with a full audit of every URL involved. Export current URLs, traffic, backlinks, and anchor text. I use a crawler like Screaming Frog to find all current redirects and orphan pages. Then I map each old URL to the closest equivalent new URL. For example, if I'm moving /blog/seo-tips to /resources/seo-tips, I keep the same path structure but redirect if the slug changed. If content was merged, I redirect to the consolidated page. I avoid redirecting to the homepage unless the page has no equivalent and no traffic or backlinks. I implement 301s via server config (Nginx or Apache) rather than plugins where possible; plugins can be slower and harder to debug. After implementing, I manually test a sample of redirects using curl to check the status code. I also update my [technical SEO](/technical-seo/) crawl to verify no chains. Finally, I submit the updated sitemap with only final URLs.
I always update internal links pointing to old URLs. I use a script to find all internal links in my CMS and replace them. This reduces redirect load and passes link equity directly. I also check external backlinks via Google Search Console; I can't change them but I can ensure the redirect is solid.
One edge case: if a page has been deleted and has no equivalent, I redirect to a parent category page, not the homepage. That preserves topical relevance. I also consider [canonical tags](/canonical-tag/) if I'm consolidating multiple pages into one: the 301 is the signal, but a self-referencing canonical on the target helps.
Watch-outs
Common mistake: redirecting everything to the homepage. I did that and lost 60% traffic. Always map URL-by-URL, even for low-traffic pages. Another: creating redirect chains. A redirect to B, B to C looks fine, but Google may stop at B if B takes too long. Worse, loops (A to B to A) cause crawl errors. I check for chains quarterly with a crawler and flatten them.
Forgetting internal links is another: if your own site links to old URLs, you're wasting crawl budget and user experience. Update them as soon as the redirects are live. Similarly, XML sitemaps should list only final URLs; old URLs waste crawl budget. I also watch for mixed signal: using a 301 for a temporary promotion. If you plan to revert, use 302. Google treats 301 as permanent; link equity may not be passed back if you revert.
Also watch for relative vs absolute URLs in redirects. Some CMS plugins create relative redirects that break when moving domains. And be careful with [duplicate content](/duplicate-content/): if you redirect but keep the old URL live, you create duplicates. Use a canonical or remove the old page.
Another watch-out: HTTPS migrations. If you redirect HTTP to HTTPS, ensure all internal links use HTTPS, and use HSTS. A [SEO audit](/seo-audit/) will catch mixed content issues.
What I got wrong
My biggest mistake: redirecting a blog section with 200 posts to the homepage. I thought it looked cleaner. I lost 60% of organic traffic overnight. Recovering took weeks and involved undoing redirects, mapping each post to new relevant pages, and rebuilding backlinks. Now I never consolidate unless the content is truly gone.
Another mistake: ignoring redirect chains from a CMS plugin. I had a plugin that created a redirect for every URL change. After a site restructure, I had A->B->C->D. Google was not reaching D. I only noticed when traffic dropped. Now I disable plugins that auto-create redirects and I manually audit before migration.
I also used a 301 for a seasonal promotion, planning to revert. When I reverted, the old page didn't regain its rankings because Google considered the 301 permanent. Now I use 302 for anything temporary.
And I forgot to update internal links after a migration. My own site was calling the old URLs for months, causing redirects on every page load. This slowed page load times and wasted crawl budget. I fixed it by running a database search-and-replace. After that, load time improved and [website structure](/website-structure/) became cleaner. I also neglected to check backlinks before redirecting. Some high-value backlinks pointed to a page I redirected to a less relevant page. I should have mapped those manually.
Next step
Quick answers
Should I use a 301 or a 302 for an A/B test?
Use a 302 redirect. A 301 tells search engines the move is permanent, so they may transfer link equity and index the target URL. For A/B testing, you want temporary redirection so the original URL stays canonical and you can revert without losing rankings.
What happens if I redirect a page that has zero backlinks and traffic?
It matters less but still avoid redirecting to the homepage if there's a relevant category. Redirecting to a closely related page helps users and can pass topical relevance. If the page is truly dead, a 404 may be better than a misleading redirect.
How long does it take for a 301 redirect to pass link equity?
Google typically transfers link equity in the next crawl cycle after discovering the redirect. For high-authority sites, it can be days. For new sites, it may take longer. I've seen it take up to three weeks in some cases.
Can I use a 301 to redirect a page to a different domain?
Yes, it's common during domain migrations. Google passes link equity to the new domain. Ensure you update your sitemap, request indexing of new URLs, and keep the old domain live with redirects for at least six months to give crawlers time.
Sources
Primary documentation is linked directly. Anything commercial is marked nofollow.
- Google Search Central — Primary source for Google's guidance on redirects, crawling, and indexing.
- Moz - Redirects — Widely cited reference explaining 301 vs 302 and common redirect use cases.
- SEMrush - 301 Redirects — Practical guidance on implementation including internal links and sitemaps.
Notes from Callum Bennett.