Forum Moderators: Robert Charlton & goodroi
Be HTTPs by October or Chrome will show "not secure" flag
Having an untrusted Cert is much worse than having no Cert
The old adsense ads that use javascript are not showing up with https.
- Generic Steps to Switch from HTTP to HTTPS -
• Read all info at your host concerning certificates & switching to HTTPS and when applicable, follow those instructions.
• Install security certificate.
• Have your host enable HTTPS (if needed.) This will enable access from both HTTP & HTTPS allowing normal access while you test.
• Go through site, page by page & make sure all file paths are relative (no protocol.) Test by accessing site using HTTPS and look for any browser alerts.
• Install 301 code in .htaccess fileNote: your server may require a different codeRewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
• Go through site again, page by page, and test. Any remote absolute links will need to be HTTPS including those found in scripts & pluggins. If you publish Adsence or other advertising, links in these scripts need to be HTTPS also (or just remove the protocol altogether.)
• Update sitemap.xml (if applicable) and submit to appropriate agencies (Google, Bing, Yandex, etc)
• In Google Search Council create a new site using HTTPS (do not use the Change of Address form.) It will take a few days to start populating information. This is normal & traffic to old site (HTTP) will drop off accordingly.
• Bing Webmaster Tools, Yandex & others should update automatically once they crawl your new pages. Updating/re-submitting sitemap.xml should speed up this process.
Also if it is possible for anyone, please open my (URL in profile) and check if it is working fine, I will appreciate it. Thanks
now the response time of SSL is 558ms
[edited by: MayankParmar at 5:08 pm (utc) on Oct 1, 2017]
There is a problem! I have the COMODO SSL installed. On Internet Explorer and Microsoft Edge in Windows Phone 8 and Windows 10 Mobile respectively is showing an certificate error to old users (who haven’t cleared the cache). It works after clearing the browser history, I have tested it on 5 devices and that’s a solution. As a result, I’m seeing a big drop in direct traffic. I cannot ask viewers to clear the browser cache, I did clear WP Super cache but it is of no help!
This might be a dumb question, but I wonder if Google will look at shared certificates like Let's Encrypt or those provided by Cloudflare to free accounts as legitimate or as "sub standard" certificates.
Or may be the direct traffic data shifted to organic section after the HTTPS change, is that possible?