How does PageRank actually get passed through redirects?

Does PageRank survive 301 and 302 redirects?

Yes, and without theoretical loss. Contrary to a persistent misconception that circulated until a few years ago, Google fully transmits PageRank during a redirect, whether permanent (301) or temporary (302). This clarification ends years of debate over an alleged "tax" or dilution of SEO juice.

Specifically, if page A has a PageRank of X and redirects to page B, the latter inherits that X. No discount factor is applied to the transfer itself. What changes the game is the speed and technical complexity introduced by multiple redirects, not the volume of authority transmitted.

Why do redirect chains pose problems?

The issue is not so much PageRank but latency and server load. Each hop in the chain adds HTTP delay: the bot must query a server, receive a 3xx response, and then re-query the new URL. Multiply that by five, and you see why Google dislikes these setups.

Another concern is crawling complexity. The budget allocated to your site is wasted on unnecessary back-and-forths. If your architecture forces Googlebot to go through four redirects to access a strategic product page, you've just burned a portion of your crawl quota for... nothing. And Google eventually gives up after five redirects: the final page remains invisible.

What happens after the fifth redirect?

Google stops tracking and must recrawl to try to resolve the chain on a later visit. In other words, if your chain has six redirects, the final page isn’t indexed immediately. It enters a crawl queue, with no guarantee of priority.

You lose time, potential authority (the page remains invisible for several days or weeks), and unnecessarily complicate the bot's life. This is a technical penalty, not algorithmic: your PageRank is patiently waiting somewhere, but no one can access it.

• PageRank is fully transmitted during 301 and 302 redirects, without theoretical loss.
• Redirect chains increase latency and consume crawl budget without providing value.
• Google gives up after five hops and postpones the crawl of the final destination to a later session.
• No difference in transmission between 301 and 302 in terms of PageRank, even though 301 remains the standard for permanent migrations.
• Regularly audit your redirects to identify and fix chains before they impact indexing.

Does this statement align with real-world observations?

Overall, yes. Domain migration tests show that 301s effectively transfer authority, and the indexing delays observed after multiple chains align with this five-redirect limit. Clients who have cleaned up their chains often see a bounce in crawled pages and a reduction in the time it takes for new content to be discovered.

However, there's a nuance on one point: the speed of PageRank consolidation. Google does not specify how long it takes for authority to be fully transferred and counted in ranking. A few days? Several weeks? [To be verified] depending on the site's crawl budget and the frequency of bot visits. A niche site crawled twice a month will not see the effects as quickly as a news media outlet.

Do 302 redirects really transmit as much PageRank as 301s?

Google says yes, and empirical data supports this in most cases. But be careful: a 302 indicates a temporary situation. If it remains in place for several months, Google eventually treats it as a de facto 301. The real risk is indexing confusion: which URL should Google prioritize?

In practice, never keep a 302 in long-term production if the intention is permanent. You introduce ambiguity that can delay signal consolidation. The 301 remains the standard, and for good reason: it removes any uncertainty for the bot.

What to do if you inherit a disastrous redirect architecture?

Start by mapping all chains with Screaming Frog or an equivalent crawler. Identify those that exceed two hops (ideally, a single redirect should suffice). Prioritize fixing those that affect high-traffic pages or pages with strong backlink capital: these are the ones that waste the most crawl budget and transit PageRank.

Next, audit your server logs. If Googlebot passes through redirect chains leading to a dead page or a loop ten times a day, you have a structural problem that negatively impacts your SEO far beyond just PageRank transmission. A redesign of the URL architecture may be needed.

How can you identify and fix redirect chains on your site?

Run a full crawl with Screaming Frog enabling redirect tracking. The report will show you all detected chains, their lengths, and the URLs involved. Export the list and filter those that exceed one hop. You can also use tools like OnCrawl or Botify to cross-reference with log data and spot the most crawled chains.

Once you have the list, edit your redirect rules (the .htaccess file, Nginx configuration, or through your CMS) to point the original URL directly to the final destination. Test each modification with a tool like Redirect Mapper or simply using curl from the command line to verify the number of hops.

What mistakes to avoid when cleaning up redirects?

Never delete an active redirect without ensuring it's no longer referenced anywhere (backlinks, XML sitemap, internal linking). A sudden deletion turns a functional link into a 404, resulting in a loss of PageRank and traffic. Use Google Search Console to spot URLs still being crawled before making any changes.

Another trap: creating a new chain while fixing the old one. If you redirect A to C to bypass B, but C itself redirects to D, you haven’t solved anything. Always check the final destination before modifying a rule.

What impact to expect after optimizing redirects?

You should observe a decrease in the number of crawled redirects in your server logs and an increase in the volume of unique pages visited by Googlebot. The released crawl budget can be reallocated to more strategic content. If pages were blocked beyond five hops, they should appear in the index within a few days.

On the ranking side, the effect is indirect but real: less latency, better user experience, and quicker consolidation of PageRank on target pages. Don’t expect a jump of +20 positions overnight, but a gradual improvement in the site's technical health. These technical optimizations can be complex to orchestrate on a large site, especially if the architecture has evolved in successive layers over the years. Engaging a specialized SEO agency can help you avoid costly mistakes and speed up the diagnosis and implementation of fixes.

• Crawl the entire site to detect redirect chains
• Prioritize chains affecting high-traffic pages or pages with strong backlink capital
• Modify redirect rules to point directly to the final destination
• Test each modification with a redirect tracking tool (curl, Redirect Mapper, etc.)
• Check that external backlinks and internal linking point to the correct URLs
• Monitor server logs post-optimization to measure the impact on crawl budget