Google has stated that websites with an improper HTTPS setup will be given minor ranking boosts.

Do you want to know those HTTPS issues?

Here it goes…

According to the research, 34% of the Google search results are HTTPS. Gary Illyes from Google said at SMX advanced that more and more sites are getting secured but they haven’t done HTTPS implementation in a well-manner.

As a result, they are losing out valuable HTTPS ranking boost. By not migrating properly, their sites are suffering.

The most common issues with the migrated site is that it has not set HTTPS version as the preferred one and having the HTTP version floating. Google has also announced that they would index the HTTPS in default.

Here are the following issues that they face by having two live version site:

  1. Link dilution
  2. Duplicate content
  3. Wastage of search engine crawl budget.

Link Dilution

If a site has both HTTPS and HTTP version along with canonical tags can results in link dilution. Additionally, users come in contact with both the site version by sharing and linking. Here, external link equity and social signals will be divided into two URLs.

http issues

Duplicate Content

Google treats the content as duplicate if any website/blog have no canonical. For instance site with both HTTP and HTTPS setup version is not making use of canonical tags.

Unnecessary search engine crawls budget

Larger sites having both HTTP and HTTPS setup version live but not leveraging the canonical tags will be crawled by search engine twice instead of one preferred version. The solution for this is to redirect HTTP to HTTPS version i. e 301 redirects. This will successfully remove duplicate link dilution and avoid unnecessary crawl budget.

Follow the below mentioned best practices to overcome the SEO issues:

  1. Add HTTPS version to Google search console and Bing webmaster tools. Ensure you add both www and non-www versions.
  2. Make sure you point all internal and external links to the HTTPS version
  3. Make canonical tags points to HTTPS versions
  4. Make sure XML sitemap has HTTPS URL versions