Do Redirects Pass Link Equity/PageRank?

Link equity (also called link juice or PageRank) is the ranking value that flows from one page to another through links. When a page with high authority links to your page, some of that authority transfers to you. The question that has consumed SEO professionals for over a decade is whether redirects transfer that same equity, or whether some of it is lost in transit.

The short answer: yes, redirects pass full link equity. But the history of how we got to this answer is complicated, and there are still scenarios where redirects can effectively waste link equity even though the mechanism itself works correctly. For the related question of whether redirects hurt rankings, see Do 301 Redirects Hurt SEO?.

A Brief History of PageRank and Links

Google's original ranking algorithm, PageRank, worked by treating links as votes. A link from page A to page B was a vote of confidence in page B. The more votes (links) a page received, the higher its PageRank. But not all votes were equal. A link from a high-PageRank page carried more weight than a link from a low-PageRank page.

The original PageRank formula, published by Larry Page and Sergey Brin in 1998, included a dampening factor:

PR(A) = (1-d) + d * (PR(T1)/C(T1) + PR(T2)/C(T2) + ... + PR(Tn)/C(Tn))

The dampening factor d was set to approximately 0.85, meaning that at each link, roughly 15% of the PageRank value was lost. This was a mathematical property of links, not redirects. But the SEO community would later apply this same logic to redirects.

Google no longer uses the original PageRank formula in its simple form. The modern ranking system uses hundreds of signals, and the concept of "link equity" is a simplification. But links remain an important ranking factor, and the flow of authority through links and redirects remains relevant.

The Pre-2016 Era: Redirects May Have Lost PageRank

In 2010, Matt Cutts, head of Google's webspam team, suggested that PageRank "dissipates" through a 301 redirect similarly to how it dissipates through a link. The SEO community interpreted this as confirmation that the ~15% dampening factor applied to redirects.

Whether this interpretation was accurate is debatable. Cutts may have been describing general behavior rather than confirming a specific percentage. But the practical effect was that the SEO industry treated every redirect as a 15% tax on link equity. This belief influenced decisions about site migrations, URL restructuring, and domain consolidation for years.

Some practitioners went further and claimed that 302 (temporary) redirects passed no PageRank at all, since they were not intended to be permanent signals. This led to widespread advice to never use 302 redirects if you cared about SEO.

The 2016 Change: Full PageRank Transfer

In July 2016, Gary Illyes of Google posted on Twitter/X: "30x redirects don't lose PageRank anymore."

This statement covered all 3xx redirect types: 301, 302, 303, 307, and 308. Every redirect type now passes full link equity to the destination URL.

Illyes did not specify when this change took effect. It may have been in place well before the announcement. Google's algorithm updates are often retroactive in this way: a change is made quietly, and the public confirmation comes later.

Since 2016, Google's documentation and public statements have been consistent. John Mueller has stated multiple times that redirects do not lose PageRank. The Google Search Central documentation on redirects makes no mention of dampening or percentage loss.

301 vs 302: Does the Type Matter for Equity?

After the 2016 announcement, the answer is no. Both 301 and 302 redirects pass the same amount of link equity. The difference between them is about indexing behavior, not equity transfer.

With a 301 (Permanent) redirect, Google drops the old URL from its index and shows the new URL in search results. The link equity flows from the old URL to the new one.

With a 302 (Temporary) redirect, Google may keep the old URL in its index, since the redirect signals that the old URL might come back. The link equity still flows to the destination, but Google's choice about which URL to show in search results may differ.

In practice, if you are permanently moving a page and want search engines to recognize the new URL as the canonical version, use a 301. If the move is genuinely temporary, use a 302. But do not choose between them based on link equity concerns, because the equity transfer is identical.

For the full comparison of redirect types, see 301 vs 302 Redirects.

Redirect Chains and Equity

A single redirect passes full link equity. But what about a chain of redirects?

Page A --301--> Page B --301--> Page C --301--> Page D

In this chain, link equity from external links pointing to Page A needs to travel through three hops to reach Page D. Google has said that all 3xx redirects pass full equity, which implies that each hop in the chain transfers 100% of the value it receives. In theory, the full equity reaches Page D.

In practice, chains introduce risks that can indirectly reduce the equity that reaches the final destination:

Crawl abandonment. Google follows up to 10 redirect hops. If a chain exceeds 10 hops, Googlebot gives up and no equity reaches the destination. This is rare but possible on sites with years of accumulated migrations.

