⚡ Summary
A website keeps living after launch and quietly decays on its own: certificates lapse, forms break without telling anyone, prices on the page go stale. Support is a monthly subscription for small fixes and for someone keeping an eye on things. Not everyone needs it: if you open your own site twice a year, one-off fixes will cost you less.
The site is live, the invoice is closed, everyone is happy. Eight months later a customer writes "your form isn't sending" — and for the first time in all those months you look at your own site the way a visitor does.
It's an ordinary story. Sites rarely break all at once. They crumble in small pieces, each of which looks harmless on its own.
How support differs from development
Development has a finish line: the design is approved, the pages are built, the site is handed over. Support has no finish line, because it isn't a project but a working routine. Every month somebody checks that things are where they should be and makes the changes you ask for.
The house comparison holds up here. Building it and signing it off is one job. Changing bulbs, clearing gutters and watching the roof is another, much cheaper one. Skip the second and the first loses its value over time.
What breaks when nobody is looking
The short answer to why website maintenance is important sits in this list. Here is what decays by itself, with nobody touching anything.
- The SSL certificate. On most hosting it renews automatically, but when the renewal fails, the browser greets your visitors with a red warning about an insecure connection. People close the tab and don't come back.
- The domain. Paid for a year and forgotten. The site disappears the day the payment lapses, and getting the domain back afterwards often costs more than renewing it on time.
- Forms. The mailbox that receives enquiries fills up or starts filing messages as spam. The form still submits and still shows a cheerful "thank you" — you simply stop receiving enquiries and have no idea it's happening.
- Dependencies. The libraries and scripts your site is built from keep moving. Older versions eventually clash with newer browsers: the menu stops opening, the layout shifts on newer iPhones, the gallery stops scrolling.
- Content. Prices from six months ago, people who left long ago, a "valid until 31 December" banner still hanging there in March. Technically the site works, but this costs you more trust than a broken button does.
Can my website be hacked while all of this sits unattended? On a small business site it rarely starts with a targeted attack. It starts with an outdated dependency nobody updated. None of this takes much work. All of it takes somebody noticing in time.
What website maintenance includes
The exact list varies from studio to studio, but the core is roughly the same:
- Content updates. New prices, copy, photos, products, without you having to work out the code.
- Small interface fixes. Move a block, change a button, fix the spacing on mobile.
- Website monitoring. A regular check that the site opens, enquiries arrive, the certificate is alive and the domain is paid for.
- Technical updates. Libraries, dependencies, compatibility with current browser versions.
- Backups. So there is something to roll back to when a change goes wrong. Backup best practices are dull but firm: several copies, kept off the same server, checked now and then to confirm they actually restore.
- A report. A short "here's what we did this month", so you know what you're paying for.
That last one gets skipped a lot, and it shouldn't. A subscription with no reporting turns into a payment with nothing defined behind it.
Need support for your site?
Tell us how actively you plan to change your site after launch — we'll tell you whether you need a subscription or one-off fixes are enough.
How often a site needs attention
There's no single answer, because the frequency depends on what the site does.
A brochure site where the phone number changes once a year lives comfortably on the technical minimum: a monthly check and fixes when something actually comes up.
A landing page with ad traffic behind it asks for more. A broken form here costs real money per click, so it gets checked more often. Once a year a broader review makes sense too, and it has its own article: website audit.
A store or a catalogue site is its own story. Products, stock, prices, seasonal promotions: there is work to be found every week. If you're planning website development with a catalogue, put ongoing support in the budget from the start rather than six months in.
What to keep yourself and what to hand over
Some of the work needs no contractor at all, and an honest studio will say so first.
If the site has an admin panel, you can update the copy, prices and photos yourself without any trouble. The same goes for blog posts and product cards: it's routine, and paying for it monthly makes little sense when the changes are rare.
What's better left alone without experience: dependency updates, DNS and mail records, edits inside the template code. A mistake here doesn't announce itself. The site looks fine while enquiries quietly stop arriving, or a page slips out of search. That kind of thing costs less to hand to someone who deals with it daily.
For a small business the split that usually works is simple: content stays with you, the technical side and the monitoring go to the contractor. The subscription comes out noticeably smaller, and you don't depend on someone else's schedule when a price needs changing today.
Agree separately on who handles changes during busy periods. Before the holidays or an ad launch the contractor's queue gets longer, and an edit that normally takes an hour can easily wait two days.
Who answers when the site goes down
Working out how to check if website is down takes two minutes with any free uptime service. Who fixes it afterwards is the part worth settling before you sign the contract, not in the middle of an outage.
The subscription should state how quickly you'll get a reply and who exactly will give it. "Write to us and we'll take a look" is not a response time. A workable version names a specific reaction window during business hours, with separate terms for the situations where the site isn't working at all.
The second question is access. The domain, hosting, mail records and admin panel should be registered in your name. This isn't about trusting your contractor: it's so you can walk to another studio without negotiations and without buying back your own site.
Who doesn't need a subscription
Honestly, most small brochure sites don't.
If the site is static, you change something on it once every few months and you're not afraid to message a contractor when you do, a subscription is overpayment. Paying for specific fixes as they come up works out cheaper.
It starts paying off in two cases: when the changes pile up, or when an hour of downtime is expensive. A store in the week before Christmas and a dentist's brochure site in February are different situations with different costs of failure.
Website maintenance checklist: what to ask before you sign
Five questions that clear up most of the misunderstandings:
- What exactly the monthly scope covers, and what counts as a "small fix" here.
- How many hours or changes are included, and what happens once you've used them up.
- How long you'll wait for a reply on a working day.
- Whether backups are included and where they're kept.
- Who owns access to the domain, the hosting and the mail.
If all five get a concrete answer, the studio is worth working with. If the answers already drift during negotiations, they won't get sharper later.
Our own terms, response times and prices are on the service page: website maintenance. Sites built by other teams are welcome too — before we take one on, we look at the state of the code and what needs sorting first.