How many hops to the final page? Check redirects, catch loops, and see every status code before visitors do.
We'll send a summary for your target only. Unsubscribe anytime.
Every hop with status code and URL
Permanent or temporary - which type is used?
Where the chain ends, or where it loops
No account required · Free · Results in under 1s
Redirect chains and status codes in plain terms
A redirect sends visitors and crawlers from one URL to another. A single redirect is usually harmless, but long chains slow page loads, waste crawl budget, and can break the path to an important page. Our checker follows every hop and shows the full chain, so you see exactly where a URL ends up.
Broken redirects and redirect loops cause the same damage even when the final page looks fine. A free URL redirect checker lets you check redirects and trace every hop before visitors hit a dead end, an error page, or a loop. Use the checker after migrations, URL changes, or any time a page lands somewhere unexpected.
Run a one-time check after server changes, HTTPS rollouts, or relaunches. Add the URL to TotalSiteControl monitoring for automated alerts when chains break, loop, or grow too long.
Start free monitoring with email alerts. No credit card required.
Check redirects for any public URL in under a minute - no account needed.
Type the URL visitors use, for example yourdomain.com/old-page or a shortened campaign link. Every redirect starts somewhere - enter the exact starting URL, including the www or non-www version you want to test.
Click Check Redirects. We follow every hop and record the status codes, the chains, and the final destination URL. The checker stops when it reaches the last page or detects a loop.
See where the URL redirects, how many hops it takes, and whether the chain is clean. Then fix long redirect chains, remove loops, or turn on monitoring so you get alerts when redirects break.
What crawlers and visitors hit - and how to fix it before traffic drops.
The URL redirects back to itself or cycles between two pages. Browsers give up with an error, crawlers drop the page, and visitors never reach it.
Find the hop that points back and fix its target. Re-run the checker to confirm the loop is gone and the page loads.
Every redirect adds latency. Chains of three or more redirects slow the page, waste crawl budget, and dilute link equity on every visit.
Point the old URL directly at the final page. Remove intermediate redirects so the chain is one hop or zero, then re-check the page.
A 302 where a 301 is expected tells crawlers the redirect is temporary. Link equity stays on the old URL, and rankings can split across the chain.
Use 301 for permanent redirects and 302 or 307 for temporary ones. Check redirects after every change to confirm the page resolves correctly.
A campaign or legacy path lands on a 404 page, a staging host, or the wrong locale. The redirect works - it just points at the wrong destination.
Update the forwarding map or CMS rule to the live page, purge the CDN cache if needed, then verify with a fresh check.
Redirect chains, status codes, and reachability history in one place.
Checks run from our servers - the same path users hit.
Turn a one-off redirect check into monitoring in under a minute.
External probes so internal network blind spots do not hide issues.
Email and Telegram when a redirect breaks or a chain grows too long.
Start free - no credit card required to begin monitoring.
Start free monitoring with email alerts. No credit card required.
Quick habits that keep redirect chains clean.
The homepage, www, and non-www versions can each forward differently. Run the checker on every public URL that matters.
Every redirect adds a round trip. Point old URLs straight at the final page instead of chaining redirects.
Site moves and CMS changes often break redirect chains. Re-check redirects after every deploy.
A 302 tells crawlers the redirect is temporary. Use 301 when the page has moved for good.
Shorteners hide the real destination. Check redirects before you publish a campaign link.
It follows every hop from a starting URL to the final destination and reports each step, the status codes, and the full chain. You see where a page ends up before your visitors do - and can fix the path if something is broken.
Yes. Enter any public URL and get instant results - no signup, no credit card, and no limit on one-off checks. Optional monitoring alerts are also free to start, so you can watch important redirects over time.
Every hop passes crawlers to another URL. Long chains waste crawl budget, add latency, and can dilute link equity before it reaches the final page. A clean chain keeps ranking signals intact and your pages fast.
A 301 is a permanent redirect - crawlers transfer ranking signals to the new URL. A 302 is temporary and keeps equity on the original page. Use the right status code for every redirect so search engines treat the move the way you intend.
A redirect loop happens when a URL redirects back to itself or cycles between two pages. Browsers stop with an error, and crawlers drop the page from the index. The checker detects loops and shows which hops repeat.
Point each old URL directly at the final destination and remove intermediate hops. After fixing, run the redirect checker again on the same URL to confirm the chain is clean and the page resolves correctly.
Yes - enter any shortened link and the checker follows every redirect to the final page. Useful before clicking unknown links or auditing the short links you use in campaigns and emails.
Check redirects after migrations, CMS changes, or CDN updates. For production sites, automated monitoring is the safer option - it catches broken redirects before visitors and search engines do.
Crawl budget is the number of pages a search engine is willing to crawl on your site. Every hop consumes a crawl without indexing a page, so long chains leave fewer crawls for the pages that actually matter.
Yes. Each redirect adds a round trip before the page loads. Multiple redirects in a chain can add hundreds of milliseconds, which hurts Core Web Vitals and the user experience on every visit.
A 307 is a temporary redirect that preserves the request method, and a 308 is its permanent version. Both are newer status codes that browsers and crawlers support alongside the classic 301 and 302.
Yes - use a 301 redirect from HTTP to HTTPS so crawlers transfer ranking signals to the secure page. Check redirects on both www and non-www versions to avoid accidental chains.
A meta refresh redirect happens in the page HTML instead of the server response. It works, but it is slower and passes less link equity than a 301 redirect, so server-side redirects are the preferred option.
Yes - a 301 redirect passes most link equity to the destination page. Chains dilute it slightly with each hop, which is one more reason to keep redirect chains as short as possible.
Yes - the checker follows 301, 302, 303, 307, and 308 redirects hop by hop until it reaches the final page or detects a loop. You get the full chain with every status code in one report.