What a redirect check actually reveals
When a server cannot or should not serve the address you requested, it can reply with a 3xx HTTP status code and a new address in the Location header. The browser requests that next address. If the next server redirects again, the process repeats until a page responds without another redirect.
A redirect checker makes those hidden responses visible. It should show the URL requested at each step, the status code returned, and the final destination. That is more useful than looking only at the address bar, which normally shows just the last URL.
Trace the URL step by step
- Copy the original link from the source that matters: a page, email, ad, QR code, sitemap, or old bookmark.
- Paste it into the Redirect Where checker. Include the full path and query string. If you omit the scheme, the checker begins with HTTPS.
- Select Trace route. The checker requests headers from each public HTTP or HTTPS address, one step at a time.
- Read the route from top to bottom. The first row is the submitted URL. The last row is the final reported destination.
- Open the final destination only if you recognize and trust it. A redirect check reports the route; it is not a security verdict about the content at the end.
How to read the result
The summary answers three different questions. Final status tells you whether the last server reported success or an error. Redirects counts the moves before that response. Total time shows how long the header requests took from the checker’s server.
| Result | Meaning | What to do |
|---|---|---|
| 200 with 0 redirects | The original URL answered directly. | No redirect work is needed. |
| 200 after 1 redirect | A common, short route reached a working page. | Confirm the status code matches the intent. |
| 200 after 2+ redirects | The page works, but visitors take an indirect route. | Update rules and internal links to skip old steps. |
| 4xx or 5xx final status | The route ends at a client or server error. | Repair the destination or point the redirect elsewhere. |
A 301 or 308 normally describes a permanent move. A 302 or 307 describes a temporary one. That distinction matters because browsers, caches, and search engines may treat the original address differently. Read the full 301 versus 302 guide before changing a rule on a live site.
What a healthy redirect route looks like
The cleanest redirect moves once from the exact old URL to the exact current URL, then ends with a successful response. For example, http://example.com/old might return 301 directly to https://example.com/new, which returns 200.
The route should also preserve anything the destination needs. If campaign parameters, language selectors, or product identifiers disappear, the final page may load while the link still fails its purpose. Compare the path and query string at each hop, not only the hostname.
Common problems a redirect check exposes
A chain
An old URL redirects to a second old URL, which redirects again. Chains often grow during repeated redesigns because each migration adds a rule without replacing earlier ones. They are slower and harder to maintain. Learn how to shorten redirect chains safely.
A loop
URL A points to URL B and another rule points B back to A. Variants can involve HTTP and HTTPS, www and non-www, or a proxy that disagrees with the application about the original scheme. A browser eventually stops with a “too many redirects” error.
The wrong final page
The technical route succeeds but lands on an irrelevant homepage, an unexpected locale, or a login screen. A 200 status means the server delivered something; it does not mean the destination is correct for the user.
A broken final response
A redirect can faithfully send every visitor to a 404 or 500. Always inspect the final status rather than assuming that a visible 301 means the job is complete.
A practical redirect audit checklist
- Test the exact old URL in both its expected and most commonly linked forms.
- Prefer one permanent hop for a permanent migration.
- Make the final URL canonical, secure, and indexable when it should appear in search.
- Update internal links so your own pages do not depend on redirects.
- Keep query parameters only when the destination uses them.
- Test on a clean browser session if cookies or authentication may affect routing.
- Recheck important redirects after CDN, proxy, CMS, or web-server changes.
A redirect checker is most valuable as a comparison tool: capture the route before a change, apply the rule, and check again. The difference tells you exactly what the change accomplished.