Redirect Checker: Trace Redirect Chains

How to use

1. Enter the starting URL, for example the http:// or non-www version.
2. Select Check and read the chain step by step.
3. Aim for a single redirect from any old URL to the final one.

What this tool does

It follows redirects one at a time (up to five) instead of letting the HTTP library do it, so every hop is shown with its status code, Location header and time. Loops and chains that are too long are reported.

Why it matters

Each extra redirect slows the page down and wastes crawl budget. Temporary redirects (302, 307) used for permanent moves can also delay search engines in transferring signals to the new URL.

Common uses

• Checking http → https and www rules after a migration.
• Finding chains created by stacked redirect rules.

Tips

• Use 301 or 308 for permanent moves.
• Update internal links to point straight at the final URL.

Limitations

JavaScript and meta-refresh redirects are not followed; only HTTP redirects are.

Troubleshooting

• “Could not connect” or “took too long”: the site may be down, slow, or blocking automated requests. Try again later or check it in your browser.
• “Certificate could not be verified”: the HTTPS certificate is expired, self-signed or issued for another domain. Visitors’ browsers will show a warning too.
• “Private or reserved network address”: the address points to a local or internal network, which this tool never contacts.
• “Limit reached”: checks are rate-limited to keep the service free and to avoid overloading other websites. Wait a few minutes.