Practical example
An old HTTP URL should ideally reach the canonical HTTPS page in one permanent step while preserving required query parameters.
Redirect Checker
Enter a URL to trace every redirect hop, status code, response time, and final destination. Use bulk mode to check multiple URLs at once.
Optional: check up to 20 URLs, one per line.
What is a redirect checker?
A redirect checker follows a URL step by step and shows every HTTP redirect hop before the final destination. It helps you see whether a page uses 301, 302, 303, 307, or 308 redirects.
This is useful when testing SEO migrations, campaign links, short URLs, affiliate links, canonical URL changes, HTTP to HTTPS redirects, and old URLs that should point to new pages.
Check 301 redirects
Verify that permanent redirects use the expected 301 status and lead to the correct final URL.
Find redirect chains
See every hop in a redirect chain so you can remove unnecessary steps and reduce latency.
Bulk check URLs
Paste multiple URLs to test redirects for migrations, campaign links, or website audits.
How to check a redirect
- Paste a URL into the URL field, including http:// or https:// when possible.
- Click Trace Redirects to follow each redirect hop.
- Review the status code, target URL, response time, and final destination.
- Use Bulk URLs when you need to check a list of redirects during a migration or audit.
What to look for in a redirect chain
- A 301 status usually means a permanent redirect, while 302 is usually temporary.
- Long redirect chains can slow pages down and waste crawl budget.
- Redirect loops prevent users and crawlers from reaching the final page.
- HTTP to HTTPS and non-www to www redirects should usually resolve in as few hops as possible.
- Campaign and UTM links should preserve their tracking parameters through the final URL.
Related redirect and URL workflows
After checking redirects, you may also need to inspect tracking URLs, HTTP headers, DNS records, SSL setup, or sitemap URLs.
Related guides
Learn the workflow behind this tool and what to check next.
HTTP debugging
How to debug redirects and HTTP status codes
A practical workflow for checking redirect chains, understanding 301 vs 302, diagnosing 404 and 500 responses, and confirming the final URL.
Read guide
Technical SEO
Redirect checks for a safe SEO migration
A practical migration workflow that protects users and search signals while domains, protocols, paths, or platforms change.
Read guide
Analytics
How to build clean UTM campaign URLs
A simple naming workflow for utm_source, utm_medium, utm_campaign, utm_content, and utm_term that keeps analytics reports readable.
Read guide
Redirect checks before a launch or migration
Follow the complete chain to verify that users and crawlers reach one stable, canonical destination without avoidable hops.
Final destination
Confirm the last URL is the intended HTTPS, hostname, locale, and path version rather than an intermediate or error page.
Status semantics
Use permanent redirects for lasting moves and temporary redirects only when the original URL is expected to return.
Chain length
Replace multi-hop paths with a direct redirect where possible to reduce latency, crawl waste, and migration ambiguity.
Query preservation
Check whether required campaign, filter, and application parameters survive the redirect without creating duplicate URLs.
A practical example, an edge case, and a maintainer note
Edge case
A redirect may loop only for a specific scheme, hostname, cookie, or user agent, so one successful desktop request is not conclusive.
Maintainer note
I review every Location value and status code; the final 200 response can hide a slow or SEO-damaging chain.
Related tools
You may also find these tools useful.
HTTP Status Code Lookup
Look up HTTP response codes such as 404, 301, 302 and 500 instantly.
Network & Web
›
HTTP Headers Parser
Parse raw HTTP headers into JSON and readable key-value pairs.
Network & Web
›
URL Parser
Parse URLs and query parameters into structured parts instantly.
Network & Web
›
DNS Lookup / IP & Domain Info
Check DNS records, reverse DNS, and IP/domain details instantly.
Network & Web
›
Robots.txt Tester / Generator
Analyze and generate robots.txt rules online.
SEO & Webmaster
›
Redirect Checker FAQ
What is a redirect chain?
A redirect chain is a sequence where one URL redirects to another URL, which may redirect again before the final destination.
What is the difference between 301 and 302 redirects?
A 301 redirect usually means the move is permanent. A 302 redirect usually means the move is temporary.
Can this tool detect redirect loops?
Yes. The checker stops when it sees a URL repeat in the same redirect path and reports a redirect loop.
Can I bulk check redirects?
Yes. Paste up to 20 URLs in the bulk field, one URL per line, and run a grouped redirect check.
Does this validate SEO redirects?
It shows the redirect path, status codes, timing, and final URL. You still need to decide whether those redirects match your SEO migration plan.