URL Redirect Checker.
Trace 301, 302 & chains.
Free online URL redirect checker — instantly trace 301, 302, 307, 308 redirects, detect chains and loops, and inspect HTTP headers for every hop.
Use Cases
Who uses our URL redirect checker
From engineers debugging 301 chains to SEO teams auditing migrations, our redirect checker gives total visibility into every hop.
For Developers
See every hop. Fix it once.
Debug complex routing logic and mixed content warnings directly from your development environment.
For SEO Teams
Stop losing rankings to bad redirects.
Identify redirect chains and loops that waste crawl budget and dilute link equity.
For Marketing
Know exactly where your traffic goes.
Validate affiliate links and campaign URLs to ensure users land on the correct landing pages.
For QA
Catch redirect bugs before release.
Automate regression testing for URL migrations and site structure changes.
For API Users
Redirect tracing, fully automated.
Integrate our powerful tracing engine into your own dashboards, monitoring tools, or CI/CD pipelines with a simple REST API.
Everything in one
URL redirect checker
Trace 301 and 302 redirect chains, catch infinite loops, inspect HTTP response headers, and test with any user-agent — all in one free tool built for engineers and SEO teams.
Instant Analysis
Trace lengthy redirect chains in milliseconds. Our optimized backend engine handles complex routing without delay.
Visual Pathing
Visualize every hop, status code, and latency in the chain. Identify loops and broken links instantly.
Header Inspection
Deep dive into HTTP response headers. Analyze cookies, caching policies, and server information per hop.
User-Agent Spoofing
Test how your redirects behave for different devices and bots. Essential for mobile-first indexing and SEO.
Security Checks
Verify SSL/TLS certificates and identify insecure redirects (HTTP to HTTPS mixed content warnings).
Robust API
Automate your auditing. Integrate our powerful redirect checking capabilities directly into your CI/CD pipeline.
Redirect Checker API.
Integrate in minutes.
Our free REST API exposes the same redirect tracing engine — perfect for building custom monitoring, link-validation jobs, or CI/CD pipelines that audit 301 and 302 redirects automatically.
- check Simple REST endpoints
- check JSON response format
- check High-rate limits available
// GET /api/check // Query params: url (required), ua (optional), ignoreSSL (optional) // CORS: Access-Control-Allow-Origin: * const response = await fetch('https://www.redirectcheck.org/api/check?url=https://example.com'); const data = await response.json(); // Optional custom user agent const response2 = await fetch( 'https://www.redirectcheck.org/api/check?url=https://example.com&ua=CustomBot/1.0' ); // Success response // { // url: 'https://example.com/', // redirects: [{ from, to, status_code, duration, headers }], // final_result: { final_url, status_code } // } // Error response // { // url: 'https://example.com/', // error: true, // error_message: '...', // error_type: 'FETCH_ERROR', // redirects: [], // final_result: null // }
Runtime note: ignoreSSL=true is accepted by the endpoint for compatibility, but Cloudflare Workers cannot disable TLS verification. If you pass it, failed requests will include a note in error_message.
URL Redirect Checker FAQ
Common questions about checking 301, 302, 307, 308 redirects and fixing redirect chains.
What is a URL redirect checker? expand_more
A URL redirect checker is a free tool that traces the full path a URL travels from the address you enter to its final destination, capturing every HTTP redirect along the way. With our checker you can:
- See every hop in a redirect chain in real time
- Identify each status code — 301, 302, 303, 307, 308 — used per hop
- Detect infinite redirect loops that cause ERR_TOO_MANY_REDIRECTS
- Inspect response headers, cookies, and canonical tags for each step
- Test how a URL behaves for Googlebot, Chrome, Safari, or any custom user-agent
How do I check if a URL has a 301 redirect? expand_more
Paste the URL into the checker above and click Start tracing. Within milliseconds you'll see the full chain — the exact status code for every hop tells you whether the redirect is 301 (permanent), 302 (temporary), 307, or 308. To verify a 301:
- Enter the source URL (e.g. https://example.com/old-page)
- Look at the first row of the redirect chain — the status badge will read 301
- Confirm the destination URL matches where you expect it to land
- Use the API endpoint /api/check for automated 301 monitoring in CI/CD
What is a redirect chain and why is it bad for SEO? expand_more
A redirect chain occurs when a URL redirects through two or more intermediate URLs before reaching the final destination (e.g. A → B → C → D instead of A → D). Long chains hurt SEO and performance because:
- Each hop adds network latency, slowing time-to-first-byte for users and bots
- Google may stop following chains after several hops, leaving pages uncrawled
- Link equity (PageRank) can dissipate across multiple 301 hops
- Crawl budget is wasted on intermediate URLs instead of new content
- Mobile users on slow networks feel the cumulative latency the most
Aim for a single hop. Our checker highlights every intermediate URL so you can flatten chains to a direct A → final-destination redirect.
What's the difference between 301, 302, 307, and 308 redirects? expand_more
All four are HTTP 3xx status codes, but they behave very differently for browsers, caches, and search engines:
- 301 Moved Permanently — permanent redirect, cacheable, passes SEO equity; use for moved content
- 302 Found — temporary redirect, not cached aggressively; use for A/B tests or temporary takeovers
- 303 See Other — redirects after a POST so the next request becomes a GET; common in form submissions
- 307 Temporary Redirect — like 302 but preserves the HTTP method (POST stays POST)
- 308 Permanent Redirect — like 301 but preserves the HTTP method; recommended for permanent moves of API endpoints
Choosing the wrong code can break form submissions, leak link equity, or get pages dropped from search results. The checker shows the exact code in use so you can audit each redirect.
How do I fix ERR_TOO_MANY_REDIRECTS or a redirect loop? expand_more
ERR_TOO_MANY_REDIRECTS means a URL keeps redirecting in a cycle (A → B → A → B…) until the browser gives up. Our checker explicitly flags loops with a red banner and shows where the cycle begins. Common causes and fixes:
- HTTP ↔ HTTPS misconfiguration — make sure HTTPS rules don't redirect back to HTTP
- www vs non-www loops — pick one canonical hostname and redirect the other to it once
- Trailing-slash conflicts in your reverse proxy or framework router
- Conflicting redirect rules in Cloudflare Page Rules, Vercel vercel.json, or Nginx config
- Stale browser cookies or cache forcing the loop — try an incognito window to confirm
Can I check HTTP to HTTPS redirects and bulk-test many URLs? expand_more
Yes. The checker captures every protocol change as a separate hop so you can audit your HTTPS migration end-to-end. For checking many URLs at once:
- Use the free bulk redirect checker to test up to 100 URLs in one batch
- Confirm every HTTP URL returns a 301 to its HTTPS equivalent (not 302)
- Spot insecure intermediate hops that trigger mixed-content warnings
- Verify www → non-www (or vice versa) consolidation is consistent across the site
- Automate ongoing audits with the public /api/check JSON endpoint
