Securing your website with HTTPS

Published March 15, 2017 | Updated September 2, 2025

HTTPS migration – you can do it and this is why

This is the subject of a talk I gave at the Boston WordPress Meetup. In a nutshell, HTTPS encrypts communications so attackers can’t steal data.

Video Transcript

My name is Amy Kvistad, and I’m going to talk about HTTP and HTTPS migration — why it matters, and how you can do it.

My website is amykvistad.com. You can follow me on Twitter at @amykvistad, and the slides are already posted there if you’d like to follow along.

I’ve been a member of the Boston WordPress meetup group since 2009 and attended the first Boston WordCamp that same year. I’m now a co-organizer. I’ve been doing WordPress design and development since 2009, and graphic design for 16 years. On a personal note, I’m co-parenting a new puppy, and when the weather is nice, I like to go sailing.

We’re going to cover what HTTPS is, why it’s important, common myths, and how to migrate your website.

HTTPS is a secure layer on top of regular HTTP. It adds encryption so communication between your website and the server is secure. It provides authentication — your SSL certificate proves you are the site owner. It prevents man-in-the-middle attacks, as well as cookie and password exposure. But vulnerabilities remain: your site can still be hacked, servers can be compromised, and software needs to be kept up to date. That’s why it’s critical to keep WordPress, plugins, and themes updated, and protect against brute-force attacks.

So why migrate? Because HTTPS is the new baseline for the web. Standards bodies, browsers, and tech companies all say HTTPS should be the default. In 2014, the Internet Engineering Task Force declared pervasive monitoring an “attack.” The White House issued an HTTPS-only standard for government sites. The W3C set three goals in 2015: prefer secure communication, remove barriers to adoption, and don’t compromise TLS. Mozilla announced they would phase out non-secure HTTP. Google said that as of January 2017, pages collecting passwords or credit cards over HTTP would be marked “Not Secure,” with stronger warnings to follow. WordPress also announced that new features would require HTTPS support. As Google Chrome’s Emily Schechter put it: “HTTPS is one of the most important topics for web developers today.”

There are a few myths worth clearing up. First, that HTTPS is expensive. Not anymore — services like Let’s Encrypt make it free. Second, that it’s hard to set up. Many hosts now automate the process. Third, that it makes sites slower. In fact, HTTPS enables HTTP/2, which can make sites 50–70% faster. And finally, that it hurts SEO. The opposite is true: HTTPS preserves referral data and gives a ranking boost on Google.

So how do you migrate? Start by getting an SSL certificate. Many hosts now offer Let’s Encrypt free. Traditional SSL certificates cost more and usually include a warranty, which may be needed for e-commerce or sensitive data. Next, update your WordPress settings: change the site and home URL under Settings → General to HTTPS, or update in phpMyAdmin. Force HTTPS throughout your site with a plugin such as Really Simple SSL, or add rules to your .htaccess file. Force HTTPS for admin and login pages via wp-config.php.

Fix mixed content by using the Better Search Replace plugin to update old HTTP URLs in your database. Use tools like Why No Padlock or Chrome Inspector to identify insecure elements. Be sure to secure assets like Google Fonts, logos, or plugin resources that may be hardcoded with HTTP. Update your supporting services: add your HTTPS property in Google Search Console, resubmit your sitemap, update Google Analytics, and make sure your CDN supports HTTPS and HTTP/2.

For example, I worked with a client who needed secure forms for parents to submit payments through Authorize.net. The site initially had issues: Google Fonts were being requested over HTTP by a plugin, and the logo was still pointing to the development server. Once those were fixed, the site showed the green lock — a secure connection.

There were also questions. Wildcard certificates? Let’s Encrypt doesn’t yet support them, so if you need subdomain coverage, use a traditional SSL certificate. SiteGround specifics? Renewal may differ by host, so check auto-renew is enabled. Expensive healthcare-level certificates? Higher-cost SSL certificates usually include a bigger warranty or Extended Validation, but for most sites, Let’s Encrypt or a standard certificate is enough.

To summarize: SSL certificates are now free and widely available. HTTPS is the new internet standard. It’s easy to set up. It makes your site faster. It helps SEO and preserves referral data. So, migrate to HTTPS now.

