HTTP Redirect Checker
Enter a URL
About HTTP Redirect Checker
A content team spends three months building backlinks to a high-performing blog post. During a site migration, the URL changes. Someone sets up a redirect — but uses a 302 (temporary) instead of a 301 (permanent). Six weeks later, Google still has the old URL in its index, the new URL is not inheriting any of the link equity, and rankings have dropped. The site has organic traffic but a broken redirect is silently bleeding the SEO value out of it.
This is why checking redirects matters. Not just whether a URL redirects — but how it redirects, through how many hops, and whether the chain ends cleanly or spirals into a loop. The DigitalSub Pro HTTP Redirect Checker traces the complete redirect path of any URL: every hop, every status code, and the final destination. You see exactly what search engines and browsers see when they follow the chain — giving you the data to fix problems before they cost you rankings.
- What the Redirect Checker Shows
- What Is an HTTP Redirect — and Why It Exists
- Every Redirect Status Code Explained: 301, 302, 307, 308
- How Redirects Affect SEO — The Full Picture
- Redirect Chains — When One Hop Becomes Many
- Redirect Loops — The Worst-Case Scenario
- Common Redirect Configurations: Good, Bad, and Dangerous
- The www and HTTPS Redirect — Getting Canonicalisation Right
- How to Use the Tool
- Who Uses This Tool and When
- The Most Costly Redirect Mistakes
- Pro Tips for Redirect Management
- Related Tools
- Frequently Asked Questions
What the Redirect Checker Shows You
Enter any URL and the tool follows every redirect in sequence — exactly as a browser or search engine crawler would — returning the full hop-by-hop chain with status codes. Here is what a real result looks like for a URL with a typical HTTPS migration and www redirect setup.
This example reveals a 3-hop redirect chain that should ideally be collapsed to a single 301. Each extra hop adds latency and slightly dilutes link equity. The tool surfaces this instantly so you can fix it.
What Is an HTTP Redirect — and Why It Exists
Every time your browser requests a URL, the server responds with an HTTP status code — a three-digit number that tells the browser what happened and what to do next. A 2xx code (like 200 OK) means success — here is your page. A 4xx code (like 404 Not Found) means something went wrong with the request. A 5xx code (like 500 Internal Server Error) means the server itself had a problem.
A 3xx code is a redirect — the server is saying "the content you requested is not here right now; look over there instead." It sends the browser to a different URL automatically. The browser follows that new URL, and the process repeats until it hits a final non-redirect response.
Redirects are not a workaround or a hack — they are a fundamental and necessary part of how the web functions. Without them, every URL change would break instantly. Every domain migration would destroy years of SEO work. Every HTTP → HTTPS upgrade would result in millions of broken links. They are the web's built-in mechanism for handling change gracefully — but only when configured correctly.
Every Redirect Status Code Explained — 301, 302, 303, 307, 308
Not all 3xx codes are the same. The number tells you the permanence of the redirect, whether SEO value transfers, and how the browser should handle the original request method. Picking the wrong code — especially in a site migration — can cost you months of recovered ranking signals.
Moved Permanently
The gold standard for SEO redirects. Tells browsers and search engines the page has permanently moved to a new URL. Google transfers approximately 95% of link equity (PageRank) to the new URL. Browsers cache this aggressively — returning users go directly to the new URL without re-requesting the redirect.
Found (Temporary Redirect)
Tells the browser to go to a different URL temporarily — the original URL should be kept in the index because the change is not permanent. Google does not transfer link equity through a 302. The original URL stays indexed. Browsers do not cache 302s aggressively. The most commonly misused redirect code — site migrations done with 302s lose all their link equity.
See Other
Specifically designed for POST-to-GET redirects — after a form submission, the server returns a 303 to redirect to a confirmation page using GET, preventing form re-submission on page refresh. Almost never used for standard web content redirects. If you see a 303 in a redirect chain for a normal web page, it is likely misconfigured.
Temporary Redirect (Method-Preserving)
Like a 302 but with strict method preservation — a POST request redirected with a 307 must remain a POST at the new URL. The original 302 specification was ambiguous about this; 307 was created to clarify it. In modern web development, 307 is used when you need temporary redirection and the HTTP method must not change. Same SEO implications as 302 — no equity transfer.
Permanent Redirect (Method-Preserving)
The modern, stricter equivalent of 301. Permanently moves a resource while preserving the HTTP method — a POST remains a POST at the new URL. The SEO implications are the same as a 301: link equity transfers. For standard web page redirects, 301 and 308 are functionally equivalent in terms of SEO. 308 is preferred for API endpoints and REST services where method integrity is critical.
Not Found — A Missing Redirect
Not technically a redirect — but the redirect checker surfaces 404s at the end of chains because a redirect pointing to a 404 is one of the most damaging redirect configurations possible. The link equity from the original redirect is sent to a dead end. Any backlinks, internal links, or bookmarks pointing to the source URL lose all their value. Finding these in the checker output means you have broken redirect chains to fix urgently.
How Redirects Affect SEO — The Full Picture
Redirects are not neutral events for SEO. Each redirect type has specific, measurable consequences for how search engines treat the URLs involved. Understanding this distinction is what separates an SEO professional who uses redirects strategically from one who causes accidental ranking drops.
Link Equity and PageRank Transfer
When a page has earned backlinks from authoritative sites over years, those links represent accumulated "link equity" — the ranking power that flows from those sources to your page. A 301 redirect passes approximately 95% of that equity to the new URL. This is not a perfect transfer — there is always some signal loss at each hop — but for a single, clean 301, the impact is typically negligible.
A 302 redirect does not reliably pass this equity. Google treats it as a temporary state, keeps the original URL indexed, and does not consolidate the ranking signals. If someone migrates their entire website with 302 redirects — as happens more often than you would expect — they effectively disconnect all their existing link equity from their new URLs until the redirects are corrected to 301.
Crawl Budget Consumption
Search engine crawlers have a finite crawl budget for each site — a rough limit on how many pages Googlebot will crawl per day. Each redirect hop consumes crawl budget. A redirect chain with five hops uses five times the crawl resources of a direct URL. For large sites with tens of thousands of URLs, redirect chains accumulate quickly and can measurably reduce the rate at which new and updated content gets indexed. Google has confirmed it typically follows up to five redirect hops during a single crawl session — chains longer than five may not be followed at all.
Page Speed Impact
Every redirect adds a full HTTP round-trip — typically 50 to 200 milliseconds per hop depending on server location and network conditions. A single clean redirect is barely noticeable. A four-hop redirect chain adds 200–800ms of overhead before the page even starts loading. For mobile users on slower connections, this is the difference between a page that feels fast and one that feels broken. Page speed is a confirmed Core Web Vitals signal and a ranking factor — redirect chain latency compounds into measurable performance degradation at scale.
Nuclear Blast Records: Site Migration Done Right
A widely cited migration case study in the SEO community: music label Nuclear Blast migrated platforms with meticulous URL mapping and comprehensive 301 redirects for every single legacy URL. Rather than using generic redirects pointing old URLs to the homepage (a common lazy shortcut), the team created one-to-one URL maps ensuring every old URL redirected precisely to its equivalent new URL.
The result: a 227% year-over-year increase in organic traffic after the migration — a figure that stands in stark contrast to typical migration outcomes, where 20–40% traffic drops in the weeks after launch are common. The difference was entirely in redirect implementation. This is the clearest evidence in the industry that redirect configuration is not a technical nicety — it is one of the highest-leverage decisions in an SEO migration.
Redirect Chains — When One Hop Becomes Many
A redirect chain occurs when the URL you redirect to is itself a redirect, creating a sequence of hops before the final destination. Chains are almost always unintentional — they accumulate over time as a site evolves, migrates, and changes, with new redirects added on top of old ones without ever consolidating them.
How Chains Develop — A Common Timeline
A 4-Year Redirect Chain — How It Builds Up
Each migration adds a new redirect without removing old ones. The chain grows. The link equity dilutes. The latency compounds.
2021 — HTTP → HTTPS migration (1 hop, correct):
2022 — URL restructure (chain grows to 2 hops):
2024 — Platform migration without cleaning up (chain now 4 hops — dangerous):
⚠ Note the 302 in the middle — link equity stops there. And 4 hops approaches Google's crawl limit.
The solution is straightforward: regularly audit your redirect chains with this tool and collapse multi-hop chains into a single direct 301 from the original source URL to the final destination. A 4-hop chain should always become a 1-hop chain pointing directly to the 200 URL — eliminating latency, preserving maximum link equity, and staying well within Google's crawl tolerance.
Redirect Loops — The Worst-Case Scenario
A redirect loop is exactly what it sounds like: URL A redirects to URL B, which redirects back to URL A, creating an infinite cycle. Neither browsers nor search engine crawlers can resolve a loop — browsers display the "Too many redirects" error (ERR_TOO_MANY_REDIRECTS in Chrome) after following approximately 20 hops, and Googlebot gives up after 5, marking the page as uncrawlable.
The most common causes of redirect loops: conflicting rules across different layers (your CMS sets a redirect one way, your CDN sets a rule going back), www/non-www rules fighting with HTTPS rules, and CMS plugin conflicts where multiple redirect plugins apply overlapping rules. The redirect checker surfaces loops instantly — instead of following the chain indefinitely, it detects the cycle and reports the loop condition directly.
Common Redirect Configurations — Good, Bad, and Dangerous
Here are the redirect patterns the checker most commonly finds — and what each one means for SEO and site health.
↓ 301
https://example.com/page
↓ 200 OK ✓
HTTP → HTTPS in One Step
Maximum equity transfer, minimum latency, no chain. This is the target configuration for every redirect on your site.
↓ 301 (www→non-www)
http://example.com
↓ 301 (HTTP→HTTPS)
https://example.com
↓ 200 OK
3 Hops Where 1 Would Do
Works — but wastes latency and slightly dilutes equity. Collapse into a single direct 301 from any http/www variant to the final https/non-www canonical URL.
↓ 302 (should be 301!)
https://new-domain.com
↓ 200 OK
Temporary Redirect on a Permanent Move
Common migration mistake. Google keeps the old domain indexed, does not transfer link equity. Change to 301 immediately — every day it stays as 302 is a day of lost equity.
↓ 301
https://example.com/new-page
↓ 404 NOT FOUND ✗
Redirect Chain Ending in Dead URL
All link equity sent directly to a dead end. Any backlinks pointing to /old-page are now worthless. Fix the 404 or update the redirect to a valid URL.
↓ 301
https://example.com/page-b
↓ 301
→ loops back to /page-a ∞
Infinite Redirect Loop
Page is completely inaccessible to users and crawlers. ERR_TOO_MANY_REDIRECTS in browser. Googlebot gives up after 5 hops. Fix immediately.
↓ 301
https://example.com/ (homepage)
↓ 200 OK
Orphaned Content Redirected to Homepage
Technically works, but Google calls this a "soft 404" — you are sending users and crawlers to irrelevant content. Link equity is diluted. Always redirect to a topically relevant replacement page.
The www and HTTPS Redirect — Getting Canonicalisation Right
The most fundamental redirect every website needs is also the one most frequently misconfigured: the canonical domain redirect. Every site must choose one authoritative URL format and redirect all other variants to it permanently. There are four possible variants of any domain, and all four must resolve to exactly one.
The 4 Variants — Only One Should Return 200, The Rest Must 301
Check all four variants in the redirect checker. If any return a 200 that is not your chosen canonical, you have duplicate content. If any return a different status code than 301 on the non-canonical variants, your redirects are misconfigured.
Why the Order Matters — Collapsing to a Single Hop
Many sites handle the www and HTTPS redirects as separate rules: first redirect www → non-www (hop 1), then redirect HTTP → HTTPS (hop 2). This results in a 2-hop chain for users typing http://www.example.com. The correct approach is a single rule that handles all four variants directly to the canonical URL in one hop — achieved with a properly written .htaccess rule or CDN-level redirect configuration. The redirect checker surfaces immediately whether your site handles this in 1 hop or multiple.
How to Use the HTTP Redirect Checker
Enter Any URL
Paste the full URL including https:// or http://. To check canonical redirects, test all 4 variants: http/https × www/non-www.
Run the Check
Click Submit. The tool follows every redirect automatically — exactly as a browser or Googlebot would — and records the status code at each hop.
Read the Chain
Review each hop. Count the total hops. Identify the redirect types (301, 302, etc.). Check that the final response is 200 OK — not another redirect or an error code.
Fix What's Wrong
Collapse chains to single hops. Replace 302s on permanent moves with 301s. Fix redirect-to-404 issues. Eliminate loops. Re-check to confirm the fix worked.
Who Uses the Redirect Checker — and When
SEO Professionals — Site Audits
Every technical SEO audit includes a redirect check. Identifying chains, wrong redirect types (302 used as 301), redirects to 404s, and loop conditions are standard audit deliverables. This tool provides the hop-by-hop data needed to document and prioritise redirect fixes.
Developers — Post-Migration Verification
After a site migration, every URL in the redirect mapping document should be checked to confirm: the source URL returns 301 (not 302), the chain is exactly 1 hop, and the destination returns 200. Checking URLs manually in a browser cannot reliably surface chains or distinguish 301 from 302 — a redirect checker does it in seconds.
Website Owners — Diagnosing Traffic Drops
Unexplained traffic drops after a site change are frequently redirect-related. Running your most important pages through the redirect checker reveals whether they have lost their 301 configuration, ended up in a chain introduced by a plugin update, or are returning unexpected status codes that Googlebot cannot process correctly.
Backlink Auditors
When reviewing a backlink profile, high-value links pointing to redirected URLs may be losing equity through chains or wrong redirect types. Checking the redirect status of each linked URL reveals whether the link equity is flowing cleanly to the canonical destination or leaking through misconfigured hops.
Security Researchers
Redirect chains are sometimes deliberately weaponised in phishing attacks — a URL that appears legitimate redirects through multiple hops before landing on a malicious page. Security researchers use redirect checkers to trace the full chain of suspicious shortened or obfuscated URLs before visiting the final destination.
Performance Engineers
Each redirect adds latency. Performance engineers audit redirect chains as part of Core Web Vitals optimisation — specifically LCP (Largest Contentful Paint) improvement. Eliminating a 3-hop chain from the entry URL of a landing page can reduce initial load time by hundreds of milliseconds before a single byte of content is transferred.
The Most Costly Redirect Mistakes
Using 302 Instead of 301 for Permanent Moves
The most expensive, most common redirect mistake in SEO. A 302 on a permanent migration leaves Google indexing the old URL, does not transfer link equity, and means the new URL starts building authority from zero. Fix: change to 301 immediately and monitor Google Search Console for re-indexation of the new URL.
Redirect Chains From Multiple Migrations
Every platform or URL change adds a redirect layer. Five years and three migrations later, some URLs have 5–7 hop chains. These accumulate silently — nobody notices because the page still loads — but they drain crawl budget and equity continuously. Run a quarterly check and collapse all multi-hop chains to single-hop 301s.
Redirecting All Old URLs to the Homepage
The lazy migration approach: when you cannot build a proper URL map, redirect everything to the homepage. Google calls this a "soft 404" — the content signal is irrelevant to the linked keyword, the user lands on an unhelpful page, and the link equity passes to the homepage instead of to topically relevant replacement content.
Not Checking Redirects After CMS or Plugin Updates
Plugin updates — particularly SEO plugins, caching plugins, and security plugins — can modify .htaccess or CMS redirect rules, introducing new chains or overriding existing redirects. A working single-hop 301 today can become a 3-hop chain or a loop after an update. Check critical URLs after any significant update.
Leaving Both www and non-www Active (Duplicate Content)
If https://example.com and https://www.example.com both return 200 without redirecting to each other, Google sees two separate versions of your entire site. Link equity splits. Crawl budget doubles. Rankings dilute. Choose one canonical version and 301 redirect the other — without exception.
Forgetting to Remove Temporary Redirects
A 302 redirect set up for a maintenance window or A/B test six months ago is still in place today. It was never removed. The original URL is still indexed, the content is being served from the destination, and Google has not consolidated the ranking signals. Temporary redirects left in place indefinitely become permanent mistakes.
Pro Tips for Clean, SEO-Safe Redirect Management
6 Redirect Management Habits That Prevent Problems
- Test all four domain variants before and after every migration. Check
http://,http://www.,https://, andhttps://www.for your domain. All non-canonical variants should return a single 301 directly to your canonical https non-www URL. This one check catches the most common canonical redirect misconfigurations. - Build a redirect map before any migration — not after. Document every URL that exists, where it should redirect to, and the exact redirect type before touching a single server configuration. Trying to build a redirect map after a migration while rankings are already dropping is enormously stressful and almost always results in missed URLs. Treat the redirect map as a deliverable that exists before the launch date.
- Run a redirect audit quarterly, not only during migrations. Redirect chains accumulate between migrations — through plugin updates, CMS version upgrades, incremental URL changes, and A/B test remnants. A quarterly check of your most important pages (highest-traffic, most backlinks, most internal links) catches accumulation before it reaches damaging chain lengths.
- Point internal links directly to final URLs, not redirected ones. Setting up redirects is necessary for external links and bookmarks you cannot control. But internal links — your site's navigation, in-content links, and sitemap entries — should always point directly to the final URL. Every internal link that goes through a redirect wastes a tiny fraction of crawl budget and adds an unnecessary latency hop for users navigating your site.
- When in doubt, use 301. For any redirect you intend to keep for more than a few weeks, use 301. The only reasons to use 302 are genuinely temporary scenarios (maintenance windows under 48 hours, active A/B tests, time-limited geographic routing). If you set up a 302 and then forget about it, it silently prevents equity transfer indefinitely. The cost of a mistaken 301 on something genuinely temporary is minor — the cost of a mistaken 302 on something permanent is significant.
- Use Google Search Console to monitor for redirect-related index issues. The Coverage report in Search Console flags "Page with redirect" issues — pages where Googlebot discovered a redirect but the destination has problems. After any major redirect implementation, monitor the Coverage report daily for the first two weeks to catch unexpected redirect-to-error conditions before they persist long enough to affect rankings significantly.
Frequently Asked Questions
Real questions from SEOs, developers, and site owners about HTTP redirects and how to manage them.
What is the difference between a 301 and 302 redirect for SEO?
The difference is permanence — and the SEO consequences are significant.
A 301 Moved Permanently tells Google the old URL has permanently moved to the new URL. Google transfers the accumulated link equity (PageRank) from the old URL to the new one, updates its index to show the new URL in search results, and eventually stops crawling the old URL. Use this for any URL change you intend to keep indefinitely.
A 302 Found tells Google the move is temporary — the original URL may return, so keep it indexed and do not transfer ranking signals to the new URL. Google keeps the old URL in its index and does not consolidate link equity. Use this only for genuinely temporary situations: maintenance windows, short-term A/B tests, temporary geographic routing.
The mistake that costs SEOs the most: using 302 during a permanent site migration. Every day the 302 stays in place, the new URL fails to inherit the ranking signals the old URL earned. This is why checking redirect types with this tool — not just whether a redirect exists — is so important.
How many redirects is too many in a chain?
Google follows up to approximately 5 redirect hops during a single crawl session (with the ability to follow 5 more in a subsequent session). Most browsers follow up to 20 before displaying an error. The practical recommendation for SEO:
- 1 hop: Ideal. Maximum equity transfer, minimum latency.
- 2 hops: Acceptable, but worth collapsing if possible.
- 3 hops: Should be reviewed and collapsed.
- 4+ hops: Significant latency impact, crawl budget waste, and meaningful equity dilution — fix as a priority.
The cumulative latency cost is also worth considering independently of Google's limits: a 4-hop chain adds 200–800ms of delay before the page begins loading. For mobile users or pages in competitive niches where Core Web Vitals scores matter, this is a measurable performance penalty.
My site shows ERR_TOO_MANY_REDIRECTS — what causes this and how do I fix it?
This error means your site has a redirect loop — URL A redirects to URL B which redirects back to URL A (or through a longer chain back to a URL already visited). Chrome gives up after approximately 20 hops and displays this error. Googlebot gives up after 5.
Common causes:
- Conflicting www rules: A rule forcing www in one place and a rule removing www in another, both firing simultaneously
- HTTP/HTTPS conflict: A server-level redirect to HTTPS conflicting with an application-level redirect back to HTTP
- CMS + CDN conflict: Your CMS has one redirect rule, your CDN (Cloudflare, etc.) has a conflicting rule — together they create a loop
- Multiple redirect plugins: Two WordPress redirect plugins both active and applying conflicting rules
- HTTPS misconfiguration: SSL certificate not properly installed, causing the HTTPS version to redirect back to HTTP
To diagnose: use this redirect checker and trace the chain — the loop will show where the cycle begins. Disable redirect layers one at a time (CDN → CMS → .htaccess) to isolate which layer is creating the conflict. Fix the conflicting rule at the source.
Does HTTPS migration require 301 redirects, and will I lose rankings?
Yes — every HTTP URL must 301 redirect to its HTTPS equivalent. This is non-negotiable for maintaining rankings during an HTTPS migration.
Will you lose rankings? Done correctly, the answer is essentially no — with a minor caveat. A clean 301 redirect passes approximately 95% of link equity to the new HTTPS URL. There is a small signal loss per hop, but for a single-hop HTTP → HTTPS redirect, the practical impact on rankings is negligible. Google explicitly supports HTTPS migrations and actively rewards HTTPS as a ranking signal (confirmed since 2014).
Rankings typically fluctuate mildly in the 2–4 weeks after an HTTPS migration as Google processes the 301s and updates its index. After this stabilisation period, sites with properly implemented HTTPS migrations routinely see rankings return to (and often exceed) pre-migration levels, with the added benefit of the HTTPS ranking signal. The key is ensuring every HTTP URL has a corresponding 301 — use this tool to verify the redirects are correctly configured before and after launch.
Can redirect chains affect page speed scores?
Yes — directly and measurably. Each redirect requires a complete HTTP round-trip: the browser sends a request, receives a 3xx response with a Location header, then sends a new request to the redirected URL. Each round-trip typically adds 50–200ms of latency depending on server proximity and network conditions.
A 4-hop chain adds 200–800ms before the browser even begins downloading the final page. For a site targeting a 2.5-second LCP (the threshold for a "Good" Core Web Vitals score), an 800ms redirect chain consumes nearly a third of that budget before any content loads.
Google's PageSpeed Insights explicitly flags "Avoid chaining critical requests" as a performance issue, and Lighthouse audits include "Avoid multiple page redirects" as a diagnostic item. Eliminating redirect chains is therefore both an SEO recommendation (for equity transfer and crawlability) and a Core Web Vitals optimisation — two SEO benefits from one fix.
What is a "soft 404" and how does it relate to redirects?
A soft 404 occurs when a URL returns a 200 OK status code but the content signals to Google that the page does not really contain meaningful content for that URL — the most common case being a redirect to the homepage for URLs that no longer exist.
When you redirect thousands of old product or article URLs to your homepage using 301, each redirect technically "works" — the browser reaches a valid 200 page. But Google's quality systems recognise that the homepage content is irrelevant to what the old URL was about. Google identifies these as soft 404s and typically does not pass meaningful link equity through them, treating them similarly to 404 errors for indexing purposes.
The correct approach: redirect each old URL to the most topically relevant replacement page on your site. If an old product page was about red running shoes, redirect it to your new red running shoes page or your running shoe category — not your homepage. This passes link equity appropriately and serves users who arrive from old bookmarks or links with useful, relevant content.
Is the HTTP Redirect Checker free to use?
Yes — 100% free with no account, no sign-up, and no usage limits. Check as many URLs as you need, as frequently as you need. This applies to all 47 free tools on DigitalSub Pro — there is no premium tier and no paywall on any feature.