It never becomes a project again.

What’s the difference between hosting and looking after a site?

Hosting is where the site lives: the server, the speed, the uptime. Care is someone looking after the site itself: testing updates, keeping backups, watching security, fixing small things before they become big ones. Most businesses buy the first and assume the second is included. It usually isn't.

“We’ve got hosting” is the sentence I hear just before someone’s site has been quietly broken for three weeks. Hosting and care get used as if they were the same thing. They’re not, and the gap between them is where websites decay.

Hosting

The building the site lives in. A server, a network, uptime. Good hosting is fast and doesn’t fall over. It has no opinion about whether your forms work, whether a plugin update broke the layout, or whether anyone has looked at the site since launch. That’s not its job.

Care

Someone whose job it is. Updates read, backed up, tested on a copy, applied, reviewed. Security watched. Small faults fixed early. The site kept fast and current over years. And a person to email when something’s wrong, rather than a host’s support desk that will tell you, correctly, that the server is fine.

Why the gap matters

Sites don’t usually fail dramatically. They degrade: an update breaks one form, a plugin gets abandoned, speed drifts, the hours on the contact page are two years old. Each one costs a few enquiries a month. By the time it’s noticed, the fix is a rebuild, and the visibility built over years resets with it.

What to ask whoever you pay now

“Who tests updates before they go live?” “When was the last backup, and have you restored one?” “Who looks at the site after an update?” If the answers are “the host does it automatically”, “we think there is one”, and “nobody”, you have hosting.

How I do it

Both, together, for a fixed monthly amount: managed hosting, and a person doing the care. Month to month.

Ask me about this, or anything else.

talk to the real Warren
Secret Link