Best Redirect Checker Tools 2027: 6 Picks, 69 Chains Traced
The best redirect checker tools for 2027, free and paid, plus 69 real redirect chains traced hop by hop: 9 used a temporary code and 7 needed more than one hop.
Kazi Khalid Hasan Tamim · BugViso Team
11 min read
The best redirect checker for 2027 is curl or the free script below for a quick hop-by-hop trace, Chrome DevTools for redirects that depend on cookies or JavaScript, Search Console's Page indexing report for what Google saw, and a site crawler such as BugViso for redirects hiding in your own links. A good checker shows every hop and its status code, not just the final page.
We traced 69 real redirects, all from links in our own blog posts that now point somewhere else. 62 resolved in one hop, but 7 needed two or three, and 9 hops used a temporary code (302, 303 or 307) where the move looked permanent. None of that shows up if your tool only reports the final URL.
By the end you will know which redirect checker to use for each job, which status codes send which signal to Google, and how to trace any list of URLs for free.
Data used: the 69 external links in bugviso.com's 276 Markdown posts that returned a redirect when we re-checked every outbound link on 2026-11-16. Each was traced hop by hop with the script in this post (no automatic following, desktop Chrome user agent, 20-second timeout). Tool facts come from each vendor's own documentation, fetched the same day. We make BugViso, one of the tools listed.
What 69 Real Redirect Chains Looked Like
Most redirects are a single clean 301, but about one in ten adds a hop or uses a temporary code. These are the 69 chains, all on well-known documentation and product sites.
| Measure (69 redirected URLs) | Count |
|---|---|
| Resolved in 1 hop | 62 |
| Needed 2 hops | 6 |
| Needed 3 hops | 1 |
| Ended on a 200 page | 69 |
| Moved to a different host | 14 |
| Moved to a different path on the same host | 53 |
| Only a trailing slash or query changed | 2 |
| Status codes across all 77 hops | Hops |
|---|---|
| 301 Moved Permanently | 62 |
| 308 Permanent Redirect | 6 |
| 302 Found | 5 |
| 307 Temporary Redirect | 3 |
| 303 See Other | 1 |
Every chain ended on a working page, so a "final URL only" checker would call all 69 fine. The trace tells a different story: 7 chains made the browser and Google's crawler do extra round trips, and 9 hops used a code Google treats as temporary.
What Each Redirect Code Tells Google
A 301 or 308 tells Google the move is permanent and to show the new URL; a 302, 303 or 307 says it is temporary and to keep showing the old one. That's the split in Google's own redirects and Google Search guide.
| Code | Meaning | Google treats it as | Use it when |
|---|---|---|---|
| 301 | Moved permanently | Permanent | A page has moved for good |
| 308 | Permanent redirect, keeps the method | Permanent | A permanent move where POST must stay POST |
| 302 | Found | Temporary | A short-term move, such as a sale page |
| 303 | See other | Temporary | After a form post, pointing to a result page |
| 307 | Temporary redirect, keeps the method | Temporary | A short-term move where the method must stay |
The method rules come from the HTTP standard, RFC 9110; MDN's redirections guide explains them in plain terms. Google's crawlers follow up to 10 redirect hops by default, according to its HTTP status code documentation, but every hop costs time for users and crawl budget for you.
The 6 Best Redirect Checkers
| Tool | Best for | Shows every hop | Price |
|---|---|---|---|
curl -IL | A fast trace of one URL from a terminal | Yes | Free |
| The script below | Tracing a list of URLs with a verdict per chain | Yes | Free |
| Chrome DevTools Network panel | Redirects that depend on cookies, login or JavaScript | Yes, with "Preserve log" | Free |
| Search Console Page indexing report | Which of your URLs Google sees as redirects | No, lists the redirecting URL | Free |
| BugViso site audit | Redirects and loops in the links across your whole site | Flags redirect loops and broken targets | First report free |
| Your server or CDN config | The source of truth for what you set up | n/a | n/a |
curl: the fastest one-URL check
curl -sIL https://example.com/old prints the headers of every hop, so you see each status code and Location. It is on every Mac, most Linux machines and recent Windows. Add -A "Mozilla/5.0" when a site serves bots differently from browsers.
The free script: a list of URLs at once
The script in this post traces any number of URLs without following redirects automatically, prints each hop, and gives a one-line verdict per chain: OK, number of hops, temporary, loop or broken. It's the tool we used for the table above.
Chrome DevTools: redirects a server-side tool can't see
Some redirects only happen in a browser: after a cookie banner, on login, or through JavaScript. Open DevTools, tick Preserve log in the Network panel, and load the page; each redirect appears as its own row with its status code. A JavaScript redirect shows up as a 200 followed by a new navigation, which no header-based checker can detect.
Search Console: what Google recorded
Search Console's Page indexing report lists URLs as "Page with redirect" when Google found that they redirect, and those URLs aren't indexed. That is expected for old URLs. It becomes a problem when a URL you want indexed shows up in that list, which usually means an internal link or sitemap still points at it.
BugViso: redirects inside your own links
BugViso's link check visits every internal and external link and image on each crawled page and flags 404s, redirect loops and server errors, alongside a check that the HTTP version of your site redirects to HTTPS. It finds the problems you cause yourself: internal links that point at old URLs. Where others go further: it doesn't print a hop-by-hop chain for every link; use the script for that.
Your server or CDN config: fix it at the source
A checker tells you what happens; your redirect rules tell you why. When you find a two-hop chain, the fix is almost always one rule in the server, CDN or framework config that points the old URL straight at the final one.
How to Fix the Redirects a Checker Finds
Fix redirects in three passes: flatten chains, correct temporary codes, then update the links that trigger them. In that order, each pass makes the next one smaller.
- Flatten chains. If A → B → C, change A's rule to go straight to C. Keep B → C for anyone who still links to B.
- Use permanent codes for permanent moves. A page that won't come back gets a 301 or 308, not a 302.
- Update your own links. Internal links, canonicals, hreflang tags and sitemaps should point at the final URL, so the redirect is only a safety net for outside links. The guide on finding and fixing redirect chains and loops covers this step in detail.
- Recheck outbound links. Sites you link to move too, as our 69 chains show. Our backlink checker guide shows the same re-check from the other side.
Run It Yourself: Trace Every Redirect Hop
This script traces each URL hop by hop without auto-following, stops at 10 hops like Googlebot, detects loops, and prints a verdict. It uses only Python's standard library.
#!/usr/bin/env python3
"""Trace every redirect hop for one or more URLs: status code, next URL, and a verdict.
Usage: python3 redirect_trace.py <url> [more urls ...]
"""
import http.client
import sys
from urllib.parse import urljoin, urlsplit
PERMANENT, TEMPORARY = {301, 308}, {302, 303, 307}
def trace(url, max_hops=10): # Googlebot follows up to 10 hops
hops, seen = [], {url}
while len(hops) < max_hops:
p = urlsplit(url)
conn = (http.client.HTTPSConnection if p.scheme == "https" else http.client.HTTPConnection)(p.netloc, timeout=20)
try:
conn.request("GET", (p.path or "/") + (f"?{p.query}" if p.query else ""),
headers={"User-Agent": "Mozilla/5.0 (redirect-trace/1.0)"})
r = conn.getresponse()
status, location = r.status, r.getheader("Location")
except OSError as e:
hops.append((type(e).__name__, url))
return hops
finally:
conn.close()
hops.append((status, url))
if status not in PERMANENT | TEMPORARY or not location:
return hops
url = urljoin(url, location)
if url in seen:
hops.append(("LOOP", url))
return hops
seen.add(url)
hops.append(("TOO MANY", url))
return hops
for start in sys.argv[1:]:
hops = trace(start)
redirects = [h for h in hops if isinstance(h[0], int) and 300 <= h[0] < 400]
final = hops[-1][0]
verdict = ("OK" if not redirects and final == 200
else "LOOP" if final == "LOOP"
else f"{len(redirects)} hop(s)" + (", temporary" if any(h[0] in TEMPORARY for h in redirects) else "")
+ ("" if final == 200 else f", ends in {final}"))
print(f"{verdict:28} {start}")
for status, url in hops:
print(f" {status} {url}")A real run on two of our own redirects, unedited:
$ python3 redirect_trace.py http://bugviso.com/ https://www.bugviso.com/pricing
1 hop(s) http://bugviso.com/
308 http://bugviso.com/
200 https://bugviso.com/
1 hop(s) https://www.bugviso.com/pricing
308 https://www.bugviso.com/pricing
200 https://bugviso.com/pricingBoth HTTP-to-HTTPS and www-to-apex resolve in one permanent hop, which is the target for every redirect on a site. The script reads server responses only, so it can't see JavaScript or meta refresh redirects; use DevTools for those.
How BugViso Finds Redirect Problems Across a Site
BugViso's link validation checks every link and image it finds on each crawled page, internal and external, and flags 404s, redirect loops and server errors with the page they were found on. The crawl runs in a real browser, so links injected by JavaScript are included.
The security checks confirm that the plain HTTP version of your domain redirects to HTTPS, and the canonical checks look at each page's canonical tag alongside. Each finding lands in the ranked fix list and the PDF, and scheduled re-scans show whether a fix held after the next deploy. The site crawl feature page shows how the crawl works.
Frequently Asked Questions
What is the best free redirect checker?
For one URL, curl -sIL in a terminal is the fastest free option and shows every hop. For many URLs, the free Python script in this post traces each one and gives a verdict. For redirects that need a browser, such as those after login or a cookie banner, use the Network panel in Chrome DevTools.
How many redirects are too many?
Aim for one hop. Google's crawlers follow up to 10 redirect hops, but each extra hop adds a round trip for users and wastes crawl budget. In our sample of 69 real redirects, 7 needed two or three hops, all of which could be flattened to one.
Is a 301 or 302 better for SEO?
Use a 301 (or 308) when the move is permanent: Google then shows the new URL in results. A 302 tells Google the move is temporary, so it keeps the old URL. Using a 302 for a permanent move can leave the wrong URL in search results.
Do redirects lose PageRank?
Google says 301 and other permanent redirects don't cause a loss in PageRank. Chains still cost time and crawl budget, and a broken hop loses everything, so keep redirects short and point your own links at the final URL.
How do I check redirects for a whole website?
Crawl the site with a tool that follows every link and reports redirects and loops, such as BugViso, then trace the problem URLs hop by hop with the script in this post. Also export Search Console's "Page with redirect" list and check that none of those URLs are ones you want indexed.
The Redirect Rule That Prevents Most Problems
Every redirect should be one permanent hop to a working page, and none of your own links should need it. Trace your top URLs with the script, flatten anything longer than one hop, and run a BugViso audit to find the internal links still pointing at old addresses.
Written by
Kazi Khalid Hasan Tamim · BugViso Team
Kazi writes BugViso’s guides on website audits, Core Web Vitals, technical SEO, accessibility and AI search. The data in them comes from audits BugViso runs in a real Chromium browser, including our 219-site study of website health.
Summarise with AI
Open this guide in your assistant.
Follow BugViso
New guides and audit data as we publish them.
AI visibility tracker
Is your brand in AI answers?
See how often AI assistants mention you, cite your site and rank you against your competitors.
- ChatGPT
- Gemini
- Perplexity
- Claude
- AI Overviews
See where your site stands
Run a free BugViso audit for SEO, speed, accessibility and AI search readiness — with fixes you can ship today.