Redirect Checker

301 is permanent; search engines treat the target as canonical. 302 is temporary; the index may stay on the old URL. 308 is also permanent and keeps the method (POST). www → apex and http → https should be one 301. Extra hops (http://www → http://apex → https://apex) mean three requests and loss.

A loop is A pointing to B and B back to A; the browser says “too many redirects”. The cause is conflicting .htaccess, plugin and CDN rules. The tool cuts the chain step by step so you see which location turns back.

If canonical points one way and 301 another, the signal splits. AMP, UTM and slash variants count as other URLs. If the certificate name and the final host disagree, the browser warns; even if the chain ends on https, an http hop leaks before HSTS. Turn HSTS on at the final HTTPS.

Each row is a status and Location. One 301 and a 200 is ideal. Four or five hops mean piled-up rules. 404 or 410 at the end means no content; the redirect “works” but SEO dies. Do not flood URLs you do not own.

Searches like “http to https redirect”, “how to redirect www”, “301 vs 302”, “too many redirects” land here. After a domain or host change, old URLs should hit the new canonical in one 301. A bulk map (old blog path → new post) comes from the sitemap; a blanket “send everything home” 301 burns rankings. A slash (/page vs /page/) is two addresses; 301 one onto the other.

CDN “Flexible SSL” turns a hop into http origin; the browser sees https, the server sees http, and cookies or mixed content break. Full (strict) and a correct certificate chain are required. This tool lists Locations seen from outside; it does not show the origin’s internal rule. After setup, run apex http, www http, apex https and www https once each. All four must land on the same 200. On a Webify cutover those four tests are the acceptance check.