As we saw on previous articles, Google is giving an increasing importance to HTTPS for ranking its famous algorithm. However, when migrating a web to HTTPS we have to take into account different considerations to prevent it from affecting SEO. First of all, we have to choose what type of certificate to use.
You guessed it: Google does not like any type of SSL certificate. It recommends using certificates that hold a key of at least 2048 bits. Moreover, it is very important that the security certificate belongs to a recognised certification authority so as to ensure maximum compatibility with every browser.
Therefore, prior to beginning the migration process to HTTPS, you have to have the adequate SSL certificate installed in the server to make sure that it can satisfy the domain’s encryption needs and possible variations. In this article we will show you the different types of SSL certificates with their degree of validation and their level of protection. This will help you choose the most suitable for your web.
Depending on the number of domains they can certify:
- Single domain certificates: to ensure communication for a single domain. For example: www.yourdomain.com.
- Multidomain certificates: you can certify several domains with a single certificate. For example, www.yourdomain.com, yourdomain.com, m.yourdomain.com, yourdomain.com.uk, etc. The problem with these certificates is that the number of domains is limited, and this depends on the emitter.
- Wildcard certificates: to ensure an unlimited number of subdomains on the same level and for the same domain. For example: www.yourdomain.com, yourdomain.com, cdn.yourdomain.com, promotion.yourdomain.com.
If you have a simple web project with just one domain and no subdomains, the first option is the best. However, if your webpage is available on different TLDs or uses dynamic subdomains, you will very probably be better off with any of the other two SSL certificates.
Depending of the level of security they offer:
- Certificates with domain validation: the certificate only checks if the request can use a specific domain. It does not check the company’s ID nor any other information. This is how you would see it:
- Certificates with validation from the organization or company: the certificate checks if the request can use the domain and also explores de organization. With this certificate, the user can obtain corporate organization when clicking on the icon of safe page. This increases the visibility of the company on the web and the confidence goes up. This is how you would see it:
- Certificates with extended validation: the certificate checks if the request can use the domain and also explores de organization more deeply, checking a set of requirements such as official registries or the physical existence of the organization. We can see this in banks and other financial institutions. This is how you would see it:
You can also combine the two modalities to adapt the certificate to suit your web. We could have a Wildcard certificate with domain validation or a single domain certificate with extended validation. No two web projects are alike, so you have to choose the certificate that fits you best.
Image: Fabio Lanari.
Latest posts by Internet República (see all)
- Why are your employees the best prescribers of your brand? - 15 December, 2016
- How much money does Facebook make from you? - 7 December, 2016
- Requirements to include contents on Google News - 5 December, 2016