Translation of the website into https: 7 times measure, 1 time cut!

Translation of a website to https

It is, in General, can be done? Any site can be translated to https?

First, you need to understand the possibility of the transfer of the site to https (considered the most popular option - a certificate free Let's Encrypt). That can prevent:

problem: hosting, hosting website, does not give/does not install such certificates (if such exist:)

solution: there is always the possibility to issue a certificate directly to the certification center and install it on your hosting by adding entries manually, and of technical support in this case to help.

problem: hosting multiple sites on one admin and non-core domains are aliases for whom the ssl certificate issuance is impossible

solution: for the main site release is possible, but you will need to use a modified redirecting to a file .htaccess for bonding, and to translate the alias to a secure Protocol, one solution is to make it NOT alias.

problem: the domain has subdomains

solution: need the possibility of issuing separate certificates for each subdomain OR issuance of the certificate Wild, which also applies to the subdomains (up to 99).

problem: the site has the content use data from other sites, not converted to https

solution: wait until all the other sites will switch to a secure connection, or reject this content

OK, figured out - move to https is possible. What's next? - SSL certificate

Secondly, order and install ssl certificate:

  • hosting nice and friendly - can 1 click to order and to bind the certificate to the domain (literally click on a couple buttons)
  • hosting or the situation is slightly more complicated, order ssl themselves (services complete) and upload to the hosting (beginners are better not to try to do it ourselves).

If the site reprulation of an online store, a free certificate will not work.

And that's all my site is already on https? - No! The hardest thing to come... Custom website to work

Thirdly, to customize the site to work on a new Protocol and correct handling of references.

A check-list of the translation of the website into https:

Settings the admin panel for switching to https Protocol: does the time and complexity depends on the admin (somewhere a somewhere a little more). For MODX REVO for two system settings link_tag_scheme (value - 1) server_protocol (set to https), carefully with contexts (! if you are using multiple contexts, to change the configuration of each context to https).

To set up a redirect in .htaccess. In all rules, explicitly indicating the Protocol change to https, and add gluing two mirrors to http and https. And this must be done carefully, because on one hosting rule can work correctly, and the other to cause a circular redirect.

Variations of the rules of gluing several (solved by trial and overkill :). Need access to the file .htaccess via ftp or through the hosting, in order to cancel in case of failure), the most commonly used:

Option 1

RewriteCond %{ HTTPS} =off
RewriteRule (.*) https://%{ HTTP_HOST}%{ REQUEST_URI} [QSA,L]

Option 2 (!)

RewriteCond %{ SERVER_PORT} !^443$
RewriteRule .* https://%{ SERVER_NAME}%{ REQUEST_URI} [R=301,L]

Option 3

RewriteCond %{ ENV:HTTPS} !on
RewriteRule ^(.*)$ https://%{ HTTP_HOST}%{ REQUEST_URI} [L,R=301]

Option 4 (!)

RewriteCond %{ HTTP:X-HTTPS} !1
RewriteRule ^(.*)$ https://%{ HTTP_HOST}/$1 [R=301,L]

Option 5

RewriteCond %{ HTTP:CF-Visitor} '"scheme":"http"'
RewriteRule ^(.*)$$1 [L]

#remember to replace with your actual domain

Option 6

RewriteCond %{ HTTP:X-Forwarded-Protocol} !=https
RewriteRule .* https://%{ SERVER_NAME}%{ REQUEST_URI} [R=301,L]

Option 7.

RewriteCond %{ HTTP:X-Forwarded-Proto} !https
RewriteCond %{ HTTPS} off
RewriteRule ^ https://%{ HTTP_HOST}%{ REQUEST_URI} [L,R=301,NE]

Как делать не надо в htaccess

Further, all the styles, scripts, fonts must be loaded via https. You need to check and fix as download on the website and ship them locally.

If there is an absolute internal links to replace them with a relative (without specifying the Protocol and domain).

All external links to replace busprotocol option (to start with //, for example href=”//”). Unfortunately, at the same time (seen on modx) links are opened via https and if it is not on an external site, then get to the error. - If anyone knows how to deal with this without hurting the Protocol, share it with us :) !!!!!!

Check files robots.txt and sitemap.xml (everywhere should be https Protocol).

Fold the cache site.

To fully test the functionality of the website (all pages open correctly, whether the form, do the scripts, calculators, etc., personal account, online shop, online payment, etc.)

Aaaaaaa.... my position in the Top? - Peace of mind! All right

Fourthly, do not forget about search engine optimization and to smooth this transition. Temporary fall positions, attendance, and other indicators is inevitable, but it can be minimized.

    i>will check again the files robots.txt (Directive host) and sitemap.xml
  • Add https site to Yandex.Webmaster
  • To enable the move to https in the panel Yandex.Webmaster for site with http
  • To add a site with https in Google Console
  • In the settings of Google Analytics to change the site address to https
  • After adding in Yandex.The Google webmaster Console site with https to verify the availability and correctness sitemap.xml
  • To replace the external links (from social networks, directories, Yandex.Reference, etc.) on links with https in the future to take this into account when placing new links.

What to do in the case of "I failed" or "you drive"?

Write on mail, Vkontakte, call me :)

We will investigate and solve problems together!

Share this post

Comment (0)

Comments are missing

Leave your comment

Want to get new knowledge and knowledge?Sign up for a useful newsletter!