Redirect Chain and HTTP Status Checker
Follow the redirects of any address hop by hop and see the HTTP status code, Location header and response time of each step. The tool flags loops, chains longer than one hop, temporary redirects that look permanent and final pages that return 404 or 5xx, and tells you what to fix. To write the rules use the 301 redirect generator; for the difference between redirect types see 301 vs 302 redirects, and for the full process see the site migration SEO guide.
Up to 10 hops are followed per address. Requests are sent from our server with a bot user agent and no cookies; private and internal network addresses are not checked.
Result (sample)
Below is a sample chain. Enter your own address and press Check.
ornek.com/hizmetlerCheck3 redirects · 513 ms200
- 301Moved Permanently120 ms · HEADhttp → httpshttp://ornek.com/hizmetlerLocation: https://ornek.com/hizmetler
- 302Found95 ms · HEADadds wwwhttps://ornek.com/hizmetlerLocation: https://www.ornek.com/hizmetler
- 301Moved Permanently88 ms · HEADadds trailing slashhttps://www.ornek.com/hizmetlerLocation: /hizmetler/ → https://www.ornek.com/hizmetler/
- 200OK210 ms · HEADhttps://www.ornek.com/hizmetler/
Final address: https://www.ornek.com/hizmetler/
Findings
- Redirect chain with 3 hops. Every extra hop slows users down and uses crawl budget.
- Hop 1 redirects http to https. That is correct; update internal links and the sitemap to the https address directly.
- Hop 2 uses 302 (temporary), but this looks like a permanent move (e.g. http → https, www or a domain change). Check it; if it is permanent, use 301 or 308.
- Hop 2 adds www. A consistent redirect to the preferred version is good; internal links should use it directly.
- Hop 3 adds the trailing slash. If internal links use the same format, this hop never runs.
- The chain has 3 separate format fixes (https, www, trailing slash). Combine them into one server rule that redirects straight to the final address.
- The final address returns 200 OK.
Recommendations
- Redirect ornek.com/hizmetler in a single 301 hop straight to www.ornek.com/hizmetler/.
- Update internal links, canonical tags and the sitemap to the final address so no redirect is needed.
- Merge the https, www and trailing slash fixes into one server rule.
- For permanent moves, use 301 or 308 instead of 302 or 307.
To prepare the server rules, use the 301 redirect generator.
Badge colours: green 2xx (success), blue 301 and 308 (permanent), amber 302, 303 and 307 (temporary), red 4xx and 5xx (error). For servers that do not support HEAD, the tool retries the same address with GET.
How to use it
- Enter an address and press Check. Switch to Bulk to check up to 10 addresses at once, one per line.
- Read the timeline: each hop shows its status code, the Location header it returned and how long it took. Blue badges are permanent redirects, amber ones are temporary.
- Fix the red and amber findings first. The recommendations tell you where each address should point in a single hop.
- After changing the rules, check again. Update internal links and the sitemap to the final addresses so no redirect is needed at all.
Frequently Asked Questions
What is the difference between 301 and 302, and which should I use?
301 (and 308) mean the page has moved permanently; Google treats them as a strong signal that the target should be the canonical address. 302 (and 303, 307) are temporary and a weak signal. Use 301 for migrations, URL changes and http to https or www moves, and 302 only for genuinely temporary situations. The details are in the 301 vs 302 redirect article.
Do redirect chains hurt SEO?
Googlebot follows up to 10 hops, so a short chain does not stop indexing, but every hop adds delay for users, uses crawl budget and is one more rule that can break. The safest approach is a single hop from every old address to the final address, with internal links pointing straight to the final address. In a migration, plan this with the site migration SEO guide.
What are 307 and 308?
307 is a temporary and 308 a permanent redirect; unlike 302 and 301 they require the browser to keep the request method (for example POST). Google treats 308 like 301 and 307 like 302. If your browser shows a "307 Internal Redirect" for http to https, that is usually HSTS working inside the browser; bots do not see it, so this tool shows what the server really returns.
Does the tool detect meta refresh and JavaScript redirects?
It detects a meta refresh tag in the HTML of the final page. Google treats an instant meta refresh as a permanent and a delayed one as a temporary redirect. JavaScript redirects only run after rendering, so the tool cannot see them. Server side 301 redirects are the most reliable option for both users and search engines.
Why do I see a different result in my browser?
Redirects can depend on the user agent, country, language, cookies or a cache. Your browser may also remember an earlier 301 or an HSTS rule. The tool sends requests from a server with a bot user agent and no cookies, which is closer to what search engine bots see. A CDN or firewall may also treat bot requests differently.
What are the limits?
Up to 10 addresses per run, up to 10 hops per address and about 30 addresses per minute. Private or internal network addresses are never checked, for security reasons. For thousands of addresses use a crawler in list mode, and generate the rules with the redirect generator.


