# Redirect checker

Follow the redirect chain from the URL you enter to the page that answers, with the status code of every hop, and check that the final URL is HTTPS with HSTS and no mixed content.

Run it at https://crawlwise.dev/tools/redirect-checker: paste a public URL, no account needed. The scan runs the full CrawlWise audit and returns a private report.

## What this checker tests

- Redirects are permanent and short (`discovery.redirects`)
- HTTPS, HSTS and redirects are correct (`trust.https`)

## What the report shows

CrawlWise requests the URL you enter and records every hop until a page answers:

- the requested URL, the final URL and each redirect with its status code;
- how many hops are temporary (`302`, `303`, `307`);
- whether the final URL is HTTPS. A chain that ends on plain HTTP fails, as does a chain of more
  than three hops;
- the `Strict-Transport-Security` header and its `max-age`, and up to five subresources the page
  loads over HTTP (mixed content).

Every hop is checked before it is followed, so a redirect to a private network address stops the
scan instead of being followed.

## Common mistakes

- **Two redirects where one would do.** `http://example.com` → `https://example.com` →
  `https://www.example.com` can be a single hop to the final URL.
- **Temporary redirects for permanent moves.** Framework defaults often send `302`.
- **Redirects in internal links.** Link to the final URL so neither visitors nor crawlers pay for
  the hop.
- **HSTS that is too short to matter.** A `max-age` of a few minutes protects nobody.

## Fix it

Redirect each old URL straight to its final HTTPS address with a `301` or `308`, update internal
links and canonical tags to the final URL, and send
`Strict-Transport-Security: max-age=31536000`. The
[indexability checker](/tools/indexability-checker) shows whether the final page names itself as
canonical.

## FAQ

### What is a good redirect chain?

No redirect at all, or one permanent redirect (301 or 308), for example from http:// to https:// or from the bare domain to www. Each extra hop costs a request and some crawlers stop following after a few.

### Why does a 302 redirect get a warning?

302, 303 and 307 say the move is temporary, so search engines may keep the old URL as the canonical one. Use 301 or 308 for a move that is meant to stay.

### How many redirects are too many?

CrawlWise warns at two hops and fails at more than three. Google follows up to ten, but every hop slows the first byte for visitors and crawlers alike.

### What does the HTTPS check cover?

The final URL must use HTTPS, and the page must not load scripts, styles, images or frames over plain HTTP. HSTS should have a max-age of at least 180 days; a shorter or missing header warns.

## Related guides

- [Is your site agent-ready? A practical checklist](https://crawlwise.dev/guides/agent-ready-website-checklist.md)

---

Last updated 19 November 2026.

HTML version: <https://crawlwise.dev/tools/redirect-checker>

Every CrawlWise page in Markdown: <https://crawlwise.dev/llms.txt>
