What is a redirect chain?
A redirect chain occurs when following an address requires another redirect after the initial one before reaching the destination. A direct redirect has no intermediate redirecting address. The relevant checks are the starting URL, each response status and Location value, and the final content.
Google’s redirect guidance explains redirect types and their search signals. RFC 9110 defines HTTP redirection semantics. A redirect chain is a sequence of responses, not a separate HTTP status code.
Extra hops complicate access and maintenance
Intermediate redirects add steps before a client reaches the useful page. Their actual delay depends on the connection, serving system and client behavior. Measure the route you are investigating instead of assigning a fixed latency to every hop.
Do not calculate a percentage of authority lost from the number of redirects. Google’s site-move guidance says permanent redirects do not cause PageRank loss. That does not guarantee that a moved page keeps every ranking: content, access and the wider migration still need review.
A shorter, correct mapping is easier to inspect and avoids unnecessary intermediaries. Prioritise broken destinations and important visitor routes using the data you actually have. Do not invent traffic or backlink counts to produce an impact score.
How an intermediate redirect can appear
An old guide moves to a new slug. Later, the new slug moves again. If the first mapping is left pointing at the second address, requests to the oldest URL take an intermediate step. This is an illustrative maintenance scenario, not a claim that every chain has the same cause.
Chain:
/old-guide/ → /renamed-guide/ → /current-guide/
Direct route after an appropriate mapping change:
/old-guide/ → /current-guide/The direct mapping is suitable only if the current guide represents the old page’s purpose. Do not flatten an application route blindly: an intermediate response may perform a required function, and the method or query behavior may matter.
Redirect chain, loop and direct redirect
| Pattern | What happens | What to investigate |
|---|---|---|
| Direct redirect | An old address sends the client to its replacement. | The status, Location value and replacement content. |
| Redirect chain | The route includes an intermediate redirecting address. | Whether the originating mapping can safely target the destination. |
| Redirect loop | The route returns to an earlier address. | The conflicting rules that prevent reaching useful content. |
A loop and a long chain are different failures. Shortening one section of a loop without resolving the rule conflict may leave the cycle intact. Trace the full route instead of changing the last response you happen to see.
Illustrative checks during a content move
A renamed article with an older hostname
Start at the old protocol and hostname as well as the old slug. Record every response until the intended article is reached. A redirect on the current hostname does not establish what a request to the earlier address does.
Review a direct mapping from the original URL to the current article. Check that it retains necessary query information and does not redirect an unrelated page to a generic destination. This example does not report a ranking recovery or a measured speed gain.
A form endpoint
Changing the destination alone can alter application behavior. RFC 9110 permits a client to change POST to GET when following a 301 or 302. Its method-preserving alternatives are 307 for a temporary move and 308 for a permanent move. Choose the status for the intended semantics, not simply the shortest-looking route.
Ask the application owner to verify the submission behavior. A content crawler using ordinary page requests cannot certify that a form or API still works. The 301 redirect entry explains the status distinctions in more detail.
A status code does not describe the whole journey
A 301 can be part of either a direct route or a chain. Temporary and permanent responses can also occur in the same sequence. Record each status and destination, then check whether the sequence matches the intended move.
For Google Search, permanent redirects are canonicalization signals. They are different from a canonical annotation on a page that remains accessible. Do not replace a redirect with an annotation when visitors need to be sent elsewhere.
Trace and simplify a redirect safely
- Choose the source addresses. Include the actual old URL and relevant protocol, hostname and trailing-slash variants.
- Record the complete route. Note the status and Location value at every step, including failures or a return to an earlier URL.
- Verify the destination. Inspect its response and content before changing any mapping. Confirm it answers the old page’s purpose.
- Review behavior that must survive. Consider request methods, query values and application responsibilities where applicable.
- Change the originating mapping. A repair to the middle address alone can leave an earlier chain in place.
- Update references and test again. Use the intended current address in relevant internal links and sitemap entries. Recheck old addresses rather than assuming updated navigation repairs them.
Keep a recoverable redirect map with the source, destination and reason. This makes a later move easier to review without losing the relationship between older addresses and current content.
Do not treat a crawler limit as a recommended chain length
Google’s current HTTP-status guidance describes general web crawling with a redirect-hop limit of ten, while noting product-specific differences and separate robots.txt handling. It does not establish a universal five-hop cutoff for every Google request or a sensible target length for a route.
Exceeding a client’s follow limit prevents that attempt from reaching the destination. It does not prove that the destination is invisible through every other discovery route. Check the destination separately.
The URL Inspection documentation says its live test follows redirects without displaying the final tested address. A successful test therefore is not proof that the starting URL served content directly. Use a separate trace to understand the route.
Do not remove useful old mappings merely because current internal links have been updated. Older external links and bookmarks can still lead to those addresses. Review the intended move and retain a working path to its legitimate replacement.
Can I send every old URL to the homepage?
That is usually the wrong mapping for distinct retired content. Google’s site-move guidance warns against redirecting unrelated old pages to one irrelevant destination, which can be treated as soft 404s. Map each moved page to relevant replacement content; when no replacement exists, evaluate an appropriate missing-page response instead.
Related glossary terms
- 301 redirect: understand a permanent response and its method behavior.
- Canonical URL: distinguish duplicate preference from redirecting visitors.
- Crawl budget: review request activity without inventing quotas.
- Soft 404: recognise irrelevant or missing destinations.
- Indexing: inspect the destination’s search state separately.
Sources and editorial note
Official Google guidance and RFC 9110 are linked beside the explanations, checked on October 12, 2026. AI assisted this revision. Routes are illustrative. No client migration, latency measurement, ranking comparison, private analytics or named expert approval was tested. The existing publication date is retained, with its historical provenance unresolved.