Redirect Checker

Trace every hop of a redirect chain with status codes, Location headers and timings, and spot loops and temporary redirects.

  • Fetches public URLs
  • Free, no sign-up

Googlebot-like only changes the User-Agent header. Sites that verify Google by IP will see it is not Google.

How to use the redirect checker

  1. Enter the URL you want to trace.
  2. Optionally pick a user agent and turn on the 4 root variants test (http/https, www/non-www).
  3. Select Check redirects and follow the chain from the first request to the final page.
  4. Review the notes and suggestions, such as replacing temporary redirects or shortening chains.

Worked example

Checking https://example.com

The chain has a single hop: HTTP 200 OK from the first request, so the notes say "No redirects: the URL responds directly" and there are no suggestions.

How it works

Each hop is requested separately from our server with automatic redirects turned off, so the exact status code, Location header and time are recorded. Every Location is resolved and validated against our network safety rules before it is followed, up to 10 hops within 30 seconds. A URL seen twice is reported as a loop. 302, 303 and 307 responses are flagged as temporary.

Assumptions

  • The Googlebot-like option only changes the User-Agent header; sites that verify Googlebot by IP address will treat the request as a normal visitor.
  • Timings are from our server and include network distance.

Frequently asked questions

Should I use 301 or 302?

Use 301 (or 308) when a page has moved permanently so search engines index the new URL. Use 302 or 307 only for genuinely temporary moves.

How many redirects are too many?

Google follows several hops, but each one adds latency. Aim for one redirect at most and update internal links to point straight at the final URL.

Why test the four root variants?

http and https, with and without www, should all end at one preferred URL. Inconsistent variants can split signals and confuse visitors.

Do you store the URLs I check?

No results are stored. The URL is fetched from our server only to produce the report, and requests are rate limited per visitor to prevent abuse. Private, local and reserved network addresses are refused.

Limitations

  • Does not execute JavaScript or meta refresh redirects.
  • Some servers answer automated requests differently from browsers.
  • Limited to 30 checks per visitor every 10 minutes.