How to Move From HTTP to HTTPS Without Harming SEO [Easiest Guide]

thumbnail

What is HTTP in computing? Well, in this post I will try to clarify the doubts you have about what is HTTP / https. Still, hey, there is Wikipedia for definitions so I will focus on how to integrate https without entering a very technical plane so that We all understand each other.


Are there differences between HTTP / HTTPS?

I will explain simply what is the https in computing.

The https protocol is an encrypted worldwide communications protocol, which provides security to the classic HTTP, eliminating possible attacks and to protect users against man-in-the-middle attacks. Historically it has been used in payment platforms, email and secure connections, since the end of 2010. Nowadays there are numerous blogs and other websites that have decided to go to https given the communications that Matt Cutts gave in which “he would like that https to be part of the algorithm. We already know that Google always thinks of the user first, and security is a basic and necessary point, which is why I consider that all eCommerce, virtual store, blogs and others should have https implemented.

Advantages and disadvantages SSL and https:

Advantages of https:

To have the https, an SSL certificate is required, there are free ones of good quality, in addition to pointing out that the certificate will cause a delay in the loading time because you have to make the request, but for your peace of mind indicate that it is insignificant and that once in https we can go to HTTP / 2 as long as our server allows us, this is something they do and we will notice a load optimization.

Also already in the present and for the future, search engines show a poster of an unsafe site for all HTTP web sites, and no, I don’t want to be scared of navigators.

Disadvantages of https:

If things are not done carefully, we can end up indexing our website twice in Google with the disaster that this can mean.

One whole afternoon can take you, and it is already your thing to know if you have the time and value.

Process

Difficulty : basic / medium level
Time: 1h
Requirements: check with your server first if you have free SSL and if they work https and what HTTP / 2 protocol (only the ALPN version is optimal in most search engines)

Plugins and links:

Free SSL Certificate: As we have Bluehost web hosting we have access to Let’s Encrypt, a free SSL certificate that is installed in a click and they do everything (the rest of mortals you can go to the official website of Let’s Encrypt and get one )
Plugins: SSL insecure content fixer (solves mixed content) you can also do it by hand like me if you are not afraid to go crazy and end up talking to the blind, which is rolled up more than me …: P
Varnish (my only plugin cache and you can check my enviable results at the end of the post)
https://www.whynopadlock.com/ (verify mixed content)
https://tools.keycdn.com/http2-test verify the HTTP / two protocol

Procedure: We always backup with backup (we backup). Except if you are a customer of Bluehost that they already do it to you every day hehe so it is a pleasure.

  1. We install the SSL certificate that our hosting provides us.
  2. We must define that the URL of the web is with https. In WordPress administration go to Settings -> General and put the URL of the web with https in WordPress Address (URL) and Site Address (URL) (currently it should be this URL with HTTP)
  3. To force the use of SSL, we add in the htacces at the beginning. (HTTP domain without www to https domain without www)

RewriteEngine On
RewriteCond% {ENV: HTTPS}! On [NC]
RewriteRule ^ (. *) $ Https://yourdomain.com/$1 [R = 301, L, NE]

You also have the option of implementing the Really Simple SSL plugin, but we hate putting unnecessary plugins, or asking me your specific case;)

  1. We verify in the browser that our HTTP is redirected to https
  2. We enable SSL insecure content from the smallest option, and we are checking in the URL to verify mixed content. We climb progressively until we see that everything is OK.
  3. We thank Webempresa, that although it may not be your hosting, they are still those who based on tickets and much care has guided us in this adventure

OK, we already have https, but no, we are not done.

  1. Now we go to the search console and add two more properties that will not be necessary to verify if they were already with the HTTP.
  2. We add a property, just as we did with the two HTTP versions, with and without www. In total, we should have 4,
  1. Then we link Analytics with our preferred https version from the gearwheel to the right.
  2. We delete the sitemap in the old version of our search console and add the sitemap with https for the new
  3. We go to Robots.txt and modify the link we have to the HTTP sitemap and put the https.

And now, yes! We are done

Notes: Remove the sitemap in the old search console version, I do not know if it is wasting time, but if in doubt, I was sailing at full speed to do so.

Back To Top