How long can your website be down before it starts to cost you money? That question, not the feature list and not the price, is how to shop for hosting. Its twin is harder: if the site vanished this afternoon, how much recent work could you afford to lose forever? Nobody asks either question in the sales process, which is why so many organizations discover the answers during an outage instead of before one.
Episode 5 of The Web Managers Podcast is built on both questions. It translates the four kinds of hosting into situations a non-technical person can picture, explains what the advertised price hides, and spends its longest stretch on the one habit that turns a backup into a plan. This post is the companion: the takeaways, the myth the episode retires, the two standing segments, and the twenty-minute task to finish this week. If you have time for one thing, set up the monitor.
The building your site lives in
A web host is the company whose computers store your website and deliver it to anyone who asks. In the property language this season uses, the registrar runs the leasing office and the host owns the building. The industry sells four kinds of tenancy, and the episode translates each into a situation rather than a specification.
Shared hosting is an apartment building: many sites on one server, splitting the rent at roughly three to fifteen dollars a month. It is the honest default for brochure sites and small nonprofits, and its weakness is the neighbors. A virtual private server (VPS) is a townhouse: your own walls at ten to fifty dollars a month, assuming somebody will manage what is inside them. Managed hosting is the full-service building, where the host handles updates, security, backups, and speed tuning, most often for WordPress, at fifteen to forty dollars a month. Cloud hosting rents flexible space that scales with demand, and in raw form it is built for engineers.
For an accidental web manager whose hours are scheduled around another job, managed hosting is often the best money in the budget. Doubling the rent to make an entire category of maintenance somebody else's job is usually a bargain.
Two honest notes on price
The advertised rate is almost always an introductory rate. Renewal commonly runs two to three times higher, and the advertised monthly number usually assumes you prepaid several years. Record the renewal price in your inventory; it is the real one.
The second note is that more expensive is not more reliable. A well-configured ten-dollar plan with responsive support outperforms a neglected fifty-dollar one. That is why the episode's scorecard weighs support above every specification: on the day something breaks, the specification will not answer the phone.
The padlock you verify instead of buy
The padlock in the address bar comes from an SSL/TLS certificate, the credential that lets your site encrypt each visitor's connection. Browsers now label any page without one "Not Secure," right next to your organization's name. Certificates are free through Let's Encrypt, and reputable hosts install and renew them automatically, so your job is verification, not purchase. Confirm the padlock appears, confirm the certificate renews automatically, and confirm that typing the plain http version of your address forwards to https.
The hill
The episode's longest stretch is backups, and it lands on the same sentence Monday's post did: an untested backup is a hope, not a plan. Keep three copies on two kinds of storage with one off-site, and make sure one copy lives somewhere your host does not control, because the host's backups live inside the same account as your site. Then test a restore every quarter and log it with a date and a signature.
Myth busted: "My host does backups, so I'm covered"
It is half true, and the true half does a lot of comforting. Most reputable hosts do back up your site. What the myth skips is custody and verification. Anything that takes your site down at the host, a compromise, a billing dispute, the host's own failure, can take the backups down in the same stroke. And a backup nobody has restored is unverified; organizations regularly discover mid-crisis that months of "successful" backups captured half a site. Covered is not a feature you buy. Covered is a log with dates in it.
Also in this episode
Two new standing segments debut. The Question Line takes a classic: a board member offers to save $180 a year by moving the site to his nephew's server, and the episode scripts a decline that does not insult anyone's nephew. The Tool Minute covers Cloudflare's free tier, a content delivery network (CDN) and DNS management in one account.
Quick win: set up an uptime monitor
Create a free UptimeRobot account.
Add your homepage as a monitor, checking every five minutes.
Point the alerts at the organization's role-based email address, not a personal one.
Send yourself a test alert and confirm it arrives.
Add a second monitor for any other domain the organization owns.
From today forward, you learn the site is down from a notification instead of a customer, and you begin building the outage log that turns "the site feels unreliable" into evidence a host has to answer.
Done looks like the monitor live, a test alert received, and a second monitor added for any other domain you own.
Get the worksheet. The M4.1 Hosting Evaluation Scorecard and Backup Verification Log scores your current host on support, uptime, backup policy, and how hard it would be to leave, and gives you a dated line for every restore test. Score your current host before any mood about switching forms. It's free with a Web Managers account at https://webmanagers.com/register, and it arrives with the weekly Web Managers letter.