Skip to content
Devtoolry
Sign InJoin for Free

Redirect Checker

Check the HTTP status code and full redirect chain of up to 100 URLs: 301, 302, 404 and 5xx, response headers, loops and HTTPS downgrades, with fixes and CSV.

Something not working, or missing a feature? Send feedback

About the Redirect Checker

The Redirect Checker shows what happens when a browser or crawler requests a URL: every hop of the redirect chain with its status code, Location header, response time and full response headers, then the final status. Paste up to 100 URLs to audit a migration, and it flags temporary redirects used for permanent moves, chains that should be one hop, loops, HTTPS-to-HTTP downgrades and noindex headers.

Our server requests the URLs you enter, like a crawler: it reads the response without running the page's scripts, and the analysis runs in your browser. The URLs and results are not stored.

How to use the Redirect Checker

  1. Paste one URL per line: old URLs after a migration, http:// and www variants, or links from a campaign.
  2. Pick a user agent if the site treats phones or crawlers differently.
  3. Press Check and open any hop to see its response headers.
  4. Fix what the notes point out, then download the CSV as a record of the migration.

Common mistakes

  • Redirecting everything to the home page. Google treats mass redirects to an unrelated page as soft 404s. Redirect each old URL to its closest equivalent, and let pages with no replacement return 404 or 410.
  • Chains after every migration. http → https → www → new path adds up. Update old redirects to point at the final URL each time you move pages.
  • Forgetting internal links. A redirect is a fallback. Update links in your navigation, content and sitemap to the new URLs so visitors and crawlers skip the hop.

Works well with the Redirect Checker

Frequently asked questions

What is the difference between a 301 and a 302 redirect?

301 (and 308) mean the page moved permanently, so search engines replace the old URL with the new one. 302 (and 307) mean a temporary move, so the old URL may stay indexed. Use 301 or 308 for site moves, HTTPS and domain changes.

How many redirects are too many?

Googlebot follows up to 10 hops before giving up, but every hop adds a round trip for visitors. Aim for one: point every old URL straight at its final destination.

Why does HEAD show an error but the page works?

Some servers handle HEAD requests badly. The checker repeats the request with GET when HEAD returns an error, and notes it on the result. Switch on "Use GET instead of HEAD" to always use GET.

Related tools