URL redirect checker

Online tool to check bulk URLs on validity. Trace all redirect steps with a full HTTP request report. Also, you can find a list of recommendations for improving your redirect policy.

Max 5 urls in a bulk. Enter each endpoint in a new row
πŸ’β€β™‚οΈπŸ’β€β™€οΈNo Custom Headers
πŸ’β€β™‚οΈπŸ’β€β™€οΈNo Results Yet

HTTP Redirect Checker Warnings

URL Redirects it's a simple mechanism that helps us redirect our users from one page to another. There are a lot of reasons for such redirects, such as site structure changes. Unifications of the entry point (www to non-www redirect) etc. All these types of HTTP redirects we will try to cover in a specific article later. We will update this page with a link later.

Below is a list of all HTTP redirect warnings that can be detected by our Redirect URL Checker. Also, you can find a detailed description of each warning and a way to solve it.

⚠️Response takes to long. Keep it less than 329ms

Loading time is a very important factor for a website. Typically visitors don't want to wait too long for a page loading and leave it early. According to Amazons research, each 100ms of latency cost 1% of sales for a company.

Here we talk not only about UI loading time but TTFB time. That's a mostly technical value that means time for a first byte. Our tool helps you to check TTFB time for each redirect stage.

The average HTTP redirect and TTFB time 162ms. The perfect range of redirect latency is between 81ms and 329ms. In case your redirect takes more than 329ms you will see a warning notification in response window.

⚠️Looks like redirect loop detected

Redirect loop means that one of your pages redirects to another page that finally redirects us to a start page. It causes a continuous chain of redirects. Typically browsers and some request libs have a limit for such redirects and that throws an Error. This error should affect your site in a few ways.

First of all such links should affect an SEO for your site. Such URLs can be penalized by search engines.

The second problem. Is that redirect loops rapidly increase CPU memory usage for your server. And can cause a memory leak.

The current error should be solved on the back end side. And the solution itself depends on the type of server that you use.

⚠️Redirect chain. More than 1 redirect in the chain could impact SEO

The redirect chain means the number of redirects between the entered URL and a final destination.

Only one rule here. More than one redirect step it is not ok.

Each redirect step causes traffic and page rank loss. According to Ahref Blog. A simple 301 redirect with a one-step should loss 15% of page rank. In the case of the redirect chain with 2 or 3 steps, you will lose up to 38% PR.

The main tip here is. If you cannot avoid redirect make it custom, with a direct redirect to a final page. In any other pages just avoid it. Check all internal links with redirects on your website and replace it with a final URL.

⚠️It is better to use 301 redirects. Any other types can impact SEO

Google not recommend to use any other types of redirects but 301. Avoid to use other status codes like 302 redirects, it can affect search engine indexation.

Avoid using meta redirect or javascript redirects. Such things can be ununderstandable not only for search crawlers but for real users.