Understanding how redirects affect SEO requires separating two distinct concerns: signal consolidation (where link equity flows) and crawl behaviour (how quickly Googlebot processes the change). Both matter, but they operate on different timescales and respond differently to implementation mistakes.
Key Takeaways
- 301 redirects pass nearly all PageRank to the destination; the amount is not precisely published but empirically close to 100% for direct redirects
- Redirect chains (A → B → C) cost link equity at each hop — flatten chains to a single hop wherever possible
- 302 redirects signal temporary moves; Google retains the original URL in its index and doesn't consolidate link equity — use 301 for permanent moves
- Google processes 301 redirects gradually over weeks, not instantly — expect 2–6 weeks for full ranking transfer after a migration
- The Redirect Tracer tool shows the full hop chain for any URL, revealing redirect chains, mixed HTTP/HTTPS hops, and unexpected status codes
301 vs 302: Which One Passes Link Equity?
| Code | Meaning | Link equity | Index retention |
|---|---|---|---|
| 301 Moved Permanently | This URL has permanently moved | Passes to destination | Old URL deindexed over time |
| 302 Found | Temporarily at another URL | Retained at source URL | Old URL stays indexed |
| 307 Temporary Redirect | Temporary, must preserve method | Retained at source URL | Old URL stays indexed |
| 308 Permanent Redirect | Permanent, must preserve method | Passes to destination | Old URL deindexed over time |
In practice, use 301 for permanent moves (domain migrations, URL restructures, HTTPS upgrades). Use 302 only when the redirect genuinely is temporary — A/B tests, maintenance pages, geo-based temporary detours. Using 302 for a permanent move means Google keeps the old URL indexed and doesn't consolidate link equity — a mistake that can last months in the index.
Redirect Chains and Link Equity Bleed
A redirect chain occurs when A → B → C (or longer). Each additional hop introduces latency, crawl budget cost, and — according to Google's guidance — some degree of link equity loss. Google has stated it follows chains up to 5 hops, but the practical advice is the same: flatten to a single hop.
Common sources of unintentional redirect chains:
- HTTP → HTTPS → www: Three-step chain when both the HTTPS migration and www normalisation add their own redirect. Consolidate to one rule.
- Old legacy redirects left in place: A migrates to B from a 2019 restructure. B migrates to C in 2023. Now external links to A go through two hops.
- Trailing slash normalisation layered on HTTPS:
http://example.com/page→https://example.com/page→https://example.com/page/
The Redirect Tracer tool is the fastest way to audit any URL for chains. Paste a URL and it follows every hop, reporting status code, server, and response time at each step — including any mixed-HTTP hops.
Redirect Loops
A redirect loop (A → B → A, or longer cycles) causes Googlebot to stop crawling the chain and mark the URL as inaccessible. Loops are usually caused by misconfigured HTTPS rules (http:// redirects to https:// but the server also redirects https:// back to http://) or CMS redirect plugins that duplicate server-level rules.
The Redirect Tracer detects loops and flags them immediately — stopping at the repeat URL rather than following the chain indefinitely.
When to Use 404 vs 410
When a page is gone permanently with no replacement, you have two options:
- 404 Not Found — signals the page doesn't exist at this URL. Google will eventually deindex it, but the rate is slower than with 410.
- 410 Gone — signals the page has been permanently deleted and should not be indexed. Google deindexes 410 pages significantly faster than 404s.
Use 410 for pages you've actively removed and are confident won't return (discontinued products, outdated content you've deleted). Use 404 as the default for missing pages.
How Long Does a 301 Take to Transfer Rankings?
The SEO impact of a 301 is not immediate. Google's processing of redirects involves several stages:
- Crawl — Googlebot visits the old URL, sees the 301, records the destination. Depends on crawl rate.
- Index update — Google updates its index to replace the old URL with the new one. Can take days to weeks.
- Ranking transfer — The new URL is treated as inheriting the signals of the old one. The full transfer can take 2–6 weeks for well-crawled sites.
For large site migrations, expect some ranking fluctuation in the 4–6 week window after the migration, even with a well-executed 301 implementation. Monitor Search Console's Coverage report and URL Inspection tool to track deindexation of old URLs and indexation of new ones.
HTTPS Migration Redirects
HTTPS migrations are one of the most common 301 scenarios. Best practice:
# .htaccess — single hop HTTP → HTTPS (includes www normalisation)
RewriteEngine On
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} ^example\.com [NC]
RewriteRule ^(.*)$ https://www.example.com/$1 [R=301,L]This collapses both the HTTP→HTTPS and non-www→www normalisation into a single redirect, avoiding a two-hop chain.
Trace Any Redirect Chain
The Redirect Tracer follows every hop — reporting status code, server, response time, and Location header at each step. Instantly identifies chains, loops, and unexpected HTTP hops.
Try Redirect Tracer Free →Affiliate disclosure: Some links on this page may be affiliate links. We only mention tools we've personally used and have an honest opinion about. Affiliate revenue helps keep ByteWaveNetwork's tools free and maintained. We are not paid by any of the tools compared in this article for favorable coverage.