A redirect checker requests a URL, follows every redirect it issues, and reports the full chain of hops and HTTP status codes that lead to the page that finally loads. That single trace answers a surprising number of questions at once: whether a page uses the right 301 or the wrong 302, whether a migration left behind a tangle of chained hops, whether two conflicting server rules have created a loop, and whether your HTTPS and www canonicalization resolve in one clean step. This redirect checker is also an http redirect checker, a 301 redirect checker and a redirect chain checker in one — and everything below explains what the numbers mean and how to act on them.
What is a redirect?
A redirect is a server’s instruction that the content you asked for lives at a different URL. When you request a page, the server can respond with a 3xx status code and a Location header pointing elsewhere; your browser — or a search-engine crawler — then requests that new URL instead. Most of the time this is invisible: you type one address and quietly land on another. The redirect itself is the mechanism that keeps old links working after you move, rename or consolidate pages.
Redirects are essential plumbing for any site that changes over time. They stop old bookmarks and inbound links from breaking, they move visitors from http to the secure https version, and they funnel duplicate URLs to a single canonical address. The catch is that redirects are easy to get subtly wrong — the wrong status code, one too many hops, or a rule that doubles back on itself — and those mistakes quietly cost you speed, crawl budget and ranking signals. A url redirect checker exists to make the invisible visible so you can fix it.
301 vs 302 vs 307 vs 308: the status codes that matter
Not all redirects are equal. The status code tells browsers and search engines why the URL moved, and getting it wrong sends the wrong signal to Google. These are the four you will meet most often:
- 301 Moved Permanently: the page has moved for good. Search engines transfer ranking signals to the destination and eventually replace the old URL in the index. This is the default for migrations, HTTPS upgrades and consolidating duplicates.
- 302 Found (temporary): the move is temporary, so the original URL stays indexed. Correct for short-lived changes like a geo-test or a maintenance page; wrong for a permanent move, because the destination will not inherit authority.
- 307 Temporary Redirect: the stricter HTTP/1.1 version of a 302. It guarantees the request method (GET, POST) is preserved, which matters for forms and APIs. Semantically still temporary.
- 308 Permanent Redirect: the permanent counterpart of 307 — like a 301 but it, too, preserves the request method. Increasingly used for API endpoints and modern frameworks.
The practical rule: use 301 (or 308) for anything permanent, and 302/307 only when the change truly is temporary. The most common and most damaging mistake is a 302 left in place on a permanent move — the new URL never picks up the old one’s rankings because you have told Google not to transfer them. This tool flags exactly that case so you can switch it to a 301.
Redirect chains: why one hop is the goal
A redirect chain is two or more redirects strung together: URL A redirects to B, which redirects to C, instead of A pointing straight at C. Chains build up almost accidentally over a site’s life — a page moves once, then the section is restructured, then the whole site goes HTTPS, and each change adds another hop without anyone collapsing the earlier ones.
Chains hurt in three concrete ways. First, speed: every hop is a full round trip to the server before the page even starts loading, and on mobile connections those milliseconds add up to a visibly slower experience. Second, crawl budget: search engines allocate a finite number of fetches to your site, and each redirect in a chain spends one of them on a non-page. On a large site, chains can leave real content uncrawled. Third, link equity: ranking signals pass through a redirect, but historically a little is lost at each hop, so a four-step chain dilutes the authority an inbound link should have delivered in full.
Google’s own guidance is to keep redirects to a single hop wherever possible, and it will only follow so many before deferring the rest of the chain to a later crawl. The fix is simple once you can see the chain: update the first redirect so it points directly at the final destination, then retire the intermediate rules. Run the URL through the checker again and confirm it now resolves in one step.
Redirect loops: the chain that never ends
A redirect loop is a chain that circles back on itself — A redirects to B, and B redirects back to A — so the browser bounces endlessly and eventually gives up with a “too many redirects” error. To a user the page is simply broken; to a crawler the URL is uncrawlable, which can quietly drop it from the index.
Loops almost always come from two rules that disagree. A classic pair is one rule forcing the www version while another forces the non-www version, so each keeps handing the request to the other. HTTPS rules fighting trailing-slash rules produce the same effect. Because this checker shows every hop in order, a loop is obvious — you will see the same URL appear twice — and the fix is to find the two conflicting rules and remove or reorder one so the chain terminates at a single canonical URL.
http→https and www canonicalization
Every site should serve one canonical version of each page, but there are four common entry points for the same address: http://, https://, http://www and https://www. Visitors and links arrive at all four, so you need redirects that funnel them to your chosen canonical — and the goal is to do it in one hop, not three.
A badly configured site bounces a request http → https → https://www → a trailing-slash version, four hops to reach one page. Each one costs speed and a sliver of equity. Configure your server so every non-canonical variant 301s directly to the final URL, and add an HSTS header so browsers skip the insecure http hop entirely on repeat visits. Checking each of the four variants with this tool is the fastest way to confirm your canonicalization collapses to a single clean redirect.
Server redirects vs meta refresh and JavaScript redirects
There are three ways to send a visitor from one URL to another, and they are not equivalent. Server-side redirects are the HTTP 3xx responses described above: the server answers with a status code and a new location before any page renders. Meta refresh redirects sit in the HTML — a <meta http-equiv="refresh"> tag that reloads to a new URL after a delay. JavaScript redirects run in the browser, changing window.location once the page’s script executes.
This redirect tracer follows server-side redirects, which is deliberate: those are what a crawler evaluates first and fastest, and they are the kind you should be using for SEO. Meta refresh and JavaScript redirects are slower, depend on the page rendering, and pass ranking signals less reliably — Google treats a 301 as the clearest signal of a permanent move and the client-side alternatives as weaker substitutes. If you find pages relying on meta refresh or JS to move users permanently, the right move is to replace them with proper server-side 301s, and then this tool will trace them cleanly.
How to read the results
When you trace a URL, the tool lists each hop as a numbered step. For every step you see the HTTP status code, colour-coded so a 2xx is green, a 3xx redirect is orange and a 4xx or 5xx error is red, along with the URL that hop requested and the target it redirects to. The final destination is marked clearly, and the summary shows the total number of redirects so you can judge the chain length at a glance.
The tool then flags the issues that matter: a chain longer than two hops, a temporary 302 or 307 where a permanent 301 is usually expected, an http→https upgrade, and any sign of a redirect loop. A single clean 301 to a 200 destination is the healthy pattern; anything else is worth a second look. A 404 or 410 at the end of a chain means the redirect points at a page that no longer exists, and a 5xx means the destination server errored.
Debugging a site migration
Migrations are where redirect problems multiply. Whether you are moving to a new domain, restructuring URLs, or switching to HTTPS, the plan is the same: every old URL should 301 to its closest new equivalent, in one hop, to a live 200 page. In practice, teams map the high-value URLs carefully and let the long tail fall back to a catch-all — which is exactly where chains, loops and dead-end 404s creep in.
After any migration, spot-check your most important URLs with this redirect chain checker: your top landing pages, your most-linked pages, and a sample of deep URLs. Confirm each resolves in a single 301 to a 200, with no 302s where a 301 belongs and no chains. For catching noindex and crawl directives that often break during the same migration, pair this with the bulk noindex checker, and review your crawl rules with the robots.txt generator so redirected URLs are not also blocked from being crawled.
Link equity and redirects
Inbound links are one of the strongest ranking signals, so what happens to them when the target URL moves matters enormously. A 301 passes the vast majority of a link’s authority to the new URL — Google has said PageRank is not meaningfully lost through a single 301 — but that reassurance is about one hop. String several redirects together and the risk of dilution, delay and dropped signals rises with each additional step.
This is the real cost of a sloppy redirect setup: the authority you earned from a hard-won backlink arrives weakened, or late, or not at all, because it had to travel through a chain instead of landing in one hop. Keeping redirects to a single, permanent 301 is how you make sure every link you build actually lands where it should. If you are investing in link building to grow that authority, do not let a redirect chain quietly throw part of it away — trace your money pages here first.
Redirect best practices checklist
Pulling it together, these are the rules worth applying to every redirect on your site:
- One hop, always. Point the first URL straight at the final destination; collapse any chain you find.
- 301 for permanent, 302/307 for temporary. Match the status code to your actual intent — and never leave a 302 on a permanent move.
- Redirect to the equivalent page, not the homepage. A relevant 301 preserves far more value than a blanket redirect to the root.
- Canonicalize in one step. Make http, https and www variants 301 directly to your single canonical URL, and add HSTS.
- Avoid loops. Check that your www, HTTPS and trailing-slash rules do not contradict each other.
- Re-check after every change. Trace key URLs after a migration, a CMS update or a server config change to catch regressions early.
Apply these and redirects become what they should be: invisible plumbing that keeps links alive and visitors moving, rather than a hidden tax on your speed and rankings. Paste a URL into the check redirects tool above to trace its chain and confirm it follows every rule on this list.