Broken intermediate links. If any server in the chain goes down, responds with an error, or is decommissioned, the chain breaks. The equity stops flowing at the broken link. A five-hop chain has five points of failure.

Crawl budget consumption. Each hop in a chain counts as a separate crawl request. On large sites, long chains reduce the number of actual pages Google can crawl within its budget.

Slow discovery. When Google encounters a new redirect, it follows the chain and discovers the final destination. But re-crawling the chain takes time, and if the chain changes (a new hop is added or a destination changes), Google may take weeks to discover the update.

The best practice is to flatten chains to a single hop. Point every old URL directly to the current final destination. This eliminates the fragility and crawl budget waste of multi-hop chains.

For detection and fixing, see How to Find Redirect Chains.

What About JavaScript and Meta Refresh Redirects?

Server-side redirects (301, 302, 307, 308) pass link equity. But what about client-side redirects?

JavaScript redirects (using window.location or similar) are not HTTP redirects. Google can execute JavaScript and may follow the redirect, but Google has stated that server-side redirects are the recommended method. JavaScript redirects are slower (the browser must download, parse, and execute the JavaScript before redirecting), and not all search engine crawlers execute JavaScript. Link equity transfer through JavaScript redirects is unreliable.

Meta refresh redirects (<meta http-equiv="refresh" content="0;url=...">) are also client-side. Google generally follows them, but they are not as clear a signal as a server-side redirect. For short delays (0 seconds), Google may treat them similarly to server-side redirects. For longer delays (5 seconds or more), Google may not treat them as redirects at all.

For both JavaScript and meta refresh redirects, server-side 301 redirects are the safer and more reliable choice for preserving link equity. See Redirect Methods Compared for the full comparison.

External Links and Equity After a Redirect

When an external site links to your old URL and that URL has a 301 redirect to a new page, the link equity flows through the redirect to the new page. The external site does not need to update their link. The redirect handles the equity transfer automatically.

This is one of the primary reasons 301 redirects exist: to preserve the value of external links when URLs change. Without the redirect, external links pointing to the old URL would result in 404 errors, and the equity from those links would be lost entirely.

However, over very long time periods, you should still try to get high-value external links updated to point to the new URL directly. This eliminates the redirect dependency and ensures the equity flows even if your redirect configuration changes in the future.

When Redirects Waste Equity

The redirect mechanism passes full equity, but implementation mistakes can waste it:

Redirecting to irrelevant pages. If a page about "best running shoes" is redirected to the homepage, the equity passes to the homepage. But the homepage is not relevant to the "best running shoes" query, so the equity does not help your rankings for that topic. The equity is technically transferred but practically wasted.

Not redirecting at all. Returning a 404 for a page that has external backlinks means all of that equity is lost. A redirect to any relevant page is better than a 404.

Using noindex on the destination. If the redirect destination has a noindex meta tag, the page is removed from Google's index. The link equity flowing to it serves no ranking purpose.

Redirecting, then deleting the destination. Setting up a redirect and later removing the destination page (or its content) means the equity flows to a page that no longer exists or no longer provides value.

Measuring Equity Transfer

There is no direct way to measure PageRank or link equity. Google stopped publishing PageRank scores in 2016. Third-party metrics like Moz's Domain Authority, Ahrefs' Domain Rating, and Majestic's Trust Flow are approximations that use their own crawl data and formulas.

After implementing a redirect, you can track its effectiveness by monitoring:

• Search Console performance reports. Watch impressions and clicks for the destination URL's target keywords. Equity transfer should gradually improve rankings.
• Index coverage. Verify that Google has dropped the old URL and is showing the new URL in search results.
• Third-party link metrics. Check that link analysis tools recognize the redirect and attribute the old URL's backlinks to the new URL.

Allow at least four to eight weeks after implementing redirects before drawing conclusions. Google needs time to re-crawl the old URLs, follow the redirects, and re-evaluate the destination pages.

References

1. Gary Illyes, Google, "30x redirects don't lose PageRank anymore," Twitter/X, July 2016.
2. Google, "Redirects and Google Search," Google Search Central, 2024. https://developers.google.com/search/docs/crawling-indexing/301-redirects
3. Sergey Brin and Lawrence Page, "The Anatomy of a Large-Scale Hypertextual Web Search Engine," Stanford University, 1998. http://infolab.stanford.edu/~backrub/google.html
4. IETF, "RFC 9110 - HTTP Semantics, Section 15.4: Redirection 3xx," June 2022. https://httpwg.org/specs/rfc9110.html#status.3xx