How to 301 Redirect an Old Domain to Preserve Its Authority
A step-by-step operator's guide to using a 301 redirect to move an old domain to a new domain without bleeding authority, rankings, or link equity.
Every acquired domain carries a history: backlinks, referring domains, aged trust signals, and whatever ranking equity accumulated over its life. When you retire that name—or fold it into a stronger brand—the question that decides your ROI is simple. Does the authority come with it, or does it evaporate?
The mechanism for carrying it forward is the permanent redirect. Done correctly, a 301 redirect from an old domain to a new domain preserves authority, consolidates link equity, and protects the rankings you paid for. Done sloppily, it quietly torches the exact asset that justified the acquisition. This guide walks through the process the way an operator should run it—deliberately, with a plan for measurement.
What a 301 Actually Does for Domain Authority
A 301 is an HTTP status code that tells browsers and search engines a resource has moved permanently to a new location. Unlike a temporary redirect, it signals intent: this is the new home, index it, and pass the accumulated signals here.
Search engines interpret that permanence as a mandate to transfer ranking signals—link equity, relevance, and trust—from the old URL to the new one. That is the entire strategic value. You are not just forwarding traffic; you are migrating the authority that made the old domain worth owning in the first place.
Two nuances matter before you touch anything:
- Redirects are per-URL, not just per-domain. Authority lives on individual pages. A homepage-to-homepage redirect does not automatically rescue the equity sitting on deep pages.
- Equity transfer is high but not perfect. The consensus is that most link equity passes through a clean 301, but expecting 100% recovery sets you up for disappointment. We cover the mechanics in depth in How Much Link Equity Does a 301 Redirect Actually Pass?
If you're still deciding between a 301 and a 302 for this move, resolve that first—it's not a stylistic choice. See 301 vs 302 Redirects: Which One Protects Domain Authority? Use a 302 for a permanent move and you may keep the old domain indexed indefinitely, splitting the authority you were trying to consolidate.
Before You Redirect: Map the Asset
The biggest mistakes happen because operators skip the inventory. You cannot preserve what you haven't measured.
1. Audit the old domain's backlink profile
Pull the full referring-domain list using a reputable backlink tool. Identify which pages hold the most valuable links. These are the URLs whose equity you most need to protect—and they dictate your redirect map.
2. Crawl and export every indexed URL
Run a crawl of the old domain and cross-reference it against the pages search engines have actually indexed. You need a complete list of live URLs that either rank, receive traffic, or attract links.
3. Build a URL-to-URL redirect map
This is the core deliverable. Each valuable old URL maps to the most topically relevant page on the new domain. A blog post about domain valuation should point to the equivalent article on the new site—not the homepage.
The lazy pattern—redirecting every old URL to the new homepage—is the fastest way to lose the authority you're trying to keep. Search engines increasingly treat homepage catch-all redirects as soft 404s, passing little to no equity.
How to 301 Redirect an Old Domain to a New Domain, Step by Step
- Stand up the destination first. Every mapped target URL on the new domain must exist, return a 200 status, and be live before you flip a single redirect. Redirecting to pages that don't exist yet creates chains of errors.
- Implement the redirects at the server level. For most operators this means editing the .htaccess file on Apache, adding server blocks in Nginx, or using redirect rules at your CDN or host. Plugin-based redirects work for smaller sites but add latency and a point of failure. Match old URLs to new ones exactly per your map.
- Preserve the URL structure where possible. If the new domain mirrors the old path structure, you can use a pattern rule to redirect an entire directory cleanly. Where structures differ, rely on your explicit one-to-one map.
- Force HTTPS and canonical host. Consolidate www vs non-www and http vs https into a single canonical version on the destination so equity doesn't fragment across variants.
- Keep the old domain registered and paid. The redirect only works while you own the old domain and its DNS resolves. Let it lapse and every inbound link points to a dead end. Treat renewal as a permanent line item.
- Update internal references you control. Where you can edit links pointing to the old domain—social profiles, directory listings, partner sites—update them directly. A direct link is always cleaner than a redirected one.
For consolidating two active properties rather than retiring one outright, the sequencing gets more involved. Our Merging Two Domains: A 301 Redirect Consolidation Playbook covers that scenario end to end.
Verify the Migration
Once redirects are live, confirm they behave as intended:
- Test status codes. Use a header-checking tool to confirm each key URL returns a single 301—not a 302, not a chain, not a 200 masking the old page.
- Eliminate redirect chains and loops. A URL should reach its destination in one hop. Chains dilute equity and slow crawling. Loops break the page entirely.
- Submit the change of address. In Google Search Console, use the change-of-address tool when moving to a new domain, and submit an updated sitemap for the new property. See the Google Search Central site-move documentation for the current process.
- Monitor both properties. Watch indexing on the new domain climb and the old domain's indexed pages fall to zero over the following weeks.
Common Failure Points
Most authority loss during a domain move traces back to a short list of avoidable errors—wrong redirect type, homepage catch-alls, broken chains, dropped registration, or targeting pages that no longer exist. We catalog them in 7 Common 301 Redirect Mistakes That Kill Domain Authority. Read it before, not after.
Set Realistic Timelines
Authority transfer is not instant. Search engines must recrawl the old URLs, register the 301s, and reassign signals to the new destinations. Expect movement over weeks, with fuller consolidation across a few months depending on crawl frequency and site size. Resist the urge to change course mid-migration; premature panic edits do more damage than patience. Our breakdown of how long a 301 redirect takes to transfer authority sets expectations by scenario.
The Strategic Takeaway
A domain's authority is an asset you can move, but only if you treat the migration as an operation rather than a checkbox. Map the equity, redirect URL to URL, verify with real tools, and hold the line while search engines catch up. Done well, the 301 is one of the highest-leverage moves in digital real estate strategy—it lets you upgrade to a stronger name without abandoning years of accumulated trust.
If you're evaluating a name to migrate onto—or weighing an acquisition where inherited authority is part of the thesis—browse the curated PixelWorks Domains inventory, or reach out about a specific target. We're happy to talk through the strategic fit before you commit capital, whether or not the name is ours.