Website Hosting and Maintenance Services Explained
Website hosting is the server and connection that keep your site reachable. Maintenance is the ongoing work that keeps it updated, secure and working. You need both; buying one without the other is how small business sites go down, get hacked, or quietly stop sending enquiries.
Hosting: what you are actually paying for
A host rents you space on a computer that stays on, plus the connection that lets visitors load your pages. That machine runs a web server, usually PHP, and a database. SSL, the padlock in the browser, is free on most UK hosts. Business email is sometimes bundled and sometimes a paid extra, so check rather than assume.
Typical UK prices sit in fairly tight bands:
- Shared hosting: £3 to £12 a month on a first-year offer, then £8 to £18 when it ends
- Managed WordPress hosting: £10 to £40 a month
- A small VPS or cloud server: £20 to £80 a month
- Hosting inside a designer or agency monthly plan: rarely itemised, so compare the whole fee
Shared hosting is enough for a brochure site with modest traffic. It lets you down when PHP is years out of date, backups cost extra, or support is a two-day ticket queue. Unlimited storage and bandwidth on a budget plan means fair use. A spike in traffic, a large media library, or a hacked site sending spam will get you throttled or suspended.
Hosting does not update your CMS, plugins or apps, and it does not repair a contact form that stopped sending. Some hosts sell a managed extra. Read the inclusions. Many of those extras patch the server and restart services. They do not own the problem when a plugin update breaks your theme.
Maintenance: the work after launch
Maintenance is the list that stops a live site rotting. For a typical small business CMS site, a serious monthly service should cover:
- Core, theme and plugin updates, checked so the layout still holds
- Security patches and a malware scan
- Backups stored off the same server, with the occasional restore test
- Uptime monitoring
- PHP upgrades when the host retires an old version
- Fixes when a form, booking tool or payment plugin breaks after an update
- Removal of unused plugins and stale logins
That is not a redesign and it is not a pile of new pages. If a plan says unlimited changes, ask what a change means. In the UK it usually means a phone number or a paragraph, not a new service section.
Do it yourself and the cash cost is £0, plus your time and the risk of a missed patch. Freelancer care plans commonly sit at £25 to £75 a month. Small agencies often charge £50 to £150. Host site-care add-ons at £5 to £30 on top of hosting tend to run automatic updates and little else. When an update wrecks the header, you are back in the ticket queue.
A static HTML site needs less patching, but still needs SSL, backups and server security. An ecommerce site needs more: payment plugin updates, a faster restore if checkout dies, and hosting that does not buckle when a few customers pay at once.
Why hosting and maintenance should sit together
A plugin that needs a current PHP version cannot be updated if the host is on an old one and nobody has server access. When the site is down, the host calls it an application fault and the maintainer calls it a server fault. Two contracts, two invoices, no owner.
Backups are the usual weak point. A host snapshot can live on the same disk as the site. A usable backup is a copy elsewhere, plus someone who has restored it before the emergency. 99.9% uptime still allows about eight hours of downtime a year. 99% allows about three and a half days. Monitoring is what tells you the site is down at 7am.
What fully managed should mean on paper
Get this in writing before you pay:
- Who holds the hosting login and the CMS login
- How often updates run, and whether anyone looks at the site afterwards
- Where backups are stored, how many days they are kept, and when they were last restored for practice
- Who you contact if the site is down, and between which hours
- Whether copy tweaks are included, and the monthly limit
- Who owns the domain, the hosting account and the files if you walk away
A promise to handle everything, with no list, is a slogan.
Common UK setups compared
Typical UK market ranges, not a quote:
| Setup | Typical monthly cost | What you still do | Main risk |
|---|---|---|---|
| Shared host, you maintain it | £5 to £15 | Every update, backup check and outage | Missed patches, expired card, no restore |
| Host plus their care add-on | £15 to £40 | Chase tickets for anything beyond auto-updates | Slow help; updates that break the theme |
| One-off site, hosting in your name, separate maintainer | £30 to £100 after the build | Two invoices; coordinate when they disagree | Split responsibility |
| One pay-monthly plan covering host and management | Varies by provider | Little, if it is genuinely hands-off | Lock-in if you do not own domain and files |
How to choose without wasting the fee
- Write down what the site must not do: go offline on a Monday, lose the enquiry form, leak customer data.
- Check the CMS. WordPress and similar systems need monthly patching. A simple static site needs less.
- Put the domain in a registrar account you control. Hosts like to bundle the domain so leaving is painful.
- Pick hosting that matches traffic and PHP needs, not the cheapest first-year banner.
- Give one party enough access to the server and the CMS that they cannot shrug when something breaks.
- Confirm backups are off-server and that a restore has been practised.
- Get support hours in writing. Email-only, next working day, is not the same as someone reachable at 8am.
I build websites for small businesses two ways. A one-off build suits you if you can pay upfront and then arrange hosting and upkeep in your own name. A pay-monthly plan uses a setup fee and then a monthly price that includes hosting, updates and ongoing management, which suits you if there is no large upfront budget. Figures are on arlowebstudio.com. Either way, own the domain and make sure you can export the files.
If the site already exists, use the same split: one named owner for host and CMS, not three people and a shrug.
What usually goes wrong
The card on the hosting account expires and the site vanishes on a Sunday, while the login sits on a freelancer's personal email from three years ago. Twenty plugins, half idle, one abandoned, is how a lot of small WordPress sites get compromised. A shop on a £3 shared plan times out at checkout, then host and theme author blame each other.
None of that is fixed by a cheaper host. It is fixed by one person who can touch the server and the CMS, and by backups that actually restore.
Frequently asked questions
Do I need both hosting and maintenance?
Yes. Hosting keeps the site reachable. Maintenance keeps the software patched, backed up and working. Hosting alone leaves you one missed update away from a broken form or a compromised CMS.
Can I buy hosting myself and only pay for maintenance?
Yes, and it is a clean setup if the maintainer has enough server access to change PHP, restore backups and manage SSL. Without that access you are back to split responsibility when something breaks.
How much do website hosting and maintenance services cost in the UK?
Shared hosting is often £3 to £18 a month depending on intro rates. Maintenance on top is commonly £25 to £150 a month. Bundled pay-monthly website plans replace those two invoices with a setup fee plus one monthly amount. Compare the whole cost, not the cheapest host banner.
What happens if I only pay for hosting?
The server stays on until the card fails or the host suspends you. Plugins go stale, SSL can lapse if it is not auto-renewed, and nobody is watching uptime. It looks cheap until the week something breaks.
Who should own the domain and the hosting account?
You should. The designer or maintainer can have access. If their email is the only login, you will struggle to leave, to renew, or to restore after a dispute.
Does a website builder replace hosting and maintenance?
The builder includes hosting of a sort, and they patch their own platform. You still need accurate content, working add-ons, backups, and a plan for support hours. Check that you can export the site if you outgrow it.