Welcome to the Q&A Forum

Miguel, You are quite right that a redirect chain can be caused by moving to HTTPS. The problem comes when you have redirects already in place and then you move to HTTPS. So for example: http://domain.com/location1 Redirects to http://domain.com/location2 because you have moved a piece of content. If you then install an SSL and move to HTTPS then the route becomes: http://domain.com/location1>http://domain.com/location2>https://domain.com/location2 So there are now 3 URLs involved. This is a simple example with only 3 URLs - I have seen cases where there are 5 or 6 because someone left an HTTP link on the page. I have also seen redirect loops where there is an endless chain which cannot be resolved. In that case, the page just crashes. Best practice is to scrap the first redirect and replace it with http://domain.com/location1>https://domain.com/location2> Depending on who you read there is a small loss of link juice when passing through a 301 (permanent redirect) and a 302 (temporary redirect) so it is important to have as few as possible. It also makes perfect sense to have as few calls to the server as possible. Regards Nigel