{"id":108,"date":"2014-09-01T11:31:24","date_gmt":"2014-09-01T18:31:24","guid":{"rendered":"http:\/\/the-networks.com\/blog\/?p=108"},"modified":"2020-05-07T15:29:50","modified_gmt":"2020-05-07T22:29:50","slug":"help-google-ranking-ssl","status":"publish","type":"post","link":"https:\/\/the-networks.com\/blog\/help-google-ranking-ssl\/","title":{"rendered":"Help Your Google Ranking with SSL?"},"content":{"rendered":"<p>Really??\u00a0 So a secure Web site will rank better in Google than an unsecured site?\u00a0 But I thought we only needed to have a secure site if we were doing online transactions involving credit card info, or if we were requesting certain kinds of info from viewers.<\/p>\n<p>It&#8217;s true; Google announced recently that they will start considering whether or not a site is protected with SSL as a ranking signal.\u00a0 They are considering this a very lightweight ranking factor now.\u00a0 It will increase gradually over the coming months and years.\u00a0 They have explained their thinking <a href=\"http:\/\/googlewebmastercentral.blogspot.com\/2014\/08\/https-as-ranking-signal.html\" target=\"_blank\" rel=\"noopener noreferrer\">here<\/a> and <a href=\"https:\/\/www.youtube.com\/watch?v=cBhZ6S0PFCY\" target=\"_blank\" rel=\"noopener noreferrer\">here<\/a>, among other places.<\/p>\n<h2>Why is Google Doing This?<\/h2>\n<p>Google has indicated that security is a very big deal to them.\u00a0 They point to being concerned about the security of their own systems, and also to helping ensure the security of sites they return to searchers.\u00a0 That&#8217;s\u00a0 where your Web site comes in.\u00a0 It&#8217;s important to realize that in the future, not having an SSL secured Web site will adversely affect your search engine rankings within Google.\u00a0 It&#8217;s even more important to realize that not having an SSL secured Web site may cause your viewers to see warnings about their privacy possibly being compromised if they view your site.\u00a0 See the example below.\u00a0 Needless to say, this could have a devastating on your site traffic!<\/p>\n<p><a href=\"https:\/\/the-networks.com\/blog\/wp-content\/uploads\/2014\/10\/priv_warning.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-116 size-full\" src=\"https:\/\/the-networks.com\/blog\/wp-content\/uploads\/2014\/10\/priv_warning.jpg\" alt=\"priv_warning\" width=\"580\" height=\"284\" srcset=\"https:\/\/the-networks.com\/blog\/wp-content\/uploads\/2014\/10\/priv_warning.jpg 580w, https:\/\/the-networks.com\/blog\/wp-content\/uploads\/2014\/10\/priv_warning-300x146.jpg 300w\" sizes=\"auto, (max-width: 580px) 100vw, 580px\" \/><\/a><\/p>\n<h2>When Should You Implement SSL For Your Site?<\/h2>\n<p>Since this is a policy decision made by Google, there really is no way to know when it will become a &#8220;big&#8221; issue with site ranking.\u00a0 Many of the experts we follow feel that the right time frame for this to move from a very new factor that now carries little ranking weight to one that carries very important ranking weight is probably about two years.\u00a0 This does not mean that you should wait for two years or even one year to implement SSL on your site, however!\u00a0 Like other recommendations from Google, all of us that administrate Web sites should start planning for this right now, with the thought of implementing as soon as practicable.<\/p>\n<p>The best time to implement SSL for an entire Web site is when you are:<\/p>\n<ul>\n<li>Launching a brand new Web site at a brand new domain<\/li>\n<li>Making a major change to the URL structure on your existing Web site, like a site redesign<\/li>\n<li>Changing domain names<\/li>\n<\/ul>\n<p>If your Web site requires any of these actions then you absolutely should be including a change to an SSL secured site along with it.\u00a0 If your Web site does require these changes, then you should probably wait on making the change to SSL for now.\u00a0 However, in that case you should begin planning for making the change to SSL sometime in the next year or so.\u00a0 It should be combined with other large scale changes to your site if possible, because the kinds and scope work required.<\/p>\n<h2>So How Do We SSL Secure Our Web Site?<\/h2>\n<p>The process of converting your site to an SSL site involves several steps.\u00a0 We will give you the 30,000 foot view here.<\/p>\n<p>First, your Webmaster needs to purchase an SSL certificate for the exact domain that you want secured. He or the Web host then installs the certificate on the Web server, and the browser then is able to verify the identity of the certificate (and therefore the Web site) when connecting.\u00a0 The SSL certificate encrypts the connection between the Web server and a viewer&#8217;s Web browser.<\/p>\n<p>SSL certificates come in a variety of types, ranging in price from free to quite expensive.\u00a0 Free certs are issued by the server itself and are &#8220;self signed&#8221;, meaning there is no way for a viewer to verify the identity of the server, and therefore the Web site.\u00a0 SSL certs with even a very modest cost are issued by a certification authority; the entity from whom the cert is purchased.\u00a0 You are paying for that entity to verify that your domain name is real, that it is registered to you, and therefore can be trusted.\u00a0 Very inexpensive certs, however, are not fully compatible with all browsers.\u00a0 This means that even though you are real and your Web site is trustworthy, your viewers&#8217; browsers may still complain that your site <strong><em>may<\/em><\/strong> be untrustworthy.\u00a0 This is totally unsatisfactory in terms of creating trust between you and your viewer.<\/p>\n<p>More expensive &#8220;DV&#8221; (domain validated) SSL certs also verify your domain name and Web site are who you say they are, but they are also compatible with virtually all browsers, so the chances of your viewers getting trustworthiness warning messages while attempting to view your secure pages are very much reduced.<\/p>\n<p>Another class of SSL certificate is the &#8220;OV&#8221; (organization validated) cert.\u00a0 When purchasing this cert, the issuer will verify the identity and ownership of the organization owning the domain name, as well as the domain name itself.\u00a0 These certs are more expensive because of this additional validation.<\/p>\n<p>Our opinion, and the opinion of most other experts on this subject is that a DV (domain validated) SSL certificate is perfectly sufficient for the purposes of being seen to Google as a secure site.<\/p>\n<p>Secondly, if your Web site is being converted to a secure site (https:\/\/&#8230;) from an insecure site (http:\/\/&#8230;) then you will need to permanently redirect your insecure pages to their secure counterparts.\u00a0 This is normally done by specifying &#8220;301 redirects&#8221; for each of those pages.\u00a0 More complicated situations may require variations of this.\u00a0 This is something your Webmaster will do for you.\u00a0 It is a process that requires care in order that errors are avoided.\u00a0 There is potential for creating errors that will cause the search engines to stop crawling your site, or to create massive &#8220;duplicate content&#8221; issues.<\/p>\n<p>Thirdly,your Google &amp; Bing Webmaster Tools accounts, and your Google Analytics accounts need to be reconfigured to refect the changes to HTTPS of your Web pages.<\/p>\n<p>Fourthly, your Web developers will have to pay even closer attention to page download speeds.\u00a0 HTTPS (secure Web browsing) is inherently a bit slower than HTTP (unsecure).\u00a0 That makes download speeds another issue to pay very close attention to, because that also affects Google page ranking.<\/p>\n<p>And there is more, but these are the main points.<\/p>\n<p>We will have more detailed articles on secured Web sites in near future, so please stay tuned.<\/p>\n<p><a href=\"\/contact\" target=\"_blank\" rel=\"noopener noreferrer\">If you would like our assistance in navigating this new issue of concern for your Web site, please contact us<\/a>.\u00a0 We have been providing SSL certificates for many of our clients for many years.\u00a0 This is a subject to know <strong>very <\/strong>well.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Really??\u00a0 So a secure Web site will rank better in Google than an unsecured site?\u00a0 But I thought we only needed to have a secure site if we were doing online transactions involving credit card info, or if we were requesting certain kinds of info from viewers. It&#8217;s true; Google announced recently that they will [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7,3],"tags":[],"class_list":["post-108","post","type-post","status-publish","format-standard","hentry","category-seo","category-web-site-development"],"_links":{"self":[{"href":"https:\/\/the-networks.com\/blog\/wp-json\/wp\/v2\/posts\/108","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/the-networks.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/the-networks.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/the-networks.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/the-networks.com\/blog\/wp-json\/wp\/v2\/comments?post=108"}],"version-history":[{"count":19,"href":"https:\/\/the-networks.com\/blog\/wp-json\/wp\/v2\/posts\/108\/revisions"}],"predecessor-version":[{"id":190,"href":"https:\/\/the-networks.com\/blog\/wp-json\/wp\/v2\/posts\/108\/revisions\/190"}],"wp:attachment":[{"href":"https:\/\/the-networks.com\/blog\/wp-json\/wp\/v2\/media?parent=108"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/the-networks.com\/blog\/wp-json\/wp\/v2\/categories?post=108"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/the-networks.com\/blog\/wp-json\/wp\/v2\/tags?post=108"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}