What is HTTPS

  • HTTPS is HTTP over a secure connection
  • The added layer of security is called SSL (secure socket layer)
  • SSL encrypts communication between your browser and a website
  • SSL also provides authentication. It proves your identity
  • Prevents man-in-the-middle attacks
  • Prevents cookie and password exposure

There are remaining vulnerabilities

  • Doesn’t stop attackers from hacking your website, server, or network
  • Software vulnerabilities
  • Brute force attacks

Why migrate to HTTPS?

The internet’s standards bodies, web browsers, and major tech companies have come to understand that HTTPS should be the baseline for all web traffic.

Pervasive Monitoring is an Attack – The Internet Engineering Task Force (IETF)

HTTPS for Everything – White House Office of Management and Budget memorandum

The web should actively prefer secure communication.
Barriers to adoption should be removed.
TLS encryption must not be compromised.
W3C’s Technical Architecture Group, “Securing the Web”

Today we are announcing our intent to phase out non-secure HTTP. There’s pretty broad agreement that HTTPS is the way forward for the web.
Depreciating Non-Secure HTTP, Mozilla Security Blog, April 30, 2015

HTTP not secure warning

Beginning in January 2017 (Chrome 56) will mark HTTP pages that collect passwords or credit cards as non-secure, as part of a long-term plan to mark all HTTP sites as non-secure.
“Moving towards a more secure web” September 8, 2016

“HTTPS is now necessary for achieving the best the web can offer and HTTP is underperforming.” – Mythbusting HTTPS, Emily Schechter, product manager on Chrome security team, Progressive Web App Summit 2016

Dispelling myths about HTTPS

  • HTTPS is expensive – Free SSL is now available from Let’s Encrypt
  • HTTPS is difficult to set up – Many hosts will install Let’s Encrypt for you and if you buy an SSL certificate from them will install it instantly
  • HTTPS will be slower – The opposite is true. HTTPS is required for HTTP/2. Websites optimized for and delivered over HTTP/2 will perform 50-70% better than sites over HTTP/1.1.
  • HTTPS and SEO – Referral data passes through from HTTP to HTTPS whereas, HTTPS to HTTP referral data is stripped. Google will rank HTTPS websites higher!

Facts about HTTPS

  • Free
  • Internet standard
  • Easy to set up
  • Faster
  • Retains referral data for higher SEO ranking

Now lets walk through how to migrate your website from HTTP to HTTPS

  • Obtain an SSL certificate from your website host – either a free Let’s Encrypt or traditional SSL certificate. The biggest difference between the two is that Let’s Encrypt doesn’t offer a warranty.
  • Install the SSL certificate – your website host will often install the SSL certificate for you
  • Do I need a dedicated IP address? Not always, multiple SSL certificates can operate from a single IP address for most modern browsers

Implementing HTTPS

  • Update your site URL to HTTPS – You can do this in the Settings > General section of the WordPress dashboard
  • Force HTTPS – you can use the WordPress Force HTTPS plugin or add the following code to the .htaccess file

RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://yourdomain.com/$1 [R=301,L]

Fixing mixed or insecure content

Fixing mixed content HTTPS
  • Resolve insecure elements with the Better Search Replace plugin – you can search and replace “HTTP” with “HTTPS”
  • Identify insecure assets causing warnings – visit WhyNoPadlock and run a scan of your website to find the insecure items
  • Identifying Insecure Assets with Google Chrome Inspector Console – see even more information on passive mixed content through the inspector

Don’t forget to install SSL on your CDN

  • Many CDNs have Let’s Encrypt integration or a shared SSL option
  • Updated the URL from HTTP to HTTPS
  • Enable HTTP/2 support on your CDN

Update Google Search Console

  • Let Google know that your pages should be indexed using HTTPS
  • Add the property https://yoursite.com
  • Re-submit your sitemap in Google Search Console
  • Fetch and crawl your new HTTPS site

Update Google Analytics

  • Go to Admin – Property Settings and switch from HTTP to HTTPS

View the slides to my talk on Speaker Deck.

Amy Kvistad author headshot

About Amy Kvistad

Amy is a web designer and developer, building WordPress websites since 2009. She specializes in creating websites that are clear, functional, and easy for clients to manage. With a strong background in graphic design, Amy brings expertise in branding and digital campaigns, helping organizations strengthen their online presence.