Canonical drift
Check whether the redirect path still lands on the intended final URL.
Documentation
Compare two redirect chains with normalized hop diffs, final destination checks, and launch-ready change tracking.
Overview
Use Redirect Diff when you want to compare the hop sequence for two public URLs before launch.
Check whether the redirect path still lands on the intended final URL.
Spot when a redirect chain crosses between hosts or schemes.
Review redirect changes before a site goes live.
Supported inputs
Walk through it
Workflow
Use this flow when you want to compare the hop sequence for two public URLs.
Workflow
Use this flow when the destination or status code changed and you need a quick review.
What you get
Redirect chains are normalized into comparable hop lines.
Final URL, status, and host changes help you spot drift quickly.
A normalized patch is available when you need to share the result.
Avoid these mistakes
Use public URLs for redirect inspection so the server can fetch them safely.
Always confirm the final URL and response status, not just the first redirect.
Use Accept-Language when redirects vary by language or region.
Glossary
This section translates the most technical labels on the page into plain language so you can interpret the output without opening another tab.
A redirect hop is one step in the chain from the starting URL to the final destination.
The final URL is the last destination reached after the redirect chain finishes.
Scheme drift means the chain changes between protocols such as HTTP and HTTPS.
Host drift means the chain ends on a different hostname than the one you expected.
A normalized diff compares the important redirect-chain details in a stable format so differences are easier to review.