Redirect Checker
Trace every redirect hop of a URL with status codes
100% free. This tool needs our server to do the work, so what you submit is sent there, processed and then discarded - it is never stored.
About this tool
When a URL redirects (like an old page forwarding to a new one), it can sometimes chain through multiple hops before reaching its final destination - each hop adds load time and can affect SEO if not configured correctly. This tool traces every redirect hop of a URL, showing the status code (301, 302, etc.) at each step.
How to use this tool
- Enter source URLUse full URL you want to audit, including protocol and path.
- Trace redirect chainFollow each HTTP hop until final destination response resolves.
- Review status codesCheck permanent vs temporary redirects and unexpected loops.
- Fix server rulesUpdate CDN/server routing to reduce hops and canonical confusion.
Fixing redirect chains after a site move
Each extra hop adds delay and can weaken the signals passed on. After a migration, point every old URL directly to its final new URL in one hop, and update internal links so they go straight to the new address rather than through a redirect.
Use permanent redirects (301 or 308) for moves that will stay; 302 and 307 are for temporary changes. A loop - A to B and back to A - means the page never loads; the checker shows exactly where it starts.
Key features
- Exposes hidden redirect chains that slow page loads.
- Improves technical SEO by validating proper 301 usage.
- Helps detect loops and misconfigured routing quickly.
- Useful for migration and domain-change QA.
Common uses
- Auditing old URLs after site migration.
- Checking HTTP-to-HTTPS and WWW canonical routing.
- Fixing campaign URLs with excessive redirect hops.
- Validating affiliate/referral redirect behavior.
Tips for better results
- Keep redirect chains as short as possible (ideally one hop).
- Use 301 for permanent moves and 302 for temporary tests.
- Align redirects with canonical tags and sitemap URLs.
- Retest after CDN or hosting rule changes.
Mistakes to avoid
- Stacking multiple legacy redirects over time without cleanup.
- Using 302 for permanent URL migrations.
- Creating mixed protocol loops with conflicting rules.
- Ignoring mobile and subdomain variants in redirect testing.
Frequently asked questions
301 means "permanently moved" - search engines transfer ranking signals to the new URL. 302 means "temporarily moved" - search engines generally keep the original URL as the canonical one, expecting it to return eventually. Using the wrong type can affect how search engines treat the redirect for ranking purposes.
Each hop adds extra time before the page finally loads, hurting page speed - and very long redirect chains can sometimes cause search engines to stop following them, potentially failing to reach the final destination at all.
Yes - enter any publicly accessible URL to trace its redirect chain, whether it's your own site or one you're investigating.
A loop shows as a chain that returns to a URL already visited, ending in a 'too many redirects' error. It usually comes from conflicting rules, such as one forcing www and another removing it.
Every old URL should 301 to its closest new equivalent in a single hop. Redirecting everything to the home page loses rankings, and Google treats many such redirects as soft 404s.
Paste it here to see every hop and the final destination, which reveals where a shortened or tracking link really goes without visiting the page.