page contents

Let’s say you own a website that you would like to change the URL and redirect to an HTTPS. For example, your website may be, and now you want to make a change. At one point, you have wanted your visitors to go to the non-www version rather than the www version of your domain. In addition, if you follow best practices regarding security, you might want to switch from HTTP to HTTPS. The question now becomes, what should you do if you want to make both these changes? You have probably figured out that you will to redirect traffic from your current domain to your now preferred domain. But what’s the best way to do this? Is there a preferred order for completing these tasks? Where should you begin? YoasSEO has put together a short video that helps explain this. Check out the video and the short explanation below.

How to Switch from HTTP to HTTPS and www to non-www

The fact is, you should make both changes at the same time. You should redirect the HTTP link straight to the HTTPS version without the www. Keep in mind, this isn’t just as simple as setting up two simple 301 redirects. While this may sound like the most obvious of solutions, you shouldn’t use two 301 redirects to switch from HTTP to HTTPS and from www to non-www versions of your URL.

Forcing HTTPS is something that you need to test really well. There are all sorts of things in your site that probably aren’t HTTPS ready that you should know of upfront. It can be awfully difficult to get your site converted to HTTPS — even if you don’t even have ads. Now, if you do have ad services, it can be even more difficult to get your site working on HTTPS. Don’t let this get you down. Just because it can be difficult, doesn’t mean it has to be overly difficult. You should just make sure to do it in one go. There happens to be a secret option: redirect from one to the other straight away, and don’t think about anything else.

If you really can do HTTPS for everything and it works fine, make sure to add an HSTS: ‘Strict Transport Security Header’, which forces everything to be over HTTPS. And then, if the browser sees an HTTP link to your domain in the content somewhere, it will still automatically grab the HTTPS version — thus, the right one.

Pin It on Pinterest

Share This