Redirect Matrix
Tests http/https and www/non-www host variants of a URL at once, follows every redirect hop, and compares where a browser and a compact set of crawler User-Agents actually end up.
Based on: RFC 9110 — HTTP Semantics
About this validation
Tests http/https and www/non-www host variants of a URL, follows every redirect hop, and compares final destinations across a browser and a compact set of crawler User-Agents using standard HTTP redirect semantics.
- Protocol / standard:
- Rules reviewed:
- Sep 6, 2026
SEOTechTests methodology: Data source: live HTTP requests performed by SEOTechTests across http/https and www/non-www host variants, following every redirect hop. Standard: RFC 9110 defines the HTTP redirect semantics being tested.
Standards and vendor-documented behavior can change. This reflects the source as last reviewed above, not a permanent guarantee.
What This Test Checks
Given a URL, this tool derives the http/non-www, http/www, https/non-www, and https/www variants (preserving the exact path and query string), requests each one with a browser profile and a compact set of crawler profiles (Googlebot, GPTBot, ClaudeBot), and follows every redirect hop rather than only the final response.
What It Flags
Redirect loops, chains that take more than one hop to reach HTTPS, an HTTPS response redirecting back to HTTP, query parameters dropped along the way, malformed Location headers, redirects to an unexpected domain, and cases where a crawler profile ends up somewhere different than a normal browser.
FAQ
What does this check that a single redirect check doesn't?
It tests all four combinations of protocol (http/https) and host form (www/non-www) for the same path and query string in one run, then compares where each one actually ends up -- the kind of check that otherwise takes several separate curl commands.
Why does it also test Googlebot and AI crawler User-Agents?
A server can legitimately (or accidentally) send a crawler to a different final destination than a browser. This tool flags that divergence as a fact -- it does not evaluate SEO intent or robots.txt.
Is losing query parameters during a redirect always a bug?
Usually worth checking, but not universally wrong -- some redirects intentionally normalize or drop tracking parameters. This tool reports the observed loss; whether it matters depends on what those parameters were for.
What counts as a redirect loop?
The chain revisits a URL it already requested during the same check, so it can never reach a final response. This is always a configuration problem.