Redirect Tracer

Redirect Tracer follows a URL’s redirect chain one hop at a time and shows you the whole journey: every URL in the chain, its HTTP status code (301, 302, 307, 308…), the redirect type, how many milliseconds each hop took, and the full response headers the server sent back. When the chain finally lands on a real page, it also detects meta-refresh and JavaScript redirects that a plain status check would miss, and grades that page’s HTTP security headers with a copy-paste value for every one you’re missing.

Why redirect chains matter

Every redirect is a round-trip: the browser asks for a URL, the server says “go here instead,” and the browser asks again. One redirect is normal and often necessary (http→https, an old URL you’ve moved). But chains (a URL that redirects to a URL that redirects again) quietly cost you on three fronts:

• Speed. Each hop is a full network round-trip before the visitor sees anything. On mobile connections a two- or three-hop chain can add hundreds of milliseconds to every visit.
• SEO. Search engines follow redirects but treat long chains as friction, and temporary redirects (302/307) don’t pass ranking signals the way a permanent 301/308 does. A page that should rank can leak authority through a sloppy chain.
• Reliability. The more hops, the more places for something to break: a mixed http/https downgrade, a loop, a dead end on a 404.

The fix is almost always the same: redirect once, permanently, straight to the final URL. Redirect Tracer makes the current chain visible so you know what to collapse.

Permanent vs temporary redirects

A 301 (and its stricter twin 308) is a permanent redirect: it tells search engines “this has moved for good: move the old URL’s ranking signals to the new one.” A 302 (or 303 / 307) is temporary: engines keep the original URL indexed because you’ve implied you’ll switch back. Using a 302 for a permanent move is one of the most common and most expensive SEO mistakes there is: you move your content but leave its ranking behind. This tool labels every hop’s type so you can catch it.

Meta-refresh and JavaScript redirects

Not every redirect is an HTTP status. Some pages redirect with a <meta http-equiv="refresh"> tag or with JavaScript (location.href = …). These work in a browser but are slower and less reliable for crawlers and bots, many of which don’t run JavaScript at all. Redirect Tracer reads the final page and flags both, so a redirect that looks invisible to a status checker doesn’t stay invisible to you.

The security-headers report card

Wherever the chain lands, Redirect Tracer grades that page’s HTTP security headers on a 100-point scale (A–F): Strict-Transport-Security (HSTS), Content-Security-Policy (CSP), X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy, and your cookie flags. These headers are free to add and defend visitors against downgrade attacks, clickjacking and script injection, and most sites are missing several. For each one you don’t have, the tool shows a sensible recommended value you can copy straight into your server or CDN config.

For AI agents

This tool exposes a plain-text endpoint designed for language models and agents:

GET https://nitrosites.com/tools/redirect-tracer/scan.php?url=<target>&format=agent

It returns a token-cheap digest of the same analysis shown on this page: the full hop list with status codes and latency, the findings, and the security-headers grade, so an assistant can answer “where does this URL actually go, and is its final page secure?” from a single request. You can also add &ua=googlebot or &ua=iphone to trace how the URL redirects for a specific crawler or device. Soft rate limits apply; results are cached briefly. No key or login required.

Frequently asked questions

What is a redirect chain?

A redirect chain is when a URL redirects to another URL that redirects again before reaching the final page. Each extra hop slows the visit and dilutes SEO signals; best practice is a single 301 straight to the destination. Redirect Tracer shows you every hop, its status code and how long it took.

What's the difference between a 301 and a 302 redirect?

A 301 is permanent: search engines transfer the old URL's ranking signals to the new one. A 302 is temporary: engines keep the old URL indexed. Use 301 for moves, 302 only when you genuinely intend to switch back. This tool labels every hop so you can see which you're using.

Are meta-refresh or JavaScript redirects bad for SEO?

They work for browsers but are slower and less reliable for crawlers than server-side redirects. Google treats them as weaker signals; prefer HTTP 301/308 redirects at the server or CDN level. Redirect Tracer detects both and flags them.

How many redirects is too many?

Aim for zero or one. Googlebot follows up to ten hops but each hop adds latency and dilutes link equity; chains longer than two are worth consolidating into a single 301.

What are security headers?

HTTP response headers like Strict-Transport-Security and Content-Security-Policy that tell browsers to enforce protections against downgrade attacks, clickjacking and script injection. They're free to add, and this tool grades which ones your final page is missing and shows the exact value to add.