Websites do not fail loudly. They drift. A dependency goes unpatched, a form stops delivering to an address nobody checks any more, a certificate lapses on a Saturday, an image-heavy page gets slower every time somebody adds to it. None of it is urgent until all of it is.
The other half is smaller and more annoying: the price that is three months out of date, the staff member who left, the hours that changed at Christmas. Changes that take ten minutes and somehow wait three weeks because there is no obvious person to ask.
Care covers both — the things that break quietly and the things that are too small to be a project.
What is covered
- Hosting, domains and certificates, in accounts that stay in your name.
- Dependency and security updates, applied and verified rather than accumulated.
- Uptime and error monitoring, so a failure is something we tell you about rather than something a customer does.
- Backups, tested by actually restoring one — an untested backup is a belief, not a backup.
- Content and copy changes: prices, hours, staff, products, a new page when you need one.
- A quarterly read of the analytics and Search Console, written as a page you can act on rather than a dashboard link.
Search does not hold still either
Rankings decay without anyone doing anything wrong. Competitors publish, Google changes what it rewards, a page that answered a question two years ago now answers it worse than three newer ones.
So care includes the search work that only matters cumulatively: keeping the Business Profile accurate and posted to, watching which queries actually bring people in, fixing the pages that lost ground, and adding the ones the data says are missing. It is unglamorous and it compounds, which is exactly why it gets dropped.
For sites we did not build
Taking on someone else's site starts with an audit, because we will not agree to keep something running that we do not understand. Sometimes that audit finds a site in good shape and the answer is straightforward.
Sometimes it finds a stack held together by twenty plugins and one abandoned theme, and the honest answer is that maintaining it costs more over two years than replacing it. You get told which, with the numbers, before anyone signs anything.
Work that shows it
Common questions
Is care required after a build?
No, and it never will be. Every project hands over with the code and the hosting in your name specifically so that you can walk away. Care is for people who would rather not think about it, not a toll on work you already paid for.
What counts as a small change?
Prices, hours, text, images, a staff change, a new page using the components the site already has. What is not small is new functionality — that is a project, and it gets quoted as one so nobody is surprised.
How fast do you respond?
Something broken and public gets looked at the same business day. Routine changes go into the next weekly batch, which is honest about how the work actually happens rather than promising an hour and delivering a Thursday.
Can you host the site?
Yes, in an account that belongs to you. You keep the credentials and the ability to move at any time without asking us.
Do you maintain WordPress sites?
Case by case, after an audit. A well-kept WordPress site with a small plugin count is straightforward. A site running twenty-five plugins on an abandoned theme is a liability we would be pretending to control, and we would rather say so than take the retainer.