Translation of a website to HTTPS — what are the pitfalls associated with SEO?

There is a "old" website (14.9 years) with these characteristics:
Indexation in Yandex (pages): 2397
TCI: 475
Trast xt = 6

Going to translate it to work with HTTPS.

  • What pitfalls can be in this regard on the part of SEO? The fall of performance? Indexing?
  • What we must not forget to provide? Something to worry about? Be sure to do?
July 8th 19 at 15:40
3 answers
July 8th 19 at 15:42
The biggest risk when translating from http to https -- this is a temporary loss of the site from the index (old has already fallen and new ones have not ranked as high), and, as a consequence, loss of traffic for this period.

First, if possible, for the old site better to either skip or minimize it: for example, translate to https only sensitive sections (e.g., sections of the basket and the payment for the online stores). At the moment, just the fact of working over https gives significant advantages in the search.

If the switch to https all the same it is necessary, here is the algorithm how to minimize losses in this move:
1. Raise the website to https. At this point, the website needs to function correctly both on http and https.
2. Add both sites (http and https) in "Yandex.Webmaster" beta.webmaster.yandex.ru.
3. In robots.txt both write Host: https://site.ru/ (substitute your domain, don't forget to consider looks as the primary mirror-with www or without).
4. For an http site at "Yandex.The webmaster is" check application to transfer the site to https.
5. Wait. When Yandex and Google completely thrown out of the index the https site, only the absolute then put a 301 redirect from http to https.
in paragraph No. 5, you have a typo: "Wait. When Yandex and Google completely thrown out of index https site" - they should throw the pages available through the http Protocol and leave all that over https - right? - murray.Okune commented on July 8th 19 at 15:45
: Yes, that's right, a typo. - Mohammad.Gottli commented on July 8th 19 at 15:48
By the way, below given the link to the user manual from Koksharova. It is outdated because it is suggested immediately put a redirect in the "Yandex", such bonding can take up to several months. Officially "Yandex" recommends gluing domains through Ya Webmaster, in practice, in this case, the bonding takes place over 1-3 update.

Basically, as soon as gluing in "Yandex", you can put a redirect: Google will eat it without any problems. - Mohammad.Gottli commented on July 8th 19 at 15:51
July 8th 19 at 15:44
a pitfall here would like 1... for search engines a website with http and https are two different website with all the consequences. But right-minded redirects will solve the problem
The right redirects is 301ый from all addresses of the form: site.ru/* on https://site.ru/* right? - murray.Okune commented on July 8th 19 at 15:47
Yes, as long as the "new" site is completely proindeksirujut. - Mohammad.Gottli commented on July 8th 19 at 15:50
Here's a very detailed manual to help https://devaka.ru/articles/moving-to-https - Mohammad.Gottli commented on July 8th 19 at 15:53
Thank you! - murray.Okune commented on July 8th 19 at 15:56
July 8th 19 at 15:46
No problem.
Well sign the certificate as it should be, if you want to absolutely gladney. Although it is not required.
What does it mean to sign the certificate as expected? As it should be? - murray.Okune commented on July 8th 19 at 15:49
: using trusted CA to get it. - Mohammad.Gottli commented on July 8th 19 at 15:52

Find more questions by tags GoogleSearch engine optimizationYandexHTTPS