SSL Resolve & SEO Help
New here? Learn about Bountify and follow @bountify to get notified of new bounties! x

We have a site, that I'm placing an SSL on. It looks like a previous firm set up a Flexible SSL from Cloudflare but never did anything to it. It's resolving to both the http version and the https version. Note that google prefers the http version but the https version has no robots or canonical tag yet its not being indexed. My concern is, if I redirect the http into the https (the https maybe has been sitting there for years out in the ether somewhere) will I see any consequences? Why would Google prefer the http version over the https (note we have not triggered any dup. content issues) what is going on in this situation? Would it be best practice to remove the Flexible SSL from Cloudflare and run with a Lets Encrypt SSL?

• They are hosted at A2 Hosting

• At A2 Hosting there is a default "Lets Encrypt" SSL on the server

• Pagelaw.com is ran through cloudflare which has a flexible SSL. This SSL is overiding the server's "Lets Encrypt"

• The previous firm either didn't set it up correctly or didn't realize that the SSL was in place as both the https:// and the http:// resolve independently. There is no robots or canonical tag on the https version but it's not indexing or triggering a dup content flag (to my knowledge).

• I can a.) run with the flexible SSL and rewrite the resolve in cloudflare or b.) turn cloudflare caching off and let the Lets Encrypt SSL kick in and then rewrite the redirect/resolve in the htaccess.

• I'm concerned that even if we do redirect to the https version that the SEO may take a hit as it's just kind of been sitting there in the ether.

http://www.pagelaw.com
https://www.pagelaw.com

awarded to Zhopon
Tags
seo
ssl

Crowdsource coding tasks.

1 Solution

Winning solution

Question 1: if I redirect the http into the https will I see any consequences?
I'm concerned that even if we do redirect to the https version that the SEO may take a hit as it's just kind of been sitting there in the ether.

Answer 1 :

1) If you migrate your site from HTTP to HTTPS, Google treats this as a site move with a URL change. This can temporarily affect some of your traffic numbers.

2) Use server-side 301 redirects
Redirect your users and search engines to the HTTPS page or resource with server-side 301 HTTP redirects.

Source: https://support.google.com/webmasters/answer/6073543?hl=en

Question 2: Why would Google prefer the http version over the https (note we have not triggered any dup. content issues) what is going on in this situation?

Answer 2 :

1) It can be Due to HTTP set as your preferred version in google Webmaster (See 'Extra' at the bottom of the page for migration)

2) Verify that your HTTPS pages can be crawled and indexed by Google

3) Do not block your HTTPS pages by robots.txt files.

4) Do not include meta noindex tags in your HTTPS pages.

Use Fetch as Google to test that Googlebot can access your pages.

Question 3: Would it be best practice to remove the Flexible SSL from Cloudflare and run with a Lets Encrypt SSL?

Answer 3:
LetsEncrypt is a real SSL that encrypts traffic between your site and your server, giving your visitors privacy.

Cloudflare SSL is a certificate that you share with lots of other websites, it will encrypt traffic between your site and cloudflare but it's then unencrypted when it hits the cloudflare network. If you also have an SSL certificate installed on your site it'll then be encrypted again and sent to the server, if not then the request is sent directly to the server.

I personally prefer LetsEncrpt but if you want to use Cloudflare Caching. You can run Cloudflare (Full strict) with LetsEncrypt, follow this tutorial https://www.itechlogix.com/servers/using-letsencrypt-with-cloudflare-for-a-free-full-strict-ssl/

Extra : Should help you in migration.

Google Webmaster Tools treats HTTP and HTTPS as separate sites.

When adding a site, simply type the URL including the https:// prefix. You will then have two sites in Google Webmaster Tools.

Screenshot of "add a site" dialogue
https://i.stack.imgur.com/BxYBB.png

This fits with the general principle that http://www.example.com is considered a different URL from https://www.example.com and may validly serve different content, Google is OK with that. In practice, most websites set up a redirect, but Google Webmaster Tools is designed to work in either case, just add both sites.

Credit : https://webmasters.stackexchange.com/a/79684

PS : The answers I provided are based on my finding.

Do Let me know if it helps you.