Website Maintenance Cost UK: What You Pay For

Website maintenance is one of the murkiest line items in our industry. Some studios charge a flat monthly fee and never tell you what it buys. Others bundle it with hosting, SEO, and "support" into a number that is impossible to interrogate.

So let us be direct about what maintenance actually is, what it should cost in the UK, and where the padding usually hides.

What maintenance actually means

A website is software running on the public internet. That means it needs the same care as any other software: security patches, dependency updates, backups, and monitoring. Left alone, a site does not stay still. The platform ages, plugins go stale, and the gap between your live code and the current secure version widens every month.

Maintenance is the work that keeps that gap small. It is not redesign work, and it is not new features. Confusing those three things is where most billing arguments start.

Here is a simple way to split it:

  • Maintenance: keeping what exists secure, backed up, and working.
  • Support: fixing things when they break, and answering questions.
  • Development: building new pages, features, or changes you request.

A fair contract states which of these you are paying for and how the boundaries work.

The essentials you genuinely need to pay for

These are the things that protect your business, not just your website.

Security updates. WordPress core, plugins, and themes ship patches constantly, often for real vulnerabilities. On a custom build the same applies to the framework and libraries. Someone needs to apply these promptly and check nothing broke afterwards.

Backups you can actually restore. A backup that has never been tested is a guess. You want automated, off-site backups and a documented restore process. When a site goes down at 4pm on a Friday, this is the difference between ten minutes and a lost weekend.

Uptime and error monitoring. You should not learn your site is down from a customer. Monitoring flags outages, broken forms, and SSL certificate expiry before they cost you enquiries. This ties directly into why a site quietly stops generating leads: a contact form can fail silently for weeks.

SSL and domain renewals. Cheap to ignore, expensive to forget. A lapsed certificate throws a scary browser warning that scares off every visitor.

Software and dependency updates. Beyond security, versions reach end of life. Running an unsupported PHP version or an abandoned plugin is a slow-motion risk.

Essential maintenance is security patches, tested backups, monitoring, and dependency updates. Everything else is either support or new development, and it should be priced separately so you can see what you are paying for.

What a fair UK price looks like

We will not invent precise figures, because they vary with the platform and the stakes. But we can give you honest ranges based on the kind of work involved.

A simple brochure site on a well-maintained platform needs light-touch care: updates, backups, monitoring. In the UK this typically sits at the lower end, often somewhere between £30 and £100 per month.

A business-critical site, an e-commerce store, or a custom web application needs more: staging environments, tested deployments, faster response times, and someone who understands the codebase. That work reasonably runs from around £100 to several hundred pounds per month.

The number matters less than what sits behind it. A £150 plan with clear scope and a named response time is better value than a £40 plan that means "we might get to it".

Where the padding hides

Be alert to these patterns.

"Maintenance" that is really just hosting. Hosting is a cost, but paying a premium retainer for what is essentially a server rental is not maintenance. Ask what human work is included each month.

Vague "support hours" that never roll over. If you pay for two hours a month and use none, where do they go? A fair plan either banks unused time or is honest that you are paying for availability, not hours.

Bundling SEO into maintenance. These are different disciplines with different outcomes. When they are merged, it becomes impossible to judge whether either is working. If SEO matters to you, it deserves its own line and its own reporting. Our engineering work and our SEO work are always scoped separately for exactly this reason.

Content changes billed as emergencies. Updating an opening time or swapping a photo is routine. If every small edit triggers a call-out charge, the plan is designed to extract, not to serve.

The DIY question

Can you do maintenance yourself? Partly. If you are on a template builder like Squarespace or Wix, most of the platform maintenance is handled for you, which is one of the genuine advantages of that route.

On WordPress or a custom stack, the honest answer is that you can click "update", but you cannot easily tell whether an update broke a payment flow or a form until a customer does. That is the value of a maintainer: not the clicking, but the checking.

If you want to understand the trade-offs between platforms before you commit, our take on custom website versus WordPress versus template covers where maintenance responsibility actually sits on each.

Questions to ask before you sign

Before agreeing any maintenance plan, ask these plainly:

  • What specific tasks are performed each month, and how do I see they happened?
  • Are backups tested, and how quickly can you restore?
  • What is the response time when something breaks, and does it differ out of hours?
  • Are content edits included, and where is the line between an edit and development?
  • What happens if I leave: do I keep the code, the backups, and access?

That last one matters more than people expect. You should never be locked out of your own website because a relationship ended. A studio confident in its work hands over access without drama.

Our view

Maintenance is not glamorous and it is not optional. A site is a live thing, and neglecting it is how a fast, secure, lead-generating asset quietly becomes slow, vulnerable, and invisible.

Pay for the essentials without apology: security, backups, monitoring, updates. Push back on anything vague or bundled. And insist on transparency, because a maintenance plan you cannot inspect is not a plan, it is a subscription to hope.

If you want a straight answer on what your specific site needs, we are happy to look at it and tell you plainly, even if the honest answer is that you need less than you are currently paying for.

Related Insights

04 Start something

Let's build
what's next.