Hello friends, I couldn’t get any sleep last night, I don’t know why, I guess I just had to get myself into trouble or I wouldn’t be at peace
At 2 AM I bought an SSL certificate, I really wondered if it would have an effect on SEO. Under this title, I will share the problems I experienced day by day and whether it really had an effect on SEO; I sort of made myself a guinea pig ![]()
Day 1
After getting the SSL certificate, I installed it on the server. I struggled for exactly 2 hours; I had never installed one before, by the way. Since it’s a DigitalOcean VPS, I have a single IP address and it appears shared. I wondered if it would work. As a result of my research, I realized the IP address actually doesn’t matter; you can apparently get SSL for multiple sites with a single IP. Once the server-side adjustments were finished, I entered WordPress, installed WordPress HTTPS as a plugin, and configured it as shown in the image below.
http://i.hizliresim.com/7VN23Y.jpg
In the image below, there is the most important setting of the plugin; you just need to add “/” there. When entered with http on Google, it automatically performs a 301 redirect to https.
http://i.hizliresim.com/z2BQ77.jpg
After these settings, the site has now completely switched to SSL and it turned out quite nice. It suddenly occurred to me that some people say sites open slowly because of SSL; to be honest, there was no change in speed, but I decided to test it via Google Page Speed anyway. The test result was terrible; I had a score of 48. When I looked at the details, it said I needed to minify CSS, images, etc., but the server I use had Google’s mod_pagespeed plugin. When I looked at the page source, I saw the plugin wasn’t working, of course because of SSL. As a result of 3 hours of research, I added the following codes inside mod_pagespeed using the trial and error method, and when I tested again, I got a score of 90 ![]()
ModPagespeedFetchHttps enable,allow_self_signed
ModPagespeedMapOriginDomain "http://www.domainismi.com" "https://www.domainismi.com"
ModPagespeedLoadFromFile "https://www.domainismi.com" "/home/domaink/public_html/"
ModPagespeedEnableFilters trim_urls
ModPagespeedRespectXForwardedProto on
Next came the turn to inform Google about this situation. I did a bit more research; on the Google support page, it said if you switch from http to https, you need to add the site again in Web Tools with the https extension as if it were a new site. I did exactly that, but this part didn’t sit well with me. I saved my rankings for important keywords before installing SSL, and now I just have to wait and enter content. I will write about the harms and benefits to me in the coming days under this title; I hope it helps everyone.
23,01,2015 Update
It has been 16 days since I switched to SSL. There has been a 30% increase in impressions so far, and impressions and clicks are constantly progressing with an upward momentum. Previously, when I added a topic, it would get indexed 1 day later without using “Fetch as Google”, but now the topic I add gets indexed by itself within max 5 minutes. So far everything is on track, I hope it continues like this…