Skip to content

Redirect Checker - Trace Redirect Chains and Status Codes

What the redirect checker shows

Enter a URL and the checker follows it one hop at a time, the way a browser or crawler would. For each hop you see the status code, the response time, where it points next, and the headers that matter for redirects: Location, Cache-Control, X-Robots-Tag, a canonical Link header, the server, the content type and whether a cookie was set.

When the chain ends on an HTML page, the checker reads the first 256 KB and looks for a meta refresh or a simple JavaScript redirect. If it finds one, it follows that too, so you see where a visitor actually lands.

You can share a check by copying the page URL. It includes the URL you tested, and opening it runs the check again.

Redirect status codes compared

Code Type Method kept? SEO effect Use it for
301 Moved Permanently Permanent No, POST may become GET Passes signals to the new URL; the new URL gets indexed A page or site has moved for good
302 Found Temporary No, POST may become GET Google keeps the old URL indexed at first; treated as permanent if it stays long enough Short-term moves, A/B tests, geo or login redirects
303 See Other Temporary No, always becomes GET Same as 302 Sending a browser to a result page after a form POST
307 Temporary Redirect Temporary Yes Same as 302 Temporary moves where a POST must stay a POST; also what browsers show for HSTS upgrades
308 Permanent Redirect Permanent Yes Same as 301 Permanent moves of API endpoints or forms that receive POST requests

"Method kept" means whether a POST request stays a POST after the redirect. For ordinary page moves this does not matter, and 301 is the usual choice. Meta refresh and JavaScript redirects are not HTTP status codes. Google can follow them, but a server-side 301 is faster and more reliable.

Why redirect chains are worth fixing

Each hop is a separate request, with its own DNS lookup and connection if the host changes. A typical chain after a few migrations looks like http://example.com/old to https://example.com/old to https://www.example.com/old to https://www.example.com/new/: three hops before the page starts loading. Point the first URL straight at the last one and visitors skip all three.

Googlebot follows up to 10 hops, so a short chain still gets indexed, and Google says 3xx redirects do not lose PageRank. The risk is in the middle hops. One of them is a 302 left over from testing, or points at a URL that later starts redirecting somewhere else, and the chain grows until something breaks. After a migration, paste the old URLs into bulk mode and check that each one is a single 301 to the right page, then run the canonical variants check to confirm http, https, www and non-www all end at the same URL.

Other things to check

Paste a bit.ly or t.co link to see where it goes before you click it, or an affiliate link to see each tracking hop and whether the final URL keeps its parameters. Switch the user agent to Googlebot, Bingbot or GPTBot and compare the result with the browser run: a different final URL can mean bot-specific redirects, geo redirects or a firewall that blocks crawlers.

Related Tools

Frequently Asked Questions

What redirect types does this tool detect?
All HTTP redirects (301, 302, 303, 307 and 308), plus meta refresh tags and simple JavaScript redirects such as window.location or location.replace on the final page. Meta refresh and JavaScript hops are labelled so you can tell them apart from server redirects.
What is a redirect chain?
A redirect chain is when one URL redirects to another URL that also redirects, for example http://example.com to https://example.com to https://www.example.com. Each extra hop adds a round trip for visitors and gives crawlers one more step to follow. The fix is to point the first URL straight at the final one.
Why does a site return 403 or 429 to the checker?
Some sites block or rate-limit requests from data centres and automated tools. The checker sends a normal browser user agent by default, but a site can still refuse requests from our server's IP address. When the last hop is a 403 or 429, treat the result with caution and try a different user agent.
How do I check how Googlebot sees my redirects?
Pick Googlebot Smartphone or Googlebot Desktop from the user agent menu. Some sites send bots to a different URL than browsers, which can cause indexing problems. The request still comes from our server, not Google's, so sites that verify Googlebot by IP address may treat it as a normal visitor.
How does loop detection work?
The checker remembers every URL in the chain. If a redirect points back to a URL it has already visited, it stops straight away and reports a loop. It also stops after 20 hops, which is well past the point where browsers give up.
Can I check many URLs at once?
Yes. Switch to Bulk mode and paste up to 20 URLs, one per line. They are checked one after another and the results can be downloaded as a CSV file. This works well for testing a list of old URLs after a site migration.