Moving from HTTP to HTTPs in WordPress

When you move from HTTP to HTTPs there are several actions to take with Search Engines, WordPress, and Social Media Accounts.

As a best practice we do recommend creating a backup of your site before making changes. If you are not sure how to create a backup, please contact your host provider.

A. Things to Change With Search Engines

1. Claim and verify your HTTPs site with your search engines. You will need to add the site in the search engines and verify ownership. These guides explain how to do this with Bing, Google, and Yandex.
2. Submit your Yoast sitemap: sitemap_index.xml under the new HTTPs site. This guide explains how to submit the Yoast sitemap to Bing, Google, and Yandex: Submit Your Sitemap to Search Engines.
3. Delete any and all sitemaps you have under your old HTTP site.
4. NOTE: It is OK to keep your old HTTP site in your Search Console, just be sure to delete the sitemaps under it.

B. Things to Change in WordPress

Since the 5.7 release, WordPress automatically detects whether your WordPress website runs on a hosting package that supports HTTPS but is not yet set up to use HTTPS by default. If it is not, you will see a critical notification in the Site Health tool. You can find the Site Health tool on your WordPress Dashboard, or by going to Tools->Site health.

When you see the notification “Your website does not use HTTPS” all you need to do is expand the issue and click on the button to update your site to use HTTPS. Then, WordPress will automatically update the database URLs.

WordPress will also detect if your site does not support HTTPS. In that case, you will see a recommendation to contact your host and switch to HTTPS.

C. Things to Change with Social Media

When you change to HTTPs any social media shares you have will be lost. This is a result of how sharing works rather than a flaw or bug with Yoast. You can restore the shares on a site by using a filter outlined in this guide: Changing the OpenGraph (og) URL

D. Other Things to Consider

If you are going from the WWW to HTTPs this guide explains more about how to make the change: Redirecting Your Site to Non-WWW and HTTPs.