Skip to main content
RankBrain

Redirect Checker

Follows an address hop by hop and shows every redirect, status code and delay on the way to the final page.

We fetch the page for you. Our server fetches the public address you enter and reads the response. Nothing you enter is stored. Free, no account.

Finding the problem is the first half.

RankBrain writes the redirect rules into your framework config so every old address goes to the right page in one hop.

RankBrain works on websites built in code, through the AI tool you already use (Cursor, Claude Code, Codex, ChatGPT).

Check my site free

How it works

You changed a URL, or moved to HTTPS, and want to know what a crawler actually hits when it asks for the old address. This checker requests the address without following redirects, then follows each hop itself. You see every status code, server and time, and which hops cost you.

  1. 1

    We request the address without following redirects automatically, record the response, then request the next address ourselves. That shows each hop separately, with its status code, server and time.

  2. 2

    The result flags what costs you: chains longer than one hop, temporary redirects where a permanent one belongs, hops that drop from HTTPS to HTTP, loops, and chains that end in an error.

  3. 3

    Check up to 10 addresses at once, as a desktop browser, a phone or a search crawler.

What it does not do

  • Redirects done by JavaScript or a meta refresh inside the page are not followed; only server redirects are.

  • Some sites redirect differently by country. The check runs from our server's location.

When a source is busy or a site does not answer, this tool says so. It never fills the gap with a guess.

Questions

Why does my page show 302 instead of 301?

301 tells search engines the move is permanent. 302 says temporary and is a weaker canonical signal; search engines may still choose the destination. If you have moved a page for good, use 301. The checker flags a temporary redirect where a permanent one belongs, hop by hop.

My redirect works in the browser but the checker stops. Why?

The checker reads server responses. It requests the address without following redirects automatically, then requests the next address itself. A redirect done by JavaScript or by a meta refresh inside the page never shows up as a response header, so it is not followed. A stopped trace can also mean a blocked request, a timeout or the hop limit. Check the reported reason.

Why is a chain of five redirects a problem?

Each hop is another request before anyone reaches the page. A chain of five means four extra round trips for every crawler and every visitor, plus more places where the chain can break. The fix is to point the first address straight at the final one. The checker flags chains longer than one hop.

Tools that answer the next question

All 74 free tools