Redirect Checker

A check I'd use after a migration: compare the final URL with the page's rel=canonical. A redirect that lands on /page/ while the canonical says /page is a common leftover. Does it also show the http to https and www to non-www hops separately? Those two are the easiest to merge into a single 301.

Tracing every hop and labeling 301 vs 302 is exactly what I need after migrations. Loop and dead-end flags beat a “final URL only” checker. One ask: in the 10-URL batch, show hop count next to each final status so long chains stand out in one glance.

Tracing every hop and labeling 301 vs 302 is the right level of detail for a migration check. The loop and dead-end flags matter more than a simple final-URL lookup, and the 10-URL batch is enough to spot a chain that is slowing one template without turning it into a crawler. Confirming a temporary redirect that should be permanent is a concrete use I would actually run.

The 10-URL batch limit feels well sized for checking a handful of key pages after a migration, and flagging loops and dead ends is more useful than just showing the final URL. One small suggestion: showing the total hop count and a clear warning when a chain is longer than two or three would make the slow ones jump out. Do you also check how redirects behave for mobile versus desktop user agents?

Handy for smart links too. I run a /go/ redirect that sends phones to the App Store or Google Play based on user agent, so I'd love an option to set the user agent per check (iPhone, Android, desktop) and see the different paths side by side. Does it follow meta-refresh and JavaScript redirects, or only HTTP 3xx?

The positioning is clear and the landing page makes the core loop obvious in under a minute. One thing I’d test next: a short before/after sample so first-time visitors feel the outcome faster.

The 301 vs 302 labeling plus loop and dead-end flags makes this handy for migration audits. Could you add CSV export for the 10-URL batch results?

Useful beyond migrations too: affiliate links often go through a redirect on your own domain before reaching the store, and it's easy to end up with an extra hop nobody notices. Does it show the final landing URL with its query string intact? That's usually where tracking tags get dropped.

Handy for migrations. One thing that helps on audits is seeing how many hops a chain has before it settles, since long chains slow crawlers and can leak link value. Does the 10-URL batch report the final status code for each URL next to the hop count, so a bad chain is easy to spot in one table?

The hop-type labels (HTTP to HTTPS, www, trailing slash) are what make a migration report readable at a glance. One check I'd add: a flag when the final URL's rel=canonical points somewhere else, since a clean 301 chain can still land on a page that canonicalizes to a different URL. Also appreciated the note that the Googlebot option only changes the user-agent string and not the IP; that difference trips people up with bot-protection rules.

Useful for checking a migration. Does it also report 307 and 308? Next.js and many CDNs use those by default, and a 307 left where you meant a permanent move is the same mistake as a 302. It would also help to know whether it follows meta-refresh or JavaScript redirects, or only HTTP Location headers.

A case from my own static site: the host adds a 308 from /page to /page/, so every sitemap entry written without the trailing slash quietly costs a hop. Could the checker take a sitemap.xml URL and flag each entry that doesn't answer 200 directly? That's a check I'd run every week.

The before/after of a chain is what I'd use this for: pasting a staging list of 10 URLs after a domain move and seeing which ones take more than one hop. A column showing the final status code per URL would make the batch easy to scan.

Flagging chains and loops separately from the simple final-URL result is the useful part for post-migration audits. Does it show the total hop count and cumulative latency per chain, so I can tell which redirect chain is actually slowing a page?

Keeping it to a focused 10-URL batch makes this feel like a quick sanity check rather than a heavy crawler, which is exactly what you want right after a deploy. One idea: a shareable results link would make it easy to drop the before and after of a migration straight into a ticket or PR for teammates to review. Do you plan to support comparing two runs side by side to show which chains got shorter?