How to find and fix redirect chains, loops and outdated URLs

What is a redirect chain?#

A redirect chain is a sequence in which one URL redirects to another URL that redirects again before reaching the final resource. For example, /old may lead to /archive, which then leads to /new. A redirect loop occurs when the sequence circles back to an earlier URL and never reaches a useful destination.

One intentional redirect can be appropriate after a permanent move. A chain often grows when migrations, URL normalization and template updates happen at different times. Review the observed behavior rather than assuming every redirected result is wrong.

Why redirect chains deserve review#

Each additional redirect requires another step before the destination can load. Chains can also hide outdated internal references and make the site harder to maintain. A loop is more serious because it prevents the visitor from completing the journey.

Google distinguishes permanent and temporary redirects, so choose the response that fits the move. Avoid turning a temporary experiment into a permanent mapping without a reason. When you own an internal source link, linking to the intended current URL makes the journey easier to inspect and reduces dependence on intermediate rules.

How to inspect a redirect trail#

Start with the address that appears in the source page, not a manually corrected version. Inspect the redirect trail and final destination in the Linky report, then open the result in a browser. Confirm the title and content as well as the URL.

The redirect-chain visualizer on this website can help organize hops you paste into it. It illustrates the supplied sequence; it does not fetch URLs or discover live server redirects. Use observed data from a scan or a request inspection rather than guessing the sequence.

1. Copy the exact source URL and preserve its path and query string.
2. Record the observed hops and their final destination.
3. Check whether the move is permanent, temporary or an error.
4. Repair the mapping or source reference you control.
5. Test the old entry point and the updated source link.

Fix loops before optimizing ordinary chains#

A loop can result from conflicting host rules, HTTPS rules, trailing-slash rules or application redirects. For example, one rule may add a slash while another removes it. Check the rules responsible for each hop so that changing one layer does not recreate the problem elsewhere.

Test representative URLs after a rule change, including query strings and paths that should not redirect. Avoid repeatedly editing production redirect rules without a record of the intended mappings. Keep rollback information available when a shared rule affects many pages.

Update internal links while keeping useful redirects#

Redirects protect older references, bookmarks and links from other websites. Updating internal links does not mean those protections should immediately disappear. Maintain the old-to-new mapping according to the migration plan while your own templates and content move to current destinations.

Audit navigation, footers, documentation and article references after a migration. Repeated redirects from shared components are easier to fix in the component than page by page. Verify canonical URLs and sitemap entries separately; a link report does not replace the full migration checklist.

Record a redirect mapping that another person can verify#

For each change, record the old URL, intended final URL, reason for the move and observed response. If the destination contains a fragment or important query parameters, test that those still produce the right experience. Do not discard parameters that a download or application workflow relies on without understanding their purpose.

After publishing, rescan the affected section and compare the old entry points. Look for chains that appeared only after combining a new content mapping with an existing normalization rule. Keep known exceptions in the handover so the next release does not accidentally undo a valid redirect.

• Resolve loops and irrelevant destinations first.
• Simplify unnecessary hops where you control the mapping.
• Use current destinations in owned internal links.
• Retain needed redirects for older references.
• Check paths, parameters and fragments after changes.

Frequently asked questions#

Put this workflow into practice

Read the related Linky documentation for the product controls and limits used in this article. Contact support if a result requires further investigation.