Home/Notes/static hosting: a field note from a language school
static hosting: a field note from a language school
7 Nov 2025
How a language school deals with static hosting — and what usually goes wrong.
The problem: an inbox shared between the office and the webmaster. This breaks static hosting for a language school.
Search consoles like honest sitemaps. Every loc should be a document. Reserving ten thousand empty shells and hoping Google does not notice is not a strategy for static hosting.
The owner at a language school asked why static hosting matters. We showed them the error page their customers see when it breaks. That ended the conversation.
We document static hosting in a shared spreadsheet. It is not glamorous, but a language school can open it on their phone at midnight if something breaks.
We deployed a fix for static hosting at 5 PM on a Friday. It worked, but if it had not, we would have had no one available. We no longer push to production after Thursday noon.
When we onboard a language school, the first thing we check is static hosting. It tells us more about the previous provider than any sales call.
Managed hosting handles static hosting automatically — until it does not. a language school learned this when their provider migrated servers and an inbox shared between the office and the webmaster disappeared silently.
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