How to Redirect a Domain for Link Equity: A Step-by-Step Guide

To redirect a domain for link equity, point every old URL at its matching new URL with a permanent 301 redirect, and keep those redirects live for at least 1 year.
To redirect a domain for link equity, point every old URL at its matching new URL with a permanent 301 redirect, and keep those redirects live for at least 1 year. A domain redirect moves the ranking value of old backlinks to the new domain, but only when each redirect lands on the same topic.
Key takeaways
- Google states that 301 and other permanent redirects cause no loss in PageRank (Google Search Central, 2026).
- Ahrefs found 66.5% of links to 2,062,173 sampled sites had rotted since January 2013 (Ahrefs, 2022).
- Keep every redirect live for at least 1 year so Google can transfer all signals (Google Search Central, 2026).
- Googlebot follows up to 10 hops, but Google advises chains of 3 or fewer (Google Search Central, 2026).
- Pew found 38% of pages from 2013 were gone a decade later (Pew Research Center, 2024).
- A medium site can take a few weeks or more to show new URLs (Google Search Central, 2026).
What redirecting a domain means
Link equity is the ranking value a link passes from one page to another. Redirecting a domain means sending every request for the old domain to the new domain. A domain redirect aims to carry that value across, so the new domain keeps the standing the old one earned.
A domain redirect is not one rule. It is a set of rules, one for each old URL, that names its new home. A single rule that sends all old pages to the new home page is a weak move. Google advises mapping each old URL to its matching new URL instead.
Domain redirects apply in three common cases, and each case needs the same care with mapping and testing.
- Rebrand: the site moves to a new name.
- Merger: one site folds into another.
- Cleanup: HTTP moves to HTTPS, or www moves to non-www.
Why link equity is at risk when a domain changes
Link equity is at risk because links point at addresses, not at brands. When a domain changes and an old address returns a 404 error, the links that pointed there stop passing value. Redirected links pass link equity only when the redirect leads to a matching page.
The scale of the loss is large. Ahrefs found in its 2022 study that 66.5% of links to 2,062,173 sampled websites had rotted since January 2013. Another 6.45% had temporary errors, and the total share counted as lost reached 74.5%. Most losses came from dropped pages at 47.7% and removed links at 34.2%.
Pew Research Center found the same decay in pages. Its 2024 study of just under 1 million pages found 25% of pages from 2013 to 2023 were gone as of October 2023. Pages from 2013 fared worst at 38% gone, while 8% of pages from 2023 were already gone within a year.
A redirect is the fix for a moved page. Ahrefs notes that old URLs with links from other sites lose their value when they are not redirected to current pages. A mapped 301 gives each of those links a live destination, so the value keeps flowing instead of dying with the old address.
Which redirect type to use
Use a permanent redirect for a domain move. A 301 tells browsers and search engines that the page has moved for good, and Google treats it as a strong signal that the new URL should be the canonical one. A 301 redirect is the default choice when the old domain will not come back.
Google splits redirects into two groups. Permanent redirects, 301 and 308, show the new target in search results. Temporary redirects, 302, 303, and 307, keep showing the source page. Google recommends a permanent server-side redirect whenever possible for a permanent move.
The old fear was that a 301 leaked value. In 2013, Google's Matt Cutts said the PageRank lost through a 301 matched the amount lost through a normal link. Then in July 2016, Google's Gary Illyes said: "30x redirects don't lose PageRank anymore." Search Engine Land reported the statement on 27 July 2016.
A redirect is not the same as a canonical tag. A 301 moves visitors and search engines to the new URL, while a canonical tag only asks search engines to credit the main version. A 301 redirect versus a canonical tag is the right comparison when both URLs must stay live.
| Code | Search shows | Use it for |
|---|---|---|
| 301 | New URL | Permanent move |
| 308 | New URL | Permanent move |
| 302 | Old URL | Short-term move |
| 307 | Old URL | Short-term move |
Pick 301 unless the move is truly short-term. A 302 left on a permanent move keeps the old URL in results longer than you want.
How to redirect a domain for link equity
Follow these steps in order. Each step builds on the last, and skipping the mapping step is the error that costs the most equity. Work on a copy of the site first when you can, and test every redirect before you point real traffic at the new domain.
Step 1: List every old URL that earns links or traffic
Start with the pages that matter most. Pull your sitemap, your server logs, and your analytics to list URLs with visits. Then pull the links report in Search Console to find pages with external links. These lists form the base of your map.
Include images, files, and other linked assets, not just pages. Google advises including video, image, JavaScript, and CSS URLs in the move plan. A linked PDF that returns a 404 loses its links just like a page does.
Step 2: Map each old URL to its matching new URL
Build a simple table with two columns: old URL and new URL. Match each old page to the new page on the same topic, even when the path changes. Keeping link equity when changing URLs starts with this map, not with the redirect rules.
Do not send all old URLs to the home page. Google warns against a blanket redirect to the home page, and says a page-to-page redirect is more work but gives users a consistent experience. When no matching page exists, let the old URL return a 404 or 410 instead.
Step 3: Set up the new domain and check it
Point the new domain at the new site and install its TLS certificate before launch. Verify both the old and new sites in Search Console, including www and non-www variants. Remove any noindex tags or robots blocks left over from development.
Check the new domain for leftovers from a past owner. Google advises checking for manual actions and old URL removals on a newly bought domain. If a manual action is in place, fix the listed problems and file a reconsideration request before the move.
Step 4: Write the redirect rules
Use server-side redirects when you can. Google recommends a permanent server-side redirect whenever possible, and notes that server-side rules have the best chance of being read correctly. For a simple domain change, one wildcard rule can send every old path to the same path on the new domain.
On Apache, the domain rule looks like this:
RewriteEngine on
RewriteCond %{HTTP_HOST} ^oldsite.com [NC,OR]
RewriteCond %{HTTP_HOST} ^www.oldsite.com [NC]
RewriteRule ^(.*)$ https://newsite.com/$1 [L,R=301,NC]
On WordPress, the free Redirection plugin adds 301 redirects without editing server files. On Cloudflare, Bulk Redirects take a CSV list of old and new URLs and turn it on with one rule. Pick the method that matches your host, and keep the rules in one place.
Step 5: Submit the Change of Address and the new sitemap
If the domain name itself changes, submit a Change of Address in Search Console for the old site. You need it only for a domain or subdomain move, not for HTTP to HTTPS, www to non-www, or path moves on the same domain. Then submit the new sitemap so Google learns the new URLs.
Keep the old sitemap out of the new setup. Remove 301 URLs from sitemaps, since pages with a 301 status no longer exist as content. Your sitemap should list only live 200 pages on the new domain.
Step 6: Test every redirect before launch
Test in bulk, not by hand. Use the URL Inspection Tool in Search Console for single URLs, and a crawler or a script for large lists. Check that each old URL returns a 301, lands on the right new page, and finishes in one hop.
Fix chains, loops, and broken targets now. A chain sends Page 1 to Page 2 to Page 3 instead of straight to Page 3. A loop sends a URL back to a page already in its own chain. A broken redirect lands on a 404, which strands both users and crawlers.
Step 7: Keep the redirects live and update your links
Keep the redirects for as long as possible, generally at least 1 year. Google says this span lets it transfer all signals to the new URLs, including recrawling and reassigning links from other sites. From the user side, consider keeping them indefinitely.
Update links at the source where you can. Change internal links to point at the new URLs, and ask the sites that link to you most to update their links. Redirects slow users down, so direct links are better than a permanent detour.
Keep the old domain registered. Google's move guide from 2008 says to retain control of the old domain for at least 180 days. The current guide goes further on redirects, asking for at least 1 year, so treat 180 days as the floor for the domain itself.
Tools and time needed
You need the old URL list, the new site, and access to the server or DNS settings, as our site migration guide explains.
- Search Console: free, for the Change of Address and sitemaps.
- Ahrefs Webmaster Tools: free, for finding linked old URLs.
- Cloudflare Bulk Redirects: list upload for large moves.
- A status checker: tests up to 100 URLs at a time.
A paid crawler is optional. Small sites can finish the whole job with free tools, since the work is mapping and testing, not buying software. Keep the old domain registered and the redirects live, since letting the domain lapse breaks every redirect at once.
A small site moves faster than a large one, which needs staged moves by section. Google says a medium site can take a few weeks or more for new URLs to show, and larger sites take longer, so plan checks for at least a month after launch.
Common mistakes
Most failed domain redirects come from a short list of errors. Each one is easy to make under time pressure, and each one costs equity that is hard to win back. Check for all of them before launch day.
- Blanket redirect: every old URL points at the home page instead of its match.
- Temporary redirect: a 302 stays live on a permanent move.
- Redirect chain: old URLs hop through two or more stops.
- Dropped redirects: rules are removed before Google finishes the move.
- Stale sitemap: old 301 URLs stay listed as live pages.
- Untested launch: no bulk check catches loops or 404 targets.
A redirect to a deleted page is another silent failure. A 301 that lands on a 404 strands the link value and the visitor. Test the final target of each rule, not just the first hop.
How to measure results
Watch Search Console first. The Index Coverage report should show old indexed URLs falling and new indexed URLs rising. The search queries report should start showing the new URLs earning impressions and clicks. A backlink audit helps you confirm the links behind the move.
Compare traffic on both sites. Old site traffic should fall while new site traffic rises, and server logs should show Googlebot crawling the new URLs. Expect a dip first: Google warns of temporary ranking fluctuation while it recrawls and reindexes the site.
Recheck the redirect list after 30, 90, and 365 days. Look for rules that still get hits, since a live redirect with steady traffic should stay in place. Check the linked pages too: Ahrefs found 5.99% of lost links were lost because the linking page itself was redirected.
Judge success by indexed new URLs and steady clicks, not by the first week. A move counts as done when Googlebot has visited every URL on the old and new site at least once. Until then, keep watching and keep the redirects live.
Frequently Asked Questions
Does a 301 redirect pass all link equity?
A 301 passes the ranking value to the new URL, and Google states that permanent redirects cause no loss in PageRank. The old idea of a fixed 15% loss came from early PageRank math and was retired in 2016. What matters now is the match: the new page must cover the same topic as the old one.
How long should I keep domain redirects in place?
Keep them for at least 1 year, and longer when they still get traffic. Google advises keeping redirects for as long as possible so it can transfer all signals to the new URLs. Check server logs before removing any rule: a redirect that still receives hits should stay live.
Can I redirect a whole domain with one rule?
Yes, when the path structure stays the same. A single wildcard rule can send each old path to the same path on the new domain. When paths change, build a map instead: each old URL needs its own line pointing at its matching new page.
Do I need a Change of Address for every domain redirect?
No. You need it only when the domain or subdomain itself changes, such as a move from example.com to example.net. You do not need it for HTTP to HTTPS, for www to non-www, or for path moves on the same domain. Submit it only after the redirects are live.
How long does a domain redirect take to work?
Google gives no fixed time. Its guide says a medium site can take a few weeks or more for new URLs to show, and larger sites take longer. The speed depends on the number of URLs and your server speed, so expect movement in weeks rather than days.
Sources
- Google Search Central: Site Moves and Migrations (2026)
- Google Search Central: Redirects and Google Search (accessed November 2026)
- Ahrefs: 301 Redirects Explained (accessed November 2026)
- Search Engine Land: No PageRank Dilution From 30x Redirects (2016)
- Ahrefs: At Least 66.5% of Links to Sites Are Dead (2022)
- Pew Research Center: When Online Content Disappears (2024)
- Cloudflare: Create Bulk Redirects in the Dashboard (2026)
If you are moving to a new domain and want to know whether the links will follow, see whether backlinks transfer to a new domain.
The BacklinkPrice Team researches backlink prices, publisher sites and link building tools. We check prices and plans against each provider's own pages and date them, so you know how current the numbers are.
More from BacklinkPrice TeamRelated guides





