Enable HTTPS/SSL

Enable HTTPS/SSL in WordPress — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
The site needs to serve securely. Enable HTTPS for Sarah's blog, use the hosting control panel…
The site needs to serve securely. Enable HTTPS for Sarah's blog, use the hosting control panel certificate she already purchased, and verify the certificate is active. Update site URL to https://sarahwrites.com, force all traffic to HTTPS, and confirm mixed content is resolved site-wide by checking five recent posts and the homepage before I tell her it's done.

Improve — make it easier to accept

+
Before I flip the site to HTTPS for Sarah, make approval easy: surface whether the hosting…
Before I flip the site to HTTPS for Sarah, make approval easy: surface whether the hosting certificate is paid or free, show the expected downtime window, list any plugins that typically break on HTTPS (like legacy asset loaders), and flag pages likely to have mixed content so procurement can sign off quickly.

Decide — diagnose the stuck moment

+
I installed the hosting certificate and changed the site URL to https://sarahwrites.com, but the…

I just installed the certificate but the site still loads on http.

I installed the hosting certificate and changed the site URL to https://sarahwrites.com, but the homepage still loads on http and the browser shows a mixed content warning. I am worried I missed hard-coded http links in themes or a plugin rewrite. I cannot check the server rewrite rules easily. What is the likely cause and the fastest next step to make the site fully HTTPS without breaking Sarah's comments and plugins?

Become — change the pattern

+
Over the last five site migrations we stall at the same place: mixed content and redirect loops…

We keep losing time to mixed-content and HTTP redirects.

Over the last five site migrations we stall at the same place: mixed content and redirect loops after enabling HTTPS. I want a habit that prevents this and saves an hour per site. Which checks and small fixes should I run before changing URLs so the switch works first-time on all small-business blogs?

Next to this one

Other website builder work people do in WordPress.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.