Redirect Checker

The Redirect Checker follows a URL through every redirect to its final destination.

Enter an address and see each hop, its status code, and whether the chain is clean, long, or looping.

How to check redirects

1. Enter a URL. Often an old or shortened link you want to trace.
2. Trace it. Our server follows the chain safely, up to ten hops.
3. Read the path. Each step shows its status code and where it points next.

See exactly where a link goes

Redirects are useful for moving pages, but chains that grow too long slow visitors down and waste crawl budget. Loops break a page entirely.

Tracing the path reveals whether a redirect is permanent or temporary, and confirms the final URL a visitor actually reaches.

• Hop by hop: every URL and status code in order.
• Loop detection: flags a URL that repeats.
• Final destination: the page a visitor lands on.
• SSRF-safe: private hosts are refused.

Related webmaster tools

Redirects and headers are closely linked. To read the full response headers of the final page, the HTTP Header Checker shows them all.

Once you reach the destination, the On-Page SEO Checker audits its title, headings, and meta tags. And to pull the meta tags from any URL, the Meta Tags Extractor lists them.

Frequently Asked Questions

How does it trace redirects?

Our server requests the URL and follows each Location header manually, revalidating every hop for safety, up to ten redirects. The full chain is returned so you can see each step.

What is the difference between 301 and 302?

A 301 is a permanent redirect that passes SEO value to the new URL, while 302 and 307 are temporary. Using the right one matters for search rankings.

Why are long redirect chains bad?

Each hop adds latency and can dilute link equity. Search engines and browsers also give up after too many, so keeping chains to one hop is best.

Can it detect redirect loops?

Yes. If a URL redirects back to one already seen in the chain, the tool flags it as a loop, which explains a page that never finishes loading.

Is the URL stored?

No. The URL is fetched to trace its redirects and is not saved. Only rate-limiting counters are kept to prevent abuse.