Free Website Redirect Checker — Trace Every 301 and 302 Hop Instantly
You changed a URL six months ago. You set up a redirect. You moved on.
Then someone tells you their link to your site shows a blank page. Or your SEO dashboard shows a page losing rankings it held for two years. Or Google Search Console flags a URL that should have been forwarded months ago as returning a 404.
Redirect & SEO Auditor
Trace HTTP hops and analyze meta data instantly.
You go check the redirect. It’s not working. Actually — it never worked properly. It was a 302 instead of a 301. Or the redirect chain has four unnecessary hops. Or there’s a loop that sends the browser back and forth until it gives up.
These problems are invisible unless you specifically look for them. And looking for them manually — checking every URL in a browser, reading server response headers, tracing hop chains — takes time and technical access that most people don’t have readily available.
This free website redirect checker fixes that. Paste any URL, click Audit, and see every redirect hop traced in real time — status code, server, HSTS security flag, and final destination metadata including page title and canonical URL. No login. No signup. Results in seconds.
Expert Personal Experience
“Look, on the surface, this might seem like a very minor thing, but it is actually incredibly important. Most people completely ignore it, completely unaware that their entire website’s stability and ranking rely on it. I am sharing this directly from my personal experience so you can understand what is truly critical and what pitfalls to avoid.
When I was optimizing my own website’s SEO, I had extensively interconnected my pages using internal links. However, due to certain structural updates, I had to change a specific page URL. I didn’t realize or remember that every single internal link pointing to that old URL would instantly break. This oversight triggered broken link errors across my site, causing my search rankings and organic traffic to tank drastically. The moment I diagnosed this disaster, I immediately worked on a solution and engineered this dedicated tool for my users, so you can instantly audit and detect broken links before they destroy your traffic.”
Pro Tips:
“Here is a pro-tip from my side: if you are using WordPress alongside the Rank Math SEO plugin, it features a built-in ‘Redirections’ module. Whenever you update an old page with new content or change its URL slug, simply navigate to that section and input your old URL and the new destination URL.
By doing this, your organic traffic remains completely safe, your link equity stays intact, and everything seamlessly redirects behind the scenes. Just make sure to always select the 301 Permanent Redirect option!”
What Does the GetCalcBase Redirect Checker Actually Do?
This tool doesn’t just tell you whether a redirect exists. It traces the entire redirect chain — up to six hops — showing you everything that happens between the URL you entered and the page that ultimately loads.
For each hop in the chain, you see:
- The URL at that hop — the exact address being resolved at each step
- HTTP status code — whether it’s a 200 (success), 301 (permanent redirect), 302 (temporary redirect), 307, 308, or anything else
- Server information — what server software is handling the response (nginx, Apache, Cloudflare, etc.)
- HSTS security status — whether the Strict-Transport-Security header is present, indicating proper HTTPS enforcement
- X-Frame-Options header — whether the page is protected against clickjacking
- Cache-control directive — how the response is being cached
At the final destination (200 status), you additionally see:
- Page title — the meta title extracted directly from the HTML
- Open Graph image — the OG image used for social shares
- Canonical URL — what the page declares as its authoritative version
This combination makes it one of the most comprehensive free redirect checking tools available — covering not just redirect status but the SEO and security headers at every step of the chain.
Step 4 — Identify and Fix Issues Look for chains with more than one redirect hop. Look for 302s where 301s should be. Look for loops (where the chain leads back to an earlier URL). Look for missing HSTS headers on HTTPS pages. Each of these is a specific, fixable problem.
How to Use the Redirect Checker — Step by Step
Step 1 — Enter Your URL Paste any full URL into the input field. Include the full protocol — https://example.com/page or http://old-domain.com/old-page. If you’re checking a short URL or affiliate link, paste the short version — the tool will follow every hop to the final destination.
Step 2 — Click Audit URL The tool sends a server-side request to your URL with redirect following disabled — meaning it reads each redirect step individually rather than jumping straight to the end. This is what reveals the full hop chain.
Step 3 — Read the Results Each hop appears as a card with the URL, status code, and server details. If HSTS is present, a green checkmark shows. If the page is the final destination (status 200), you also see the page title, OG image, and canonical URL.
Understanding HTTP Status Codes — What Each One Means
When the tool shows you a status code, here’s exactly what each one tells you:
200 — OK
The page loaded successfully. This is what you want at the end of any redirect chain. If you see 200 at the first hop, there’s no redirect at all.
301 — Moved Permanently
The resource has permanently moved to a new URL. Search engines update their index to the new location and transfer the majority of link equity (PageRank) from the old URL to the new one. This is the correct choice for permanent URL changes, domain migrations, and HTTP-to-HTTPS transitions.
302 — Found (Temporary Redirect)
The resource has moved, but only temporarily. Search engines keep the original URL in their index and do not transfer ranking signals to the destination URL. This is correct for A/B testing, seasonal promotions, and maintenance pages. Using a 302 when you mean 301 is one of the most common and costly redirect mistakes in SEO.
307 — Temporary Redirect (Strict)
Like 302, but the browser must use the same HTTP method for the redirect request. Useful for POST forms and API endpoints where changing the method would break the functionality.
308 — Permanent Redirect (Strict)
Like 301, but method-preserving like 307. The page has permanently moved, and the browser keeps the same HTTP method. The modern spec-compliant version of 301.
404 — Not Found
The URL doesn’t exist. If you encounter a 404 in a redirect chain, the chain is broken — users and search engine bots following that path hit a dead end. This is critical to fix immediately.
500 — Internal Server Error
Something went wrong on the server. If a redirect target returns 500, the redirect is broken at the destination rather than in the chain itself.
301 vs 302 vs Canonical Tag — Which to Use When
This is the question that causes more SEO confusion than almost any other redirect topic. Here’s the clear answer:
The key distinction: A redirect physically sends users to a new URL — the old one stops being visible to them. A canonical tag keeps both URLs accessible while telling search engines which version to prioritize in rankings.
If visitors should only ever see one URL, use a redirect. If both URLs need to remain live but you want to avoid duplicate content penalties, use a canonical.
Use a 301 when:
- A page has permanently moved to a new URL
- You’re migrating a domain to a new domain
- You’re consolidating multiple URLs into one
- You’ve switched from HTTP to HTTPS
- A URL structure has permanently changed
Use a 302 when:
- A page is temporarily unavailable (maintenance)
- You’re A/B testing content at a different URL
- You’re doing geo-based or device-based routing temporarily
- The original URL will return in the future
Use a canonical tag when:
- You want both URLs to remain accessible
- You have duplicate content across multiple URLs (e.g., product pages accessible from different category paths)
- You have tracking parameters creating URL variations (example.com/page vs example.com/page?ref=email)
- You have print-friendly or AMP versions of pages
Crawl budget: Search engines have a finite amount of crawling they’ll do on any given site. Every extra hop in a redirect chain consumes crawl resources. On large sites with many redirects, this can meaningfully affect how frequently and completely search engines crawl your content.
How to fix a redirect chain: Update the first redirect to point directly to the final destination, bypassing all intermediate hops. If A → B → C → D, set A → D directly. Remove B and C from the chain entirely.
What Are Redirect Chains and Why Do They Hurt Your Site?
A redirect chain is what happens when URL A redirects to URL B, which redirects to URL C, which redirects to URL D. Instead of getting to the destination in one step, the browser (and search engine crawler) makes multiple additional requests just to reach the final page.
Why redirect chains are a problem:
Performance: Every additional hop adds latency. Each redirect requires a new DNS lookup, TCP connection, and HTTP request-response cycle. On a decent server, that’s 50–150ms per hop. Chain four redirects together and you’ve potentially added half a second before the page even begins loading. Google’s Core Web Vitals (particularly LCP — Largest Contentful Paint) are sensitive to this kind of pre-load delay.
Link equity dilution: When other websites link to your old URL, that link carries ranking value. Each redirect in the chain between that linked URL and your final destination leaks a small amount of that value. One redirect: negligible loss. Five in a chain: meaningful degradation of ranking signals reaching the final page.
Comparison: GetCalcBase Redirect Checker vs. Other Tools
| Feature | GetCalcBase | Other Tools 1 | Other Tools 2 | Other Tools 3 |
|---|---|---|---|---|
| Full redirect chain trace | ✅ Up to 6 hops | ✅ Up to 10 hops | ✅ Yes | ✅ Yes |
| HTTP status code display | ✅ Per hop | ✅ Per hop | ✅ Yes | ✅ Yes |
| HSTS header check | ✅ Per hop | ✅ Yes | ❌ No | ❌ No |
| Final page title extraction | ✅ Yes | ❌ No | ❌ No | ❌ No |
| Canonical URL check | ✅ Yes | ❌ No | ❌ No | ❌ No |
| OG image preview | ✅ Yes | ❌ No | ❌ No | ❌ No |
| Server header display | ✅ Yes | ✅ Yes | ❌ No | ❌ No |
| No login required | ✅ Always | ✅ Yes | ✅ Yes | ✅ Yes |
| 100% free | ✅ Yes | ⚠️ Limited free | ✅ Yes | ✅ Yes |
The combination of redirect chain tracing with final-page SEO metadata (title, canonical, OG image) in a single free tool is what makes this checker genuinely different from most alternatives.
Redirect Checker Checklist — Run This After Every Site Change
- Check all primary pages after any URL structure change
- Verify HTTP → HTTPS redirects complete in one hop, not two or three
- Confirm www and non-www versions redirect to your canonical domain
- Check that 301 is used for all permanent redirects (not 302)
- Verify no redirect chains exceed two hops
- Look for redirect loops (circular chains) using the hop trace
- Confirm HSTS header is present on HTTPS pages
- Check canonical URL matches your intended page URL at the final destination
- Verify affiliate links reach the correct merchant destination
- Run the checker on all URLs mentioned in high-traffic external links
Key Benefits of Using a Redirect Checker Regularly
Catch problems before Google does A broken redirect that Google discovers during a crawl means a page loses its ranking position, potentially permanently. Finding it first means you can fix it before it affects traffic.
Verify migrations are complete After any site migration, running your most important URLs through the redirect checker confirms every redirect is working exactly as intended — correct status code, correct destination, correct hop count.
Protect link equity The ranking value accumulated in old URLs flows to new URLs through proper 301 redirects. Verifying those redirects are properly configured protects the SEO investment in your content.
Improve page speed Every unnecessary redirect hop adds latency. Identifying and removing intermediate hops in chains directly improves your page load time — which affects both user experience and Core Web Vitals scores.
Security verification The HSTS check at each hop confirms your HTTPS implementation is correctly enforced at the server level — not just via a redirect.
How Does the Tool Work Technically?
The redirect checker uses WordPress’s server-side wp_remote_get() function with redirect following disabled ('redirection' => 0). This means:
- It sends an HTTP request to your URL
- It reads the response code and headers from that step
- If the response is a 3xx redirect, it reads the
Locationheader to get the next URL - It repeats the process for the next URL in the chain
- It continues until it reaches a 200 response or hits the maximum of 6 hops
This server-side approach means the tool sees exactly what a search engine crawler sees — not what a browser sees. Browsers often cache redirects and skip hops that have been cached. The tool makes a fresh request at each step, showing the actual server response.
At the final 200 response, the tool additionally parses the HTML body to extract:
- The
<title>tag - The
<meta property="og:image">tag - The
<link rel="canonical">tag
This gives you SEO visibility at the destination — confirming the page has a title, that its canonical URL matches what you expect, and what image it shares socially.
For affiliate link auditing: Affiliate links often pass through multiple redirect hops before reaching the merchant. Each hop is a potential point of failure — and extra hops mean slower landing pages. Trace your affiliate chains to understand exactly where your traffic is going and how many hops it takes to get there.
When checking a suspicious link: Before clicking an unknown URL in an email or message, trace it with the redirect checker to see where it actually leads. If it chains through unexpected domains or leads somewhere other than what the anchor text suggests, it’s a red flag.
When Do You Need a Redirect Checker?
During a site migration: When you’ve moved pages, restructured URLs, or switched domains, every redirect needs to be verified. A redirect that looks correct in your CMS might chain unnecessarily or point to the wrong destination. Check systematically before and after migration.
After installing an HTTPS certificate: The transition from HTTP to HTTPS creates redirect requirements for every page. Verify that your HTTP URLs are redirecting cleanly to HTTPS in one hop, and that the HSTS header is present.
When diagnosing ranking drops: If a page that previously ranked well starts losing position, a broken or misconfigured redirect is often the cause. Check whether the URL is returning the right status code and whether any redirect chain has grown unexpectedly.
Before publishing content with old backlinks: If you’re relaunching a URL that previously existed and had backlinks, verify that the redirect from the old URL to the new one is a 301, not a 302 or nothing at all.
How to Set Up Redirects on Your Server
Apache (.htaccess)
# Single page 301 redirect
Redirect 301 /old-page https://example.com/new-page
# HTTP to HTTPS (301 permanent)
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
# www to non-www (or vice versa)
RewriteCond %{HTTP_HOST} ^www\.example\.com [NC]
RewriteRule ^(.*)$ https://example.com/$1 [R=301,L]NGINX
server {
listen 80;
server_name example.com www.example.com;
return 301 https://example.com$request_uri;
}
server {
listen 443 ssl;
server_name example.com;
location = /old-page {
return 301 /new-page;
}
}PHP
<?php
// 301 Permanent Redirect
header("HTTP/1.1 301 Moved Permanently");
header("Location: https://example.com/new-page");
exit();
// 302 Temporary Redirect
header("HTTP/1.1 302 Found");
header("Location: https://example.com/temp-page");
exit();
?>Server-level vs plugin redirects: Apache and NGINX redirects happen before your CMS loads — they’re faster by 200 to 500ms compared to plugin-based redirects that require spinning up WordPress (PHP, database connection, all plugins) just to process a redirect. For high-volume redirect lists, always prefer server-level configuration.
Common Redirect Problems — What to Look For
Redirect Loops
A redirect loop happens when a URL redirects to another URL that eventually redirects back to the first one. The browser makes requests in circles until it gives up and displays an error — typically “Too many redirects” or ERR_TOO_MANY_REDIRECTS.
Common causes:
- Misconfigured .htaccess rules that conflict with each other
- WordPress plugins applying redirect rules that contradict server-level rules
- HTTP-to-HTTPS redirect rules that trigger on the HTTPS URL as well
How to fix: Open your .htaccess or server configuration and look for conflicting redirect rules. Check that your HTTPS redirect rule only fires when the current protocol is HTTP (RewriteCond %{HTTPS} off).
Using 302 Instead of 301
The second most common redirect mistake after chains. A developer sets up a temporary redirect, forgets to update it to permanent, and months later your ranking signals aren’t flowing to the new URL because search engines think the move is temporary.
How to identify: Run the URL through the redirect checker. If you see a 302 for a permanent URL change, it needs to be updated to 301.
HTTP Not Redirecting to HTTPS
Your site is on HTTPS, but the HTTP version isn’t properly redirecting. Users who type http:// or follow an old HTTP link land on an insecure version of your page. This also creates a canonical URL problem — two versions of the same page accessible at different URLs.
The correct setup: http://example.com → https://example.com (301, one hop). Not: http://example.com → http://www.example.com → https://www.example.com (two hops unnecessarily).
WWW vs Non-WWW Inconsistency
https://example.com and https://www.example.com are technically different URLs to search engines. If both versions load the page without redirecting to a canonical version, you have duplicate content. One version should 301 redirect to the other.
The redirect checker shows you whether your domain enforces this redirect and in how many hops.
Missing HSTS Header
HSTS (HTTP Strict Transport Security) tells browsers to always use HTTPS for your domain, even if someone types http://. Without it, the first visit after a browser cache clear goes through HTTP before being redirected to HTTPS — a brief window of insecurity. The tool flags whether HSTS is present on each hop.
Frequently Asked Questions (FAQs)
What is the difference between a 301 and 302 redirect?
A 301 tells search engines the move is permanent — they update their index and transfer ranking signals to the new URL. A 302 tells search engines the move is temporary — they keep the original URL indexed and don’t transfer rankings. Using 302 for a permanent change means your new URL won’t inherit the SEO value of the old one.
How do I check if my redirect is working correctly?
Paste the old URL into this redirect checker. The tool shows every hop and the final destination. Confirm the status code is 301 (for permanent) or 302 (for temporary), that the destination URL is correct, and that the chain completes in one hop rather than multiple.
What is a redirect chain and how do I fix it?
A redirect chain occurs when URL A → B → C → D instead of A → D directly. Fix it by updating the first redirect to point directly to the final destination, bypassing all intermediate URLs.
Do redirects hurt SEO?
A single correctly implemented 301 redirect does not hurt SEO — Google has confirmed that 301 redirects pass full PageRank. What hurts SEO is redirect chains (multiple hops that dilute link equity), using 302 instead of 301 for permanent changes, and broken redirects that lead to 404 errors.
What is HTTPS redirect and why does it matter?
An HTTPS redirect sends all HTTP traffic to the secure HTTPS version of your site. It should be implemented as a 301 and should complete in one hop. Without it, HTTP and HTTPS versions of your pages are treated as separate URLs, creating duplicate content and splitting ranking signals.
How many hops is too many in a redirect chain?
Google’s John Mueller has said Google won’t follow a redirect chain more than five hops when crawling. Two hops should be your maximum target. One hop — straight from old URL to final destination — is always the cleanest solution.
Conclusion — Know Where Every URL Actually Goes
Redirects are invisible by default. They happen in milliseconds, behind the scenes, without any visible indication to the user that anything has changed. That invisibility is their strength — and their biggest risk.
A misconfigured redirect silently loses ranking signals for months. A redirect chain quietly adds latency to every page load. A loop displays an error that sends users away from your site completely.
The free website redirect checker at GetCalcBase makes the invisible visible. Every hop, every status code, every server header, and the SEO metadata at the final destination — all shown clearly, in one scan, with no login required.
Check your redirects today. Fix what’s broken before it becomes a bigger problem.
Content prepared for GetCalcBase.com — Developer Tools Category Tool: Website Redirect Checker | SEO & HTTP Auditor HTTP status code definitions based on RFC 7231 and RFC 7538 specifications
Important Disclaimer
This redirect checker tool is designed for informational, diagnostic, and educational purposes. It performs server-side HTTP requests to the URLs you enter. Only check URLs you own or have permission to audit. The tool traces up to 6 redirect hops and extracts publicly available response headers and HTML metadata from the final destination. No user data or checked URL data is stored after each session.
What the Get Calculator Base Community Says
Average Rating: 4.9/5 based on our beta users
