See the full redirect chain, hop by hop
Trace exactly what happens between the URL you enter and where it finally lands - loops, excess hops, and protocol downgrades included.
What gets checked
Redirect loops
Catches a URL that redirects back to itself, directly or through a longer chain - something a browser will refuse to load at all.
Excess hops
Flags chains longer than one hop - each extra redirect adds latency and dilutes the SEO value passed to the final URL.
HTTPS-to-HTTP downgrades
Flags a chain that goes from a secure URL back to an insecure one - a real, uncommon misconfiguration that defeats HSTS.
How it works
Every hop safety-checked before it's followed.
Paste a URL
Any URL you suspect redirects - or want to confirm doesn't.
Each hop is followed and checked
Every redirect target is safety-checked before being followed, up to 10 hops.
See the full chain
Every hop's status code, in order, plus what to fix if something's wrong.
Frequently asked questions
How many redirects is too many?
More than one hop is worth investigating. A single 301 from an old URL to its replacement is normal and healthy; chains of three or more usually mean redirects have been stacked on top of each other over time without ever being cleaned up.
Does a redirect chain actually hurt my SEO?
Each additional hop adds latency, and while modern search engines follow chains reasonably well, a long chain increases the chance a crawler gives up before reaching the final page - and it's a strictly worse experience for real visitors regardless of any ranking impact.
What's the difference between a 301 and a 302?
301 is permanent and tells search engines to transfer ranking signals to the new URL. 302 is temporary and traditionally signals "don't update your index yet." Using a 302 for what's actually a permanent move is a common, easy-to-miss mistake.
Why would a redirect chain downgrade from HTTPS to HTTP?
Usually leftover legacy rules - an old HTTP-to-HTTPS redirect combined with a newer rule that accidentally sends part of the chain back to HTTP. It's uncommon but worth catching, since it can undermine HSTS and trigger browser security warnings.
Related audits
Website Audit
Run a free instant audit for performance, SEO, accessibility, and best practices.
SEO Audit
Check crawlability, metadata, structured data, and AI-agent discoverability.
Performance Audit
A full Lighthouse lab run across desktop and mobile, with framework-aware fixes.
Accessibility Audit
See exactly which WCAG 2.1/2.2 success criteria your site fails, and why.
Security Audit
Turn a header/vulnerability scan into SOC 2 and GDPR control evidence.
Website Speed Test
How fast your site loads, in plain language - one number, no jargon.
Core Web Vitals Test
Check LCP, CLS, and INP against Google's thresholds, lab and field.
Broken Link Checker
Crawl a page's links and find the ones that are dead before your users do.
Security Headers Checker
CSP, HSTS, and every other HTTP security header - analyzed, not just listed.
Open Graph Checker
See whether your page has the og:title, og:description, and og:image tags social platforms need.
Schema Markup Checker
Check whether your page ships JSON-LD structured data search engines and AI agents can read.
Sitemap Checker
Check whether your sitemap.xml is reachable, valid, and free of common mistakes.
Fix guides