Skip to content
toolsbox

Bulk Redirect Chain Checker

Trace every hop for up to 100 URLs — chains, loops, 302s and broken destinations.

  • Free
  • No sign-up

What is a bulk redirect chain checker?

A bulk redirect chain checker follows every redirect for a list of URLs and shows you each hop on the way to the final destination. Paste up to 100 URLs, one per line, choose a user agent, and the tool requests each URL server-side without auto-following redirects. It records the status code, the Location header and the response time for every hop, up to a maximum of 10, then reports where each URL ends up and what went wrong along the way.

Browsers hide all of this. You type an old URL, land on the right page, and never see that it passed through three redirects first. Search engine crawlers do see every hop, and so do users on slow mobile connections, because each hop is a separate HTTP request with its own DNS lookup, connection and wait time.

The checker flags the problems that matter for SEO: chains of two or more hops, redirect loops, temporary redirects (302, 303, 307) where a permanent one was probably intended, HTTP to HTTPS hops, www and non-www host switches, final destinations that return 4xx or 5xx errors, meta refresh tags on the final page, and chains that exceed the hop limit. Results include summary counts, an issues-only filter, an expandable chain for each URL and CSV export.

How to check redirect chains in bulk

  1. 1

    Paste your URLs

    Enter up to 100 absolute URLs, one per line. Good sources are old sitemap files, a crawl export of internal links, top backlink targets or the old URLs from a migration map.

  2. 2

    Choose a user agent

    Pick the toolsbox bot, Googlebot smartphone or Chrome desktop. Some servers redirect differently by device or block unknown bots, so compare results when something looks off.

  3. 3

    Run the check

    URLs are processed in batches of 10 with a progress bar. Each one is followed hop by hop until it reaches a non-redirect response, loops, or hits 10 hops.

  4. 4

    Filter to issues

    Use the summary counts and the issues-only filter to focus on chains, loops, temporary redirects and broken destinations. Expand any row to see every hop with its status code, Location header and timing.

  5. 5

    Export and fix

    Download the CSV, then update redirect rules so each old URL points straight to its final destination, and update internal links to use the final URL directly.

When to use a redirect chain checker

Validating a site migration

Before and after a domain move, replatform or URL restructure, run the old URLs from your redirect map to confirm each lands on the intended page in a single 301 or 308 hop.

Cleaning up layered redirects

Sites that have been through several redesigns often stack rules: an old URL redirects to a 2019 URL, which redirects to a 2022 URL, which redirects to the current one. The checker exposes these chains so you can collapse them.

Protecting backlink value

Check the URLs your strongest backlinks point to. If they pass through a long chain or end at a 404, fix the redirect so that link equity reaches a live, relevant page.

Auditing HTTPS and host canonicalization

A common pattern is http://example.com to https://example.com to https://www.example.com. That is two hops where one would do; the checker flags both the protocol and host changes.

Finding internal links that redirect

Paste internal link targets from a crawl. Any that redirect should be updated in your templates and content so users and crawlers reach the final URL directly.

Redirects and SEO: what actually matters

Google documents that Googlebot follows up to 10 redirect hops; beyond that, the URL fails with a redirect error. Staying under the limit is not the goal, though. Every hop adds latency, consumes crawl requests and adds another place for a rule to break, so the practical target is a single hop from any old URL to its final destination.

Status codes carry meaning. 301 and 308 are permanent: they tell search engines the old URL has moved and the new URL should be indexed in its place. 302 and 307 are temporary: they say the original URL is still the one that matters, so search engines may keep it indexed. Google has said that a redirect left in place long enough may eventually be treated as permanent, but relying on that is slow and unpredictable. If a move is permanent, use a permanent code.

Meta refresh tags and JavaScript redirects are weaker signals than server-side redirects and add a full page load before the next hop. The checker reports a meta refresh on the final page so you can replace it with a proper 301.

Fixing redirect rules is only half the job. Update internal links, canonical tags, hreflang annotations and XML sitemaps to point at final URLs. Redirects should catch external links and old bookmarks, not route your own navigation.

Frequently asked questions

Is the bulk redirect chain checker free?

Yes, the bulk redirect chain checker is free to use without an account. You can check up to 100 URLs per run, switch between user agents and export results to CSV. Runs are rate-limited to keep the service responsive, so very large audits are best split into several batches spread over a session.

What do you fetch, and is anything stored?

We fetch only the public URLs you paste and the redirect targets they point to, nothing else. Each hop is requested server-side, analyzed in memory and returned to your browser; your URL list and results are not stored. Requests are rate-limited, and private or internal network addresses are blocked for security.

How many redirects is too many?

More than one redirect hop is worth fixing, even though Google follows up to 10. Each extra hop adds a full request and response, which slows users and wastes crawl activity. The checker flags any chain of two or more hops and marks chains that reach the 10-hop limit as failures.

Should I use a 301 or a 302 redirect?

Use a 301 or 308 when a page has moved permanently, and a 302 or 307 only when the move is genuinely temporary, such as a short promotion or maintenance page. Permanent redirects tell search engines to index the destination. Google may eventually treat a long-standing temporary redirect as permanent, but that takes time and is not something to plan around.

Why do results differ between user agents?

Some servers redirect based on the user agent, sending mobile browsers to an m-dot site or blocking unfamiliar bots with a 403. Testing as Googlebot smartphone shows what Google's crawler is likely to receive from user-agent rules, while Chrome desktop shows the typical visitor path. IP-based bot verification can still produce different results for the real Googlebot.

What is a redirect loop?

A redirect loop happens when a URL redirects back to itself, directly or through other URLs, so the request never reaches a final page. Browsers show a too many redirects error and crawlers give up. Loops usually come from conflicting rules, such as an HTTPS rule and a trailing-slash rule undoing each other, or a CDN and origin server disagreeing.