Does your site force HTTPS and redirect cleanly?
Before a visitor or search engine sees your page, they follow your redirects. This tool follows them too and tells you whether http is forced to https, whether the chain loops or drags, and whether anything drops back to insecure http.
Why redirects quietly cost you
Redirects and HTTPS are invisible when they work and expensive when they do not, and nothing on the page tells you which one you have.
Insecure pages lose trust and rank
A page that loads over http is marked not secure in the browser and quietly downranked in search. Both cost you clicks.
Every extra hop bleeds speed and equity
A redirect chain adds round trips before the page even starts, and each hop leaks a little of the ranking signal a link carries.
A loop makes the page unreachable
Two rules pointing at each other end in a too-many-redirects error. The page is simply gone until someone notices.
One site in, a fix list out
Paste your site
Your home address or a page. No sign-up, nothing installed.
It follows the redirects
The http and https versions, hop by hop, the way a browser does.
You get a ranked fix list
Anything insecure, looping, or slow, most costly first, with the fix.
What it checks
The four things that decide whether visitors reach a secure page quickly, each followed the way a browser follows them and scored by how much it costs you.
HTTPS is forced
Whether the plain http:// version redirects to https, or quietly serves an insecure page.
No downgrade
Whether any hop sends a secure URL back to insecure http, which browsers warn about.
No redirect loop
Whether the redirects settle on a final page or spin until the browser gives up.
A short, clean chain
Whether the address reaches its destination in one hop or drags through several.
Straight talk about what it cannot see
It follows the redirect chain from the address you give. It is honest about the edges of that.
It follows up to eight hops
A chain longer than eight redirects is reported as a loop, because in practice that is what a browser treats it as.
It checks the address you give
It follows http and https for that URL, not every www, non-www, or trailing-slash variant of it.
It reads the chain, not the page
It reports status codes and where each hop points, not the content of the page at the end of the chain.
It keeps the report, not your site
Your redirects are followed, checked, and thrown away. Only the report is stored, and only for you.
Make sure the front door is secure
Run it on your site right now. HTTPS and clean redirects are the cheapest trust you will ever buy. Every Growth Tool is included in one subscription: start a free trial and scan any site.
Check my site