A redirect is not just “working” or “broken.” The real question is what chain a URL follows, which status code is used, and where the request finally lands. This page is built for that inspection step. Paste a page URL with the full scheme, run the check, and review the redirection result directly on the page. It is especially helpful when you are validating migrations, canonical URL changes, protocol rewrites, or campaign links that may pass through multiple hops before reaching the destination.
Use this checker after a site migration, when moving from HTTP to HTTPS, when normalizing trailing slashes or www handling, or when validating that old campaign links still resolve correctly. It is also useful for SEO audits, because redirect quality affects crawl efficiency, indexing, and link equity transfer. If you want to inspect the response headers that sit behind the redirect behavior, continue into Check Server Status.
https://.The checker requests the submitted URL and reports how the server responds. A clean permanent move usually shows a permanent redirect before landing on the canonical destination. A temporary redirect may be appropriate for short-lived routing changes, but it is often a sign to investigate further when used in places that should be permanent.
Practical interpretation matters more than memorizing codes. A single redirect can be acceptable. A long chain usually is not. Every extra hop adds latency and increases the chance of unexpected behavior for crawlers, browsers, or third-party tools.
A team migrates a site from old product paths to new SEO-friendly URLs and uses the checker to confirm each legacy path lands on the intended replacement.
A marketer tests a campaign link to verify that the redirect does not break UTM parameters or land on a generic homepage.
A developer checks both the non-www and www versions of a page to make sure only one canonical version survives.
A useful working habit is to keep one known-good sample beside the real input. If the tool behaves the way you expect on the sample first, you can trust the larger run with much more confidence and spend less time second-guessing the output later.
When the result will affect production content, reporting, or a client handoff, save both the input assumptions and the final output in the same note or ticket. That makes the workflow reproducible and turns the page into part of a documented process instead of a one-off browser action.
It also helps to make one small change at a time when you are troubleshooting. Changing a single field, option, or value between runs makes it obvious what affected the result and prevents accidental over-correction.
A 301 signals a permanent move. A 302 signals a temporary redirect. The correct choice depends on intent, but permanent canonical changes usually should not stay temporary.
Usually, yes. The bigger concern is a chain with multiple hops or an unexpected destination.
Because chains add friction for crawlers and users, and they make migrations harder to validate cleanly.
After you confirm the redirect behavior, document the tested source URL and the final destination so the fix stays auditable. Then inspect the broader response context with HTTP Response Codes or use your crawl and sitemap workflow to catch similar paths at scale.
Web Services are like teenage sex. Everyone is talking about doing it, and those who are actually doing it are doing it badly.