Skip to content

Free redirect checker

Free redirect checker that traces every hop a URL takes.

Paste a URL to check its redirects. You see each hop in order with its status code, where it points and how long it took, plus plain advice on loops, long chains and temporary redirects. No account needed.

  • No sign-up needed
  • 10 free checks a day
  • Up to 10 redirects followed
Try an example

Free, no signup, 10 checks a day. Follows up to 10 redirects over https.

Free checks a day, no account
10Free checks a day, no account
Redirects followed in one check
10Redirects followed in one check
Redirect codes read: 301, 302, 303, 307, 308
5Redirect codes read: 301, 302, 303, 307, 308
Wait per hop before it's called unreachable
8 sWait per hop before it's called unreachable

What you get

The whole redirect chain, hop by hop.

The checker requests the URL, reads the status code and the Location header, then follows each redirect itself. That way every step is timed and shown, not just the page you end up on.

    • example.com/old-page301 · 120 ms
    • www.example.com/old-page302 · 95 ms
    • www.example.com/new-page200 · 190 ms

    Example chain

    Trace redirects from first URL to final page

    Each hop gets a row with its status code, its address and its time, in the order a browser would meet them.

    • 301
    • 308
    • 302
    • 307

    A 301 redirect checker that flags 302s

    Permanent and temporary redirects are told apart, and a 302, 303 or 307 comes with a note to use 301 or 308 for a permanent move.

    • Loop
    • Ends in a 404

    Redirect loops caught

    The check stops as soon as an address repeats and names the one that closes the loop.

    • Moves to another host
    • Switches protocol

    Host and protocol changes marked

    A hop that adds or drops www, moves to another domain, or switches protocol is labelled, so a stray rewrite stands out.

  • 405 ms

    Example total time

    Time for every hop

    See which step is slow, and how much the whole chain adds before the page starts to load.

Check where your URL really goes.

Paste any address and see every redirect it takes, with plain advice on what to fix. Free, no account needed.

Check redirects

Why it matters

Every extra hop costs you something.

  • Speed

    Each hop is another round trip before the page starts loading. On a slow server or a phone, a chain of three is a delay people notice.

  • Signals to search engines

    A 301 or 308 says the move is permanent, so the new URL is the one to index. A 302 left in place by mistake can keep the old URL in results. Run a check after every change to your redirect rules.

  • Dead ends

    A loop, or a chain that ends in a 404, loses the visitor and the link that sent them. One check shows where it breaks.

How to check a URL redirect

From URL to full redirect chain in seconds.

  1. 1

    Enter a URL

    Paste a full address with its path, or just a domain. The check starts from its https version.

  2. 2

    Follow each hop

    The checker requests the URL, records the status code and time, then follows the Location header, up to 10 redirects.

  3. 3

    Read the advice

    Chains, temporary redirects, loops and error pages are called out in plain words, with what to change.

Read it honestly

What a redirect check can and can't show.

The checker sees what the server sends back, header by header. A few kinds of redirect live elsewhere, and it's worth knowing which.

What it shows

  • Every server-side redirect in order, with its status code, its target and how long it took to answer.
  • Loops, chains of two or more redirects, temporary redirects, missing Location headers and chains that end in an error.
  • A redirect that drops from https to http, which is flagged and not followed.

What it can't show

  • Redirects made with JavaScript or a meta refresh tag. Pages aren't rendered, so only HTTP redirects are followed.
  • An http starting point. The check only connects over https, so an http address is checked from its https version.
  • A bulk redirect check. It traces one URL at a time, and what you see is one fresh request from our servers, with no cookies.

Who it's for

Built for the people who move pages.

  • SEO specialists

    Confirm a migration's redirects are single, permanent hops before crawlers find the chains. Spot-check the old URLs that carry the most links first.

  • Developers

    See what a server rule actually returns, including relative Location headers and www or https rewrites.

  • Marketers

    Make sure campaign links and short links land on the right page instead of an error.

  • Site owners

    After a redesign or a domain change, check that old URLs still reach a page that loads.

FAQ

Questions, answered.

Free SEO tools

Redirects fixed? Check who links to the pages you moved.