Redirect checker
Trace the redirect chain behind any URL
A redirect stays invisible until it costs something. An extra hop delays the first byte. A chain that lands somewhere unexpected sends visitors and crawlers to the wrong page. A cycle stops the browser before anything renders at all. VeriFixScan follows the address you submit, hop by hop, and reports the status code that produced each one.
Every hop, with the code that produced it
A redirect chain is a sequence of answers, not a single one. VeriFixScan records each hop as the status it returned and the address it pointed at, so a 302 sitting where a 301 belongs becomes visible instead of assumed. Two hops or fewer pass; beyond that the chain is flagged, because every extra round trip is latency a visitor pays before seeing anything at all.
A loop is not a normalisation
Most chains open with a jump from plain HTTP to HTTPS and a decision about the www prefix. That is ordinary, and it is reported as ordinary. What gets separated out is a genuine cycle — one address pointing at a second that points back at the first — which no browser ever resolves and which surfaces as a failure rather than as a slow page. Treating the two alike would flag almost every site on the internet.
The four addresses a domain answers on
Plain HTTP, HTTPS, the www prefix and the bare hostname all resolve somewhere. When they fail to converge on one origin, search engines see four sites and divide the signals among them. The variants are requested and the result says whether they land on a single address, and which one won.
What the canonical declares, beside what actually answers
A page can redirect toward one address while declaring a different one as canonical. Those two disagreeing is a quiet way to lose the ranking of a page that otherwise works perfectly. Reading the redirect and the declared canonical together is the only way to catch it.
The redirect checks that run on your site
Each of these is a real check, and each one reports the addresses and status codes it actually observed.
Redirect chain
The entry URL reaches its destination without a long redirect chain. Each hop is reported with its status and target.
Redirect loop
Detects a real cycle (A → B → A). Ordinary http→https and www normalisation chains are not loops.
HTTP → HTTPS
Plain HTTP requests are redirected to HTTPS.
www / non-www
One canonical hostname is used, the other variant redirects to it.
URL variants (www / non-www, HTTP / HTTPS)
The four canonical URL variants of the domain converge on one single origin.
Availability classification
Single classification of the entry response: accessible, maintenance, server error, DNS/TLS failure, timeout or redirect loop.
Canonical URL
Pages declare a canonical URL, which can then be compared against the address the chain really reaches.
URL consistency
Compares scheme, www variant, trailing slash, case and parameters across the URLs really fetched.
HTTPS
The website is served over HTTPS.
VeriFixScan traces the chain of the URL you submit and of the pages it crawls from there. It does not test a prepared list of old-to-new addresses after a migration, and it is not an uptime monitor: it reports the chain as it answered at the moment of the scan.
Enter your website address and VeriFixScan analyses it straight away. No account, no installation, nothing to add to your site.
Frequently asked questions
- How do I check where a URL redirects to?
- Enter the address and read the redirect chain finding. It lists each hop with the status code that produced it and the address it pointed at, ending with the URL that finally answered.
- What is the difference between a 301 and a 302 here?
- The status code of each hop is reported as observed. A 301 tells search engines the move is permanent and passes the signals along; a 302 says the original address is coming back. You are shown which one answered, not which one was intended.
- How many redirects are too many?
- Two hops or fewer pass. Beyond that the chain is flagged, because each additional round trip delays the first byte and gives search engines one more place to drop a signal.
- Is a redirect loop the same as an http to https redirect?
- No. Moving from plain HTTP to HTTPS, and settling the www prefix, are normal parts of almost every chain. A loop is a genuine cycle that never resolves, and it is classified separately from those.
- Can it check my whole redirect map after a site migration?
- No. VeriFixScan follows the chain of the address you submit and of the pages it reaches from there. Testing a prepared list of thousands of old-to-new pairs is a different job, and this is not the tool for it.