How to determine "When to make a site into HTTPS"


Since Google's future HTTPS (SSL) site preferential policy has been reported, the interest of web managers seems to be increasing gradually.

Nonetheless, it is not easy for the site administrator to make the site HTTPS, but when it comes to handling the HTTPS implementation . In this article, consider the best timing.
20141117ssl_ key

Compare "labor" and "merit"
It is natural that HTTPS is useful for users, but for now the ranking is not different from the HTTP site, it seems that there is still a difference actually.
If you do, you will have to take the time and effort to "make HTTPS" your own site now running on HTTP and "the merit obtained by that" . First of all, I will think about "work".

"Time and effort" for HTTPS conversion

HTTPS of an existing HTTP site will be troublesome. That is,
· I need to set up a new site
Basically, Google recognizes HTTPS site and HTTP site as different sites. Therefore, it is necessary to perform forwarding setting (301) and normalization (canonical) processing on the original HTTP site.

· Search traffic may be temporarily dropped. <br /> Even if transfer settings are successful, Google indexes may take a while to update, so temporarily the search traffic to the site may drop There is.

"Merit" of HTTPS conversion

Let's consider the merit with HTTPS.
First of all, of course, it is quality improvement of security . For commercial sites in particular, HTTPSed sites give users great security and the site gains trust from users.
Next, although it is preferential treatment with the search result mentioned earlier, this is still a previous story, there is no information that the ranking of the HTTPS site is preferential treatment at this time.

Timing suitable for HTTPS, different for each site

In other words, it takes time and labor to finish the introduction effect like SEO yet . So far as I mentioned in past articles.
→ Google: percentage of HTTPS sites, "three times" in 2 years | SEO Pack blog
Why not aim for a high-ranking display with popular fixed-rate SEO measures? 
However, considering the future, it is necessary to make HTTPS someday. Since there was an interview that gathered well the idea around here, I will introduce.
→ "Does My Website Need an SSL Certificate?" On #SoundCloud * English, voice only
I am talking about John Henshoo of a US SEO company. We introduce SSL introduction as "In the long run", with a preface, we talk as follows.
1. For existing HTTP sites already converting <br /> You should not switch yet. Instead, it is better to create high-quality content.
The point is that it does not have to rush. However, if you are prepared ready to inject enough time and effort, I think that it is beneficial to do it quickly.
2. When creating a new site from now <br /> If you create a new site from now on, you should introduce SSL. There is no doubt that it will become important in the future.
In other words, "Since it is troublesome to start up the site, it is best to put it together."
In addition, another article is mentioned in the article of Search Engine Land mentioned in this interview.
3. If you already manage multiple sites <br /> On a site that is not doing so well, you should try HTTPS first. This has the advantage of accumulating test data.

Summary

In this way, based on the merits and demerits of HTTPS, when comparing it with the situation of its own site, I think that the timing of HTTPS conversion is roughly a guideline.
In particular, I think that there are many cases where technical personnel are located separately from the site manager, such as the commercial site of the company. In such cases, it may be handy to ask consultation with reference to the above criteria.

No comments:

Post a Comment

Powered by Blogger.