Use the Redirect Tracker to trace single or batch public URL redirects hop by hop with status codes, Location targets, URL deltas, headers, final URL, timing, and SEO cleanup signals.
Privacy note: this tool uses a server request for public network checks; do not enter private URLs. How privacy works
A redirect tracker shows whether the first public URL reaches the expected canonical destination directly or takes extra hops.
Input
http://example.comOutput
Final URL, status code, redirect count, timing, and hop-by-hop Location headersBatch mode helps SEO and engineering teams spot redirect chains, loops, dropped query strings, and broken final URLs before a migration goes live.
Input
https://old.example.com/pricing
https://old.example.com/docs
https://old.example.com/contactOutput
A comparison table with grade, redirect count, final URL, timing, and top cleanup issue for each URLPoint the old pattern directly to the final canonical URL instead of chaining page rules.
Example
If incoming requests match:
Hostname equals old.example.com
Then:
Static redirect to https://www.example.com/$1
Status code: 301
Preserve query string: enabledPlace redirects in configuration so old URLs resolve directly to the final destination.
Example
{
"redirects": [
{
"source": "/old/:path*",
"destination": "/new/:path*",
"permanent": true
}
]
}Use a forced permanent redirect only when you are sure it should override existing files.
Example
/old/* /new/:splat 301
http://example.com/* https://www.example.com/:splat 301!Collapse protocol, host, and path changes into one redirect where possible.
Example
RewriteEngine On
RewriteCond %{HTTP_HOST} ^old\.example\.com$ [NC]
RewriteRule ^(.*)$ https://www.example.com/$1 [R=301,L,QSA]Prefer an exact server block redirect over proxying through the old application first.
Example
server {
listen 80;
server_name old.example.com;
return 301 https://www.example.com$request_uri;
}This is a server-assisted public URL check. LocalTools sends only the public URL to its API and blocks local, private, reserved, and credentialed URLs before following redirects.
How LocalTools handles local and server-assisted toolsHow to inspect 301, 302, 307, and 308 redirects before a migration, cleanup, or canonical URL change.
A technical SEO hub for checking redirects, response headers, metadata, robots.txt, URL parts, and launch-blocking crawl issues.
A practical launch checklist for CSP, HSTS, X-Frame-Options, Referrer-Policy, Permissions-Policy, CORS, and cross-origin isolation headers.
A redirect tracker follows a public URL from the first request through every HTTP redirect until it reaches the final URL, then reports each hop, status code, Location target, timing, and cleanup issue.
Yes. It tracks 301, 302, 303, 307, 308, and other 3xx responses, then labels permanent and temporary redirects so you can audit migration and canonical rules.
Yes. Batch mode accepts multiple public URLs and returns a comparison table with grades, redirect counts, final URLs, timing, and the top issue for each trace.
No. Local, private, reserved, and credentialed hosts are blocked before the request, and every redirected destination is checked before another hop is followed.