Redirect Chain Checker

Trace every redirect hop for any URL. Detect loops, count hops, and find redirect chains that are slowing your site and hurting your SEO.

What does this tool check?

Full Redirect Chain

Every redirect hop is traced and shown visually with its status code, destination URL, and response time.

Loop Detection

Automatically detects redirect loops where URLs redirect back to themselves, causing infinite cycles.

HTTP → HTTPS Upgrades

Highlights which hops perform HTTP-to-HTTPS upgrades or www/non-www changes so you can consolidate them.

SEO Issue Flags

Flags issues that hurt SEO: long chains, temporary 302 redirects where 301 is needed, and missing HTTPS upgrades.

Got questions?

Frequently Asked Questions

Everything you need to know about Uptrue — no fluff.

What is a redirect chain?
A redirect chain is a sequence of redirects before reaching the final URL. For example: http://example.com → https://example.com → https://www.example.com is a 2-hop chain. Each extra hop adds delay and can reduce how much SEO value passes through the chain.
Yes. Long chains slow down page load, search engine crawlers may stop following them after 3-5 hops, and each hop can reduce the link equity passed to the final URL. Consolidate chains to a single direct redirect to the final destination wherever possible.
301 (Permanent) — search engines transfer link equity to the new URL and update their index. Best for permanent page moves. 302 (Temporary) — search engines keep the original URL indexed and do not fully transfer ranking signals. Only use 302 when the redirect is genuinely temporary, such as during A/B testing or maintenance.
One redirect hop is ideal. Two is acceptable. Three or more starts to impact SEO and performance. Google follows up to 10 redirects but may reduce crawl budget for pages with long chains. Each hop adds 100–300ms of latency. Aim to direct old URLs straight to the final destination in a single 301.
A redirect loop occurs when URL A redirects to URL B which redirects back to URL A. To fix: check your .htaccess or Nginx config for conflicting rules, check any CMS redirect plugins for duplicates, and review CDN redirect rules (Cloudflare Page Rules). Make sure your HTTP→HTTPS and www→non-www rules do not create a cycle.

Monitor your redirects automatically

Redirect chains often appear silently after deployments. Uptrue's redirect chain monitoring watches your URLs continuously and alerts you when a chain changes or a loop appears. Pair it with HTTP uptime monitoring for end-to-end coverage.

Start Monitoring Free