Home/Notes/A practical look at HTTP to HTTPS for a language school
A practical look at HTTP to HTTPS for a language school
20 Jun 2026
How a language school deals with HTTP to HTTPS — and what usually goes wrong.
The problem: a lastmod stamp that never changes. The certificate chain breaks for a language school.
We have seen agencies charge a language school for a yearly HTTP to HTTPS audit that consists of a screenshot and a paragraph. Ours is a working config file they can apply themselves.
When a language school moved hosts, the outage was not the new box — it was a lastmod stamp that never changes. We keep TTL short the week of a move, then raise it once everything is stable.
We underestimated how long HTTP to HTTPS migration would take for a language school. The estimate was two hours; the reality was a full day because a lastmod stamp that never changes had never been documented.
The job started when a language school realised their HTTP to HTTPS had been wrong for months. Nobody noticed because the site still loaded.
Related work on this site follows the same principle: one job, a real inbox, no theatre. a language school did not need four analytics dashboards to know that Tuesdays are slow.
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