Cristian Worthington

Migrating a WordPress site from HTTP to HTTPS can be easily achieved with HTTPS Social Migration.This plugin checks to make sure your SSL Certificate is properly installed and makes the necessary changes to refer your incoming web traffic to HTTPS.
This plugin contains a link to a Premium version of the plugin (HTTPS Social Migration Pro), which addresses a range of other problems that can occur when you migrate your site to HTTPS, including, loss of social media counts, loss of social credibility, problems with other plugins on your site and the need to turn HTTPS off on certain pages.
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/YML8Lao4l5U?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
<blockquote>
Premium Support 
 MediaVidi provides support for HTTPS Social Migration Pro (our premium version), which you can access at https://MediaVidi.com/https
</blockquote>
<h4>Tags</h4>
seo, SEO, google, https, HTTPS, migrate https, social media, ssl, SSL, migrate ssl, migrate, counts, social media counts, social media shares, recover social media counts, social media counters

HTTPS Social Migration

Migrate your Wordpress site from HTTP to HTTPS with HTTPS Social Migration.

Simon Waters

TLS is growing in complexity. Server Name Indication (SNI) now means HTTPS sites may be on shared IP addresses, or otherwise restricted. For these servers it is handy to be able to set desired HTTP headers without access to the web servers configuration or using .htaccess file.
This plug-in exposes controls for:
<ul>
<li>HSTS (Strict-Transport-Security)</li>
<li>HPKP (Public-Key-Pins)</li>
<li>Disabling content sniffing (X-Content-Type-Options)</li>
<li>XSS protection (X-XSS-Protection)</li>
<li>Clickjacking mitigation (X-Frame-Options in main site)</li>
<li>Expect-CT</li>
</ul>
HSTS is used to ensure that future connections to a website always use TLS, and disallowing bypass of certificate warnings for the site.
HPKP is used if you don’t want to rely solely on the Certificate Authority trust model for certificate issuance.
Disabling content sniffing is mostly of interest for sites that allow users to upload files of specific types, but that browsers might be silly enough to interpret of some other type, thus allowing unexpected attacks.
XSS protection re-enables XSS protection for the site, if the user has disabled it previously, and sets the “block” option so that attacks are not silently ignored.
Clickjacking protection is usually only relevant when someone is logged in but users requested it, presumably they have rich content outside of WordPress authentication they wish to protect.
Expect-CT is used to ensure Certificate Transparency is configured correctly.

Security Headers

Plug-in to ease the setting of TLS headers for HSTS and similar

HTTPS Social Migration vs Security Headers