Skip to content
MrKeyword
Free redirect checker

Redirect checker: see every hop a URL takes.

Enter any address to follow it one redirect at a time, with the status code, destination and time for every hop, plus what to fix: chains, loops, temporary redirects and HTTPS problems.

Free, no account needed. MrKeyword fetches the page live and shows only what it found.

Built on first-party data from Google and Bing
Search ConsolePageSpeed InsightsBing Webmaster Tools
An explorer discovering useful search ideas with a magnifying glass
A little curiosity goes a long way.
What it checks

Where a link really goes, and how it gets there.

A redirect sends visitors and search engines from one address to another. One permanent redirect is normal; a chain of them slows every visit and wastes crawl budget, and a temporary redirect (302 or 307) tells search engines to keep indexing the old address.

The checker requests the address without following redirects, reads the Location header, and repeats until a page answers, so you see the exact path rather than only the end.

In the result

Clear answers,
with the reason shown.

Status codes

301, 302, 303, 307 and 308, explained.

Each hop shows its status and whether it is permanent or temporary.

  • Permanent vs temporary
  • Response time per hop
Problems

Chains, loops and dead ends.

Flags more than one redirect in a row, loops, HTTPS to HTTP and redirects that end in an error.

  • Redirect chains and loops
  • Final status of the page
More free checkers

Other quick checks.

Questions

About the redirect checker.

What is the difference between a 301 and a 302?

A 301 (or 308) is permanent: search engines move rankings to the new address. A 302 (or 307) is temporary: they keep the old address indexed. Use 301 when a page has moved for good.

How many redirects are too many?

Aim for one at most. Google follows up to 10 hops, but each one slows visitors down, and long chains are often a sign of old rules stacking up.

Does it follow JavaScript or meta refresh redirects?

No. It follows HTTP redirects, which are the ones search engines rely on. JavaScript and meta refresh redirects are slower and less reliable for SEO.