Redirect chain checker.
Follow real 301, 302, 307 and 308 responses from URL to destination, one hop at a time. Understand loops and insecure HTTPS downgrades.
See the route your visitors take.
Enter a URL to inspect 301, 302, 303, 307 and 308 responses with real hop data, status codes and safe target URLs.
REDIRECT EVIDENCE
Remove unnecessary URL detours.
Redirects can help preserve old links when paths or domains change. But long chains add extra network trips and may make it harder for search engines and people to reach a destination.
This checker calls the Site Discovery Engine redirect-inspection API. It shows only observed HTTP HEAD responses and resolved destinations. Blocked requests, loops or missing HTTP responses are marked incomplete rather than inventing intermediate redirects.
Submit an HTTP or HTTPS page without credentials or a custom port.
Review per-hop status, Location header, resolved target and last observed response.
Check loops, long chains or HTTPS downgrades and export the findings.
FREQUENT QUESTIONS
Understanding HTTP redirects.
What is the difference between 301 and 302?
301 is a permanent redirect; 302 is temporary. Similarly, 308 is permanent and 307 temporary, and the latter pair preserve request methods.
Does this checker perform a Googlebot crawl?
No. It makes a bounded, unauthenticated HTTP HEAD request through the existing safe engine. A server can respond differently to GET, HEAD or browser navigation.
Can I inspect private sites or local IPs?
No. Both the public input and each redirect target must pass the engine's public-network safety policy. The tool will not follow redirects to private or link-local addresses.
What does a redirect loop mean?
The chain points back to an already visited URL. Fix server or application rules to provide a terminating destination.
Do redirects guarantee search rankings?
No. A short, correct redirect strategy can improve clarity, but ranking and indexing depend on many additional signals.
SITE MIGRATIONS & SEO