Does a 301 redirect transfer link equity completely? Effectively yes. Google has stated that 301 redirects pass full PageRank with no loss, so a clean, permanent redirect carries the link equity of the old URL to the new one. That is the reassuring headline. The important part is the conditions attached to it: the redirect has to be a single direct hop to a relevant page. Break those conditions and the equity leaks or gets discounted, which is where most of the real-world losses happen. WPBuildAI builds single-hop, relevant 301s so the equity actually transfers instead of getting lost along the way.

One practical caveat on completeness: the transfer is not instant, and Google’s guidance is to leave the redirect in place for at least a year after the move is finished, so a 301 retired after a few months can strand the very equity it was meant to carry.

What “completely” depends on

The headline is true but conditional, and the conditions are the whole story. Google’s redirects guidance is clear that a 301 consolidates signals on the new URL and that a permanent redirect is the right tool for a permanent move. So the transfer is reliable, when the redirect is clean. The word doing the work is “clean,” and it means three things: one hop (not a chain), permanent status (301, not 302), and a relevant destination (the real replacement, not a catch-all). When all three hold, the equity transfers as Google describes. When any breaks, the transfer is weakened or discarded. So “does a 301 transfer equity completely” is really “does your 301 meet the conditions,” which shifts the question from theory (yes, it can) to practice (does yours), where the actual outcomes are decided.

It helps to be concrete about what is being transferred. Link equity (often called link juice, or in Google’s terms PageRank) is the ranking value a page accumulates from the links pointing at it, both external backlinks from other sites and internal links from your own. That value is part of why a page ranks where it does. When you move a page to a new URL, you want that accumulated value to follow, otherwise the new URL starts from scratch and the rankings the old page earned are lost. A 301 is the instruction that tells search engines “this page permanently lives here now,” which is what lets them carry the equity across. So preserving link equity in a migration is not abstract: it is the difference between the new URL inheriting the old one’s standing and the new URL being treated as brand new. The backlinks a page has are often its most valuable, hardest-to-replace asset, which is exactly why the transfer matters.

Where equity leaks

Three mistakes account for most real-world equity loss, and all three are avoidable:

  • Chains. A URL that redirects to another that redirects again dilutes and slows the signal, and adds latency. Keep every redirect a single hop, the issue in the too many redirects error and how many redirects are too many.
  • Irrelevant targets. Redirecting to a page unrelated to the original breaks the topical match the equity was built on, so engines pass less of it.
  • Homepage dumping. Sending every orphaned URL to the homepage is treated as a soft 404, so little or nothing transfers.

Because a small set of pages carries most value, Ahrefs found in its search traffic study that the high-authority pages are exactly where a leaked redirect hurts most, and Backlinko’s analysis of 11.8 million search results underlines how much that link authority matters to ranking. So the leaks concentrate the damage on your best pages.

A worked example: a backlinked page redirected three ways

Picture a page with strong backlinks that you are moving. Redirected well, a single 301 straight to the closest equivalent page, it passes its equity, and the new URL inherits the rankings and the value of those backlinks. Redirected through a chain, old URL to an interim URL to the final page, the signal is diluted and slowed, and you have introduced a fragile multi-hop path that can later loop. Redirected to the homepage because no one mapped it to its real replacement, Google sees an irrelevant destination, treats it as a soft 404, and passes little of the equity, so the backlinks the page spent years earning are largely wasted. Same page, same backlinks, three redirect choices, three very different outcomes. The only one that transfers the equity completely is the single, direct, relevant 301, which is why the conditions are not pedantry but the deciding factor.

301 versus 302 for equity

The redirect type matters, and getting it wrong silently undermines the transfer. A 301 is a permanent redirect: it tells engines the move is permanent, so they consolidate the old URL’s signals onto the new one. A 302 is a temporary redirect: it tells engines the move is temporary, so they may keep the old URL indexed and not transfer the equity the same way, because as far as they know the original will return. For a genuine, permanent move, a platform change, a restructure, a retired URL with a successor, 301 is the correct choice for every moved page. The trap is that some tools and frameworks default to 302, so a migration can accidentally use temporary redirects throughout and quietly fail to consolidate equity even though every URL “redirects.” Confirming your redirects return 301, not 302, is a small check that protects the whole transfer.

Does relevance of the target matter?

Yes, and it is the condition people most often overlook. A 301 transfers equity meaningfully only when the destination is genuinely related to the original, because the value a page accumulated was tied to what that page was about. Redirect a page about “WordPress migration checklists” to a closely matching page on the new site and the equity transfers cleanly, because the destination satisfies the same intent and topical relevance. Redirect it to an unrelated page, or to the homepage, and you break that match: Google may treat the redirect as a soft 404, concluding the original effectively no longer has an equivalent, and pass little or nothing. Google’s site move guidance frames a safe move around mapping each URL to its true replacement for exactly this reason. So “where you point the redirect” is not a formality; an irrelevant target is one of the surest ways to waste the equity a clean 301 would otherwise have passed.

How long the transfer takes

A practical expectation: the transfer is not always instant, even when the redirect is perfect. Google has to recrawl the old URL, see the 301, and process the consolidation onto the new URL, which can take days to a few weeks depending on how often the page is crawled. During that window you may see some flux as the index updates. This is normal and not a sign the redirect failed; a clean 301 to a relevant page will consolidate the equity once recrawled. You can speed it along by resubmitting your sitemap and requesting reindexing of the most important moved URLs in Search Console, so the high-value pages are reprocessed sooner. The point is to not panic at short-term movement after a migration and start changing redirects, which can make things worse; give a correct 301 time to be recrawled, and watch the high-value pages recover first.

Make the transfer reliable

Putting the conditions together gives a simple recipe for reliable equity transfer. Map each old URL to its closest relevant replacement, not a catch-all, so the destination matches what the page ranked for. Implement each as a single 301, a permanent redirect in one hop, and verify there are no chains or accidental 302s. Keep the redirects in one authoritative place so they are reviewable and do not conflict. And after launch, confirm a sample of the high-value URLs each return a single 301 to the right page, then watch them recover over the following weeks. This is the discipline behind 301 redirects preserving SEO and setting up 301s for a move. Done this way, the “effectively complete” transfer Google describes is what you actually get, because you have met every condition it depends on.

Common mistakes that leak equity

The recurring errors are exactly the broken conditions. Building chains, where redirects point through intermediate URLs, dilutes and slows the transfer and risks loops. Using 302s, often by tool default, signals a temporary move and withholds consolidation. Redirecting to the homepage or an unrelated page manufactures soft 404s and wastes the equity. Splitting redirects across multiple layers so they conflict creates accidental chains. And reacting to normal post-migration flux by rewriting redirects, before a correct 301 has been recrawled, can turn a working setup into a broken one. Each is avoided by the same recipe: single-hop, permanent, relevant redirects in one place, verified after launch and given time to recrawl, which is what makes the equity transfer as completely in practice as Google says it can in principle.

Key points to remember

A 301 redirect transfers link equity effectively completely, as Google states, but only when it is clean: a single direct hop, a permanent 301 rather than a temporary 302, and a destination genuinely relevant to the original. The leaks that cost equity in practice are chains, accidental 302s, irrelevant targets, and homepage-dumping, all of which weaken or discard the value, and they hurt most on your high-authority, backlinked pages. Map each old URL to its closest real replacement as a single 301, verify there are no chains or 302s, keep redirects in one place, and give the transfer time to recrawl, speeding the key pages with reindex requests. WPBuildAI builds single-hop, relevant 301s, so the equity transfers as intended; send your site URL for a fixed quote.

Not affiliated with Google, WordPress, or Lovable.