Services · Chapter VIII
Website care and hosting
A website needs looking after. Our care plans keep the software up to date, the backups tested and the small jobs done promptly.

A website is not finished at launch. WordPress and its plugins release updates every few weeks, many of them security fixes. Hosting needs monitoring. Forms stop sending when an email setting changes. Someone needs to notice when the site goes down at 2am on a Sunday. For many small Oxford businesses, that someone has been nobody, until the day the site is hacked or simply disappears. A care plan prevents that.
Who this is for
- Owners who do not want to think about their website between busy periods.
- Businesses whose original developer has moved on, leaving nobody who knows how the site works.
- Seasonal trades such as guest houses, tour operators and cafés that need changes made quickly before busy weeks.
- Clinics and charities that need accessibility and privacy settings kept in order as content changes.
- Growing companies with a steady trickle of news, vacancies and page edits.
What a care plan covers
| Task | How often | Why it matters |
|---|---|---|
| Software updates, tested on staging first | Monthly, or sooner for urgent security fixes | Most WordPress compromises use known holes in outdated plugins |
| Off-site backups | Daily, kept for 30 days | A backup you cannot restore is not a backup |
| Restore test | Monthly | Proves the backups actually work |
| Uptime monitoring | Every few minutes | We often know before you do |
| Security scanning | Daily | Catches unexpected file changes early |
| Form test submissions | Monthly | Broken forms fail silently |
| Speed and Core Web Vitals check | Monthly | Sites slow down as content and plugins pile up |
| Accessibility spot checks | Monthly | New content can introduce new problems |
| Edits and small improvements | As requested, within the plan's time | Keeps the site current without a new project |
| Written report | Monthly | A short email saying what was done and anything we noticed |
Getting started, step by step
- Audit. For sites we did not build, we review the hosting, theme, plugins, backups and security before agreeing a plan.
- Fix the urgent things. Outdated software, missing backups or broken forms are dealt with first.
- Set up monitoring, staging and backups to our standard.
- Agree a calendar of known busy periods and planned changes.
- First monthly report, after which the routine takes over.
Oxford's calendar matters. Term dates, graduation ceremonies, open days and the summer visitor season shape when many local businesses need changes. We plan care time around that rhythm, so menus, availability and opening hours are right before the visitors arrive rather than after.
Small edits, done properly
Edit time covers the jobs that otherwise sit on a to-do list for months: new staff, revised prices, seasonal menus, a new service page, swapping tired photographs, fixing a broken link someone emailed about. Requests go to one address and are logged, so nothing gets lost.
Hosting
We host sites on managed platforms suited to their size: well-supported hosting for WordPress, and static hosting on a global network for lightweight sites. Either way, you own your domain and your content, and you can take them elsewhere at any time. We handle SSL certificates, DNS records and email deliverability settings so your contact forms reach your inbox.
How long it takes to start
Taking on a site we built is immediate. For a site we did not build, the audit takes about a week, and any urgent fixes follow straight away.
What drives the cost
- The platform. A static site needs much less care than a WordPress site with an online shop.
- Number of plugins and integrations, each of which needs updating and testing.
- Editing time included each month.
- Traffic and hosting needs, which matter mainly for shops and busy sites.
- Response times you need. A shop selling every day needs faster cover than a brochure site.
Common mistakes
- Auto-updating everything on the live site with no testing, then finding the layout broken on a Monday morning.
- Backups stored on the same server as the site, which disappear together.
- Hosting bundled with a developer's account, so the owner cannot get access when they part ways.
- Unused plugins left installed, each one a potential way in.
- Nobody receiving the form emails because the address belongs to someone who has left.
What a typical month looks like
In the first week we apply and test updates on staging, then push them live at a quiet time. Through the month, monitoring runs in the background and edit requests are handled as they arrive, usually within a couple of working days. Towards the end of the month we test every form, run a restore from backup, check speed and spot-check accessibility on recently changed pages. The report lands in your inbox with anything we think you should know, such as a plugin that is no longer maintained or a page that has become slow.
When something goes wrong
Even well-kept sites occasionally have problems: a hosting outage, a third-party service that changes without warning, an update that clashes with a plugin. Because updates are tested on staging and backups are checked monthly, recovery is usually a matter of rolling back rather than rebuilding. We tell you what happened, what we did and whether anything needs to change to stop it happening again.
Leaving is easy
Plans run month to month. If you move to another provider or bring the work in house, we hand over every login, the full set of files and a fresh backup, and explain anything unusual about how the site is set up. We would rather keep clients because the service is useful than because leaving is awkward.
How we measure it
The monthly report records uptime, updates applied, backup and restore results, form tests, speed figures and edits made. Over a year, the measure that matters most is simple: the site stayed up, stayed secure and stayed accurate, and you did not have to think about it. If you are considering a larger change, our website redesign page explains how we approach that without losing what already works.
Every month
Core, theme and plugin updates tested on staging, uptime and security monitoring, a backup restore check and a short written report.
Small edits
Each plan includes time for content changes, new pages and minor fixes. Larger work is quoted separately.
Questions people ask
Do you look after sites you did not build?
Yes, after a short audit. If the site has serious problems we will tell you before taking it on, so there are no surprises.
Where is the hosting?
We use managed hosting with UK or European data centres, daily off-site backups and free SSL certificates.
Can we leave the plan?
Yes. Plans run monthly. If you leave, we hand over all logins, files and a full backup.
What happens if the site is hacked?
We restore from a clean backup, find and close the way in, and tell you plainly what happened. On a care plan this is part of the service rather than an emergency bill.
Do we need a care plan for a static site?
Static sites need far less maintenance, so a lighter plan, or simply an hourly arrangement for edits, is often enough. We will say which suits you.