What is a Redirect Checker?
One URL often bounces through several redirects — http to https, apex to www, tracking layers, then the page. Every hop adds latency, and messy chains leak SEO signal and occasionally loop.
This checker follows up to ten hops, recording each URL, status code and response time, so you see exactly what browsers and crawlers experience.
How to use the Redirect Checker
- Enter the starting URL.
- Press Trace Redirects.
- Read the chain top to bottom — the last row is where users finally land.
Frequently asked questions
What is the difference between 301 and 302?
301 is permanent (search engines transfer ranking to the target); 302 is temporary (they keep the original URL indexed). Use 301 for moves that will not be undone.
How many redirects are acceptable?
Ideally one (http→https or apex→www combined). Two is common. More than three is worth cleaning up for speed and SEO.
What causes a redirect loop?
Two rules pointing at each other — commonly a CDN forcing https while the origin redirects back to http. The chain view makes the cycle obvious.
Do redirects hurt SEO?
A single clean 301 is fine. Long chains dilute signals and slow crawling — search engines may stop following after several hops.