Built by us, for us: we wanted to measure our own sites in search and AI – without an expensive subscription.

Start for free

Guide

Resolving redirect chains and redirect loops

Learn how to spot redirect chains and redirect loops, find the causes and switch cleanly to a direct target URL path.

Weiterleitungsketten und Redirect-Schleifen auflösen means shortening the path of a request or ending an infinite loop. Find the affected URLs, check the redirect path and use as few hops as possible.

In practical terms, this is about identifying, classifying and fixing technical SEO findings. Clean URL structures, clear rules and careful checking of redirects all help.

What a chain is

A redirect chain exists when a URL does not lead directly to the target URL, but routes via further addresses. A redirect loop occurs when redirects refer back to one another and no endpoint is reached.

The distinction is important: not every redirect is a problem. It becomes problematic when the path gets unnecessarily long or goes round in circles. A hop is a single step from one URL to the next.

Typical causes are:

  • old paths after a relaunch
  • www and non-www variants
  • http to https migrations
  • language or slash variants
  • duplicate rules in server configuration or CMS

Technically, the cleanest approach is usually a direct jump from the old URL to the final target URL. For the team, a simple distinction often helps: chain = several redirects in a row, loop = redirects with no end.

A technical Site Audit shows such paths as findings. In the Dashboard you can assess them together with other data. Search Console can also help you find the affected addresses. If you later review search queries, Rank-Tracking supports the classification; it shows the position of a query for selected location and device values at a given point in time. Keyword Research and Competitor Analysis are not central to this, but can be useful in the surrounding context.

Why they cost crawl and speed

Search engine crawlers follow redirects in order to find and understand content. Each additional step adds extra requests. In a chain, the crawler has to process several intermediate destinations before it reaches the actual target page.

In a redirect loop, the fetch does not sensibly reach its destination. The page may then not be captured cleanly, because the redirect runs in circles.

Users notice this too: several redirects lengthen the request and can delay the page load. It is not a content issue, but it is a technical finding you should take seriously.

A technical Site Audit checks such points, among other things, through:

  • status codes such as redirects
  • internal links
  • load time

Search Console also helps you classify your own site. There you can see clicks, impressions, CTR and average position for the verified property. Important: average position is an average across impressions, not a fixed rank.

For technical classification, you can use Google Search Central documentation as a reference; the pages may change.

If you want to view audit, Search Console and tracking data together, SerpDash by ballmüller solutions in Berlin can be used for this; some functions are still in development.

How to find them

Start with a technical Site Audit. Redirects, status codes and internal linking are checked systematically there, and you often see the first clues the fastest.

Then check the affected URLs individually and follow the redirect path step by step to the final URL. A redirect is a forwarding from one URL to another.

Pay particular attention to these patterns:

  • several redirects on the same route
  • mixed variants of the same domain
  • jumps between old and new directories

Also check whether canonical tags, robots directives or internal links still point to the wrong URL variant. That helps you find the cause, not just the symptom.

If a page stands out in Search Console, clicks, impressions and average position can serve as clues. But the value is not direct proof of a redirect chain.

Rank-Tracking is also useful if you want to monitor a specific search query for a chosen location and device. A rank is always only a snapshot and depends on location, device, language and personalisation.

If you want to see audit, Search Console and tracking data together, you can use SerpDash by ballmüller solutions in Berlin for this; some functions are still in development.

How to fix it with one hop

The aim is usually a direct redirect from the old URL to the final target URL. That keeps the path short and easy to verify.

Start with the rule that triggers the redirect. Remove intermediate destinations if they serve no separate purpose. If several rules catch the same URL, define a clear target structure so that redirects do not trigger one another.

Proceed as follows:

  • check old rule locations and clean up duplicate rules
  • lead the old URL directly to the final address
  • switch internal links to the final URL
  • set canonical tags to the reachable target page
  • check the affected URLs again after the change

In a loop, the cause is often in the rule chain itself. For example, an old rule may not have been removed after a changeover, or a target URL may have been brought in again as a source.

Document the new redirect path so that later changes remain traceable. For ongoing monitoring, SerpDash by ballmüller solutions, Berlin, can be used; it combines Rank-Tracking, Search Console data and Site Audit in one dashboard, and some functions are still being developed.

Frequently asked questions about redirect chains and redirect loops

How do I clearly distinguish a chain from a loop in the finding?

A redirect chain exists when a URL passes successively through several addresses and ends up at an accessible target page. A redirect loop exists when the redirect leads back to earlier addresses and no sensible endpoint is reached.

For the initial check, look at the order of the responses. In a chain there are several steps, but a conclusion. In a loop, the path repeats itself or leads back to the start. This matters because the cause is not in the same place.

Simply put: a chain keeps going, a loop goes round in circles.

Look out for recurring addresses and for the same URL in several roles. If old and new variants of an address appear one after the other, that points more towards a chain. If a target address appears again as the starting point, that points more towards a loop.

Which signals from a technical audit are particularly useful for this?

A technical Site Audit checks pages against rules such as status codes, redirects, internal links, canonical tags, robots directives, titles, meta descriptions and load time. For redirect chains and loops, the redirect findings are especially important, because they show the path of the request.

It is helpful if the audit not only reports that a redirect exists, but also shows the sequence of steps. Then you can see whether a hop is unnecessary or whether an address appears more than once in the process. In a loop, it is also crucial whether the target page is reachable at all.

Also check the accompanying information. Internal links may still point to an old variant. Canonical tags may mark a different address as preferred. Robots directives can restrict access to variants. These clues do not always explain the error, but they help with classification.

If several findings appear at once, the usual rule is: first the clear errors, then the tangled cases. That keeps the check manageable.

What should I change first when fixing the error?

Start with the rule that triggers the redirect. The aim is usually a direct jump from the old URL to the final target URL. If you only replace an intermediate destination, the chain often remains unnecessarily long or the loop continues.

Proceed in this order:

  • check the affected redirect rule
  • remove intermediate destinations if they serve no separate purpose
  • define clear target URLs
  • switch internal links to the final address
  • set canonical tags to the reachable target page

Make sure old and new variants do not remain active at the same time if they can trigger one another. Such errors often arise after changes, when an earlier rule has not been removed or several rules capture the same path.

The most important point is a clear target address. The fewer stations there are between the source URL and the target page, the easier the path is to check.

How do I check the fix afterwards?

After the change, check the redirect path again from the source URL to the target page. What matters is that the process now stays direct and no further station is added. If you only look at the first response, a second redirect can remain unnoticed.

Also check the signals that can reveal the cause. Search Console data show clicks, impressions, click-through rate and average position for the verified property. Average position is not a fixed rank, but an average across impressions.

If you use Rank-Tracking, bear in mind that a rank is always only a snapshot. It depends on location, device, language and personalisation. It is therefore suitable for monitoring a query, but not as the sole proof of the effect of a redirect change.

These steps are still useful after the fix:

  • open the affected URL again
  • check the full path
  • check internal links to the final address
  • document the finding so later changes remain traceable

If you want to analyse audit, Search Console and tracking data together, SerpDash by ballmüller solutions in Berlin can be used for this; some functions are still in development.

Next step

If you deal with such findings regularly, it is worth having a workflow in which audit, Search Console and tracking come together in one place. That way you can keep the affected URLs and their development in clear view.

SerpDash by ballmüller solutions in Berlin combines Rank-Tracking, Search Console data and Site Audit in one dashboard for this purpose; some functions are still being developed.

This allows you to:

  • collect affected URLs more quickly
  • check the redirect path
  • review the cleaned-up structure again later

All guides