See every hop a URL takes before it loads — status codes, timings and loops — and check that the http, https, www and non-www versions of your site all end up in one place.
Follows up to 10 redirects. No login required.
A redirect chain is when a URL redirects to another URL, which redirects again before the page finally loads — for example http://example.com → https://example.com → https://www.example.com. Each hop adds a delay and can lose some ranking value. The best setup is a single 301 redirect from every old or alternative address straight to the final page.
Use 301 (or 308) when a page has moved for good, such as http to https or an old URL to a new one. Search engines then pass rankings to the new URL. Use 302 or 307 only for short-term moves.
One is ideal. Google follows up to 10 hops, but every extra hop slows the page down. If you see two or more in a row, redirect the first URL straight to the final one.
Usually two rules that contradict each other — for example the server forcing www while a CMS setting or Cloudflare forces non-www, or Cloudflare "Flexible SSL" combined with a server rule that forces https.
Either is fine. What matters is choosing one and 301-redirecting the other three versions (http/https and www/non-www) to it, so search engines see one site instead of duplicates.
Last updated: · Free tool by Regdec Enterprise
Free Web Tools