Test a redirect from the first request to the final page
Start with the exact URL people use, not the destination you expect. Record each response and follow its Location until you reach a terminal result or a loop. A browser's address bar shows only the ending.
General educationDefine the entry point
Copy the entire published URL, including http or https, host, path and query. A poster may show http://example.com/offer while a website links to https://www.example.com/offer. Those are different entry points and can follow different rules. If a real campaign includes personal data in the query, redact it before sharing the trace.
Entry: http://example.com/offer?utm_source=flyer
Record: status → Location → next status → final URL and pageCollect the responses
Use a network panel or a command-line client that displays headers and follows redirects with a bounded hop count. Record the numeric status and Location for each step. Resolve relative Location values against the current URL. Keep the URL fragment separate: a fragment is not normally sent in the HTTP request. A redirect checker that shows only the final address does not give enough evidence to diagnose a chain.
- Trace both GET and a method-sensitive request only when the workflow actually uses both.
- Check whether query parameters survive each hop and whether destination analytics receives them.
- Confirm the final hostname's certificate, response status and visible content.
Interpret the trace
A 301 or 308 declares a permanent move; a 302 or 307 declares a temporary one. A 404 at the end means the target is missing. A repeated URL suggests a loop, often from conflicting canonical-host or scheme rules. A chain of successful redirects can still be slow or land on the wrong campaign page.
| Trace | Next action |
|---|---|
| One redirect, correct final page | Record as expected |
| Several avoidable hops | Update the earliest rule you control to the final target |
| Loop between two hosts | Inspect competing host rules |
| TLS error on entry host | Fix certificate before relying on a redirect |
| Final page error | Repair or replace destination |
Retest after the fix
The repaired destination's own page is not enough. Repeat from the original public URL and from the variants actually in circulation. Use a fresh client if a prior 301 may be cached. Use a real network trace for a live diagnosis.
Before: /old → /intermediate → /new → 200
After: /old → /new → 200