A redirect checker traces the path a URL actually takes before it settles on a final page — every 301, 302, 307 and 308 hop, the HTTP status code and Location header at each step, whether each hop runs over HTTPS, and what the final URL returns. Paste any URL or bare domain into this redirect chain checker and it follows the whole chain from our servers — the same way Googlebot does — then renders it as a hop-by-hop timeline with a summary of the redirect count, final status and final content type. It's free, requires no signup, and results appear in your browser in a couple of seconds.
Redirects fail quietly, and the failures are expensive. A migration that stacks http → https → www → trailing-slash becomes a three-hop chain that slows every visit and wastes crawl budget. A 302 left on a permanent move tells Google the old URL is coming back, so it keeps the wrong URL indexed. A chain that dead-ends in a 404 throws away every backlink pointing at the original URL. And a redirect loop takes the page down completely — browsers give up with ERR_TOO_MANY_REDIRECTS and crawlers abandon the URL. None of these show up when you just load the page; the browser hides the hops. Checking the raw HTTP headers per hop is the only way to see them.
Use this URL redirect checker whenever you touch redirect rules: after a migration, before launching a campaign URL, or when auditing the legacy URLs your best backlinks still point at. It's the one-URL-at-a-time version of what Black & Gold SEO runs across your entire site — crawling every URL, flagging every chain, loop and misused 302, and shipping the fixes rather than just listing them.
How to use it
- 1
Paste the URL you want to trace
A full URL or a bare domain both work — the tool normalizes it and follows the chain. The highest-value URLs to check: old URLs from a site migration, the targets of your strongest backlinks, campaign/short links, and every http:// and www/non-www variant of your homepage. Or click the example link to prefill http://github.com and watch a real-world HTTP-to-HTTPS chain resolve.
- 2
Read the summary strip first
Three numbers up top: how many redirects fired, the final HTTP status, and the final content type. Zero redirects with a 200 is the ideal for a canonical page. One hop is normal for legacy URLs. Two or more is a chain worth collapsing — and anything ending in a 4xx or 5xx means the redirect is pointing at a dead page.
- 3
Walk the chain hop by hop
Each hop is a card: the status code badge (amber for 3xx redirects, green for 200, red for errors), the exact URL, and a lock indicator showing whether that hop was served over HTTPS. Between hops you see the raw Location header from the response — the same http header a crawler reads to decide where to go next.
- 4
Act on the warnings
Amber callouts flag the problems that matter: long chains, temporary redirects (302/307) sitting on what look like permanent moves, hops that fall back to insecure http://, and chains that end somewhere other than a healthy 200. A red callout means a loop — fix that immediately, because the URL is effectively down.
- 5
Collapse chains at the source
The fix is almost never 'add another redirect' — it's editing the original rule so every variant points directly at the final URL in exactly one hop. Update your server config (or CDN rules) so http://, www, and old paths each 301 straight to the canonical destination, then re-run the check to confirm a single hop. Also update internal links so they skip the redirect entirely.
The thresholds that matter in 2026: Google follows up to 10 hops in a redirect chain before it gives up and reports a redirect error in Search Console, and browsers bail at around 20 — but performance falls apart long before that. Every hop is a full network round trip, commonly 100–300ms on mobile, paid before a single byte of your page renders. The practical rule is one hop maximum from any URL that earns traffic or links. The classic offender is the stacked migration: http://example.com → https://example.com → https://www.example.com → https://www.example.com/ is three hops that should be one rule sending every variant directly to the canonical form.
On the 301 vs 302 question: since 2016 Google has said no PageRank is lost through any 3xx redirect, so the old '301s leak 15%' folklore is dead. What still differs is canonicalization. A 301 or 308 is an unambiguous instruction — index the destination, drop the source. A 302 or 307 says the move is temporary, so Google may keep the old URL indexed and delay consolidating signals onto the new one, sometimes for months. If a move is permanent, use a permanent code. One more gotcha: if you check a URL in Chrome DevTools and see a 307 you never configured, that's usually the browser's internal HSTS upgrade, not a real server response — which is exactly why a server-side redirect checker like this one shows you the truth a crawler sees instead.
Two failure modes deserve special paranoia. First, redirecting retired pages en masse to your homepage: Google treats irrelevant redirects as soft 404s, so the link equity you were trying to save evaporates anyway — redirect each old URL to its closest living equivalent instead. Second, redirect targets that rot: a chain that ended in a 200 last year can end in a 404 today because someone deleted the destination. Your most-linked legacy URLs should be re-checked after every restructure, because they're the pipes your backlink authority flows through. A redirect checker run takes seconds; a quarter of lost equity from a silent 404 chain does not come back quickly.
More free SEO tools
SERP Snippet Preview
Preview how your title and meta description appear in Google results, with live pixel-width and character limits.
Meta Tag Generator
Build copy-paste title, description, canonical, Open Graph and Twitter Card meta tags with a live preview.
Schema Markup Generator
Create valid JSON-LD structured data for Organization, LocalBusiness, Article, FAQ, Product and Breadcrumb.
See all free SEO tools or compare Black & Gold SEO vs other platforms.