Home/Notes/What a plumber needs to know about HTTP to HTTPS
What a plumber needs to know about HTTP to HTTPS
5 Jul 2026
How a plumber deals with HTTP to HTTPS — and what usually goes wrong.
The problem: a booking tool that demands an account. The certificate chain breaks for a plumber.
When a plumber asked for a quote on HTTP to HTTPS, we sent a one-paragraph email instead of a slide deck. They signed the same day.
Test HTTP to HTTPS from outside your network before you call it done. Your office Wi-Fi might cache the old answer for another six hours.
Two-factor on the registrar account is the single highest-value thing we do for a plumber when managing HTTP to HTTPS. Everything else can be rebuilt; a stolen domain cannot.
Automate HTTP to HTTPS if you can. If you cannot, write a quarterly reminder in a calendar that someone actually checks. a booking tool that demands an account is what happens when nobody does either.
The vendor promised a plumber that HTTP to HTTPS was handled. We verified: it was not. Trust but verify has saved more uptime than any product we have used.
After the move, a booking tool that demands an account broke search indexing for a plumber. Google kept serving the old pages for another nineteen days.
If the hours on Google disagree with the site, people trust Google and then arrive angry. HTTP to HTTPS will not fix that. The hours page will.
Related notes
Tell us what you need.
Write a few lines about your project. We reply within one working day, usually with questions and a rough estimate.
hello@digitalserved.com