What this detects, and what it cannot. We follow standard HTTP redirects (301, 302, 303, 307, 308) and HTML meta refresh redirects, recording each hop from our server. We cannot follow JavaScript redirects (for example
window.location), because that needs a real browser, so a chain may continue past where we stop. Some sites block or rate-limit automated requests, which can show as "unreachable" or a 429 even though a browser loads them fine. We will not follow a redirect to a private or internal address. Nothing about your check is stored. Redirects are not just an SEO detail: an unexpected hop to another domain can be the first sign of a hijacked link or an open-redirect flaw, so if something here looks wrong, talk to us.
// What this means for your business
Every extra hop costs speed, ranking and trust
Long or broken redirect chains slow your site, leak SEO value, and quietly break links in emails and ads. The wrong kind of redirect can even hand visitors to an attacker. Keeping redirects clean, correct and monitored is part of running a healthy, secure web presence, which is the kind of work we do for small Canadian businesses, as one team you can actually call.