Buying guide

Website Maintenance Costs in the UK: What Should a Plan Include?

Website maintenance costs depend on what a plan covers, how complex your site is and the support it includes. Learn what to compare, what may cost extra and which questions to ask before committing.

By
DevAgency
Published
Reading time
11 min

Website maintenance cost depends on the work and responsibility included

A man reviews a document at a desk beside a laptop.

When assessing website maintenance, consider the site, the work included and how much responsibility and support you need. Check whether a proposal covers hosting, routine maintenance and support, and whether these are listed separately. To judge whether a proposal is suitable, compare what the provider will do, any limits on that work and how tasks outside the plan are handled.

Start with the role the website plays in your business. If it mainly provides information and receives occasional enquiries, the cover you need may differ from that for a site taking orders or handling bookings. Consider what would happen if a page stopped working, an enquiry form failed or the site became unavailable. This helps you decide which tasks need regular attention and what level of help you expect when something goes wrong.

Look beyond the name of the plan. Check whether the proposal includes hosting and routine updates, or lists these as separate services. Ask which requests are included and how additional work is handled. Ask for the scope and exclusions in writing before comparing fees; compare the recurring fee with the work you need and the cover described in the proposal.

Keep recurring care separate from building the website. Ask whether initial setup, taking over an existing site or handover work applies to your situation, and how each would be handled. This guide focuses on recurring care and on checking what the plan covers. If you need to understand the service categories, see website maintenance and hosting.

Separate hosting, maintenance and support before comparing fees

A woman sits at a desk with papers, folders and office supplies spread out in front of her.

Before comparing recurring fees, separate what keeps the website available from the work that keeps it maintained and the route you use when something needs attention. Check the proposal for what it includes under each heading and where the limits sit.

Hosting provides the environment and resources used to make the site available. Check whether hosting is part of the fee or billed separately, and what limits or exclusions apply. If a provider says hosting is included, ask what happens if the site’s needs change or an issue concerns the hosting environment rather than the website itself.

Maintenance is the recurring work carried out on the website and its underlying software. The exact scope depends on the proposal. Confirm which tasks the provider performs, rather than assuming that a hosting package includes them. Assess hosting and maintenance separately.

Support is how you raise a fault or request and what the provider commits to doing with it. Check the permitted contact route, how work is assessed, and what response or resolution commitments apply. Also establish whether investigating a problem is included if the cause turns out to be outside the provider’s responsibility.

For example, imagine a customer reports that an enquiry form is not working. Hosting cover may concern the environment serving the site; maintenance cover may include checking the site and its software; support cover should explain how you report the fault and how the provider handles it. The proposal needs to say where diagnosis ends and separately chargeable repair work begins.

Routine upkeep is not automatically the same as adding a new feature, redesigning a page, writing new content or carrying out substantial repairs. Ask how those requests are scoped and charged. A bundled plan can still be convenient, provided its component services and exclusions are visible enough for you to decide whether it matches your needs.

Check the plan's updates, backups, monitoring and support

A person writes on a clipboard document with a pen.

The NCSC says software updates fix bugs that criminals could use to hack devices. 1, 2 Ask whether updates include the website platform, themes, extensions and other dependencies, and how the provider checks compatibility and tests the site afterwards. Agree what happens if an update causes a fault, including who investigates and whether corrective work is included.

If the site uses WordPress, ask how the provider handles an older installation: WordPress.org says the last major release is the only currently officially supported version; previous major releases may or may not receive security updates. 3

For ongoing maintenance, focus on how backups are retained and restored, what monitoring detects and reports, and how support can be contacted and when it is available.

What makes a maintenance plan cost more or less

A person draws a flowchart in red marker on a whiteboard.

Assess a maintenance plan by its scope, not simply by the number of pages on the site. Compare proposals by asking what the supplier expects to maintain, what it will check, and what it will do when something goes wrong.

For sites connected to booking, payment, stock or customer-management systems, include those connections in the maintenance scope. With each connection, someone may need to identify whether a fault sits in the website, the integration or the external service. If different suppliers own those parts, clarify who investigates and who keeps you informed; otherwise, troubleshooting can fall between them.

Hosting requirements also depend on the site's traffic, storage and other resource needs. Ask the provider to state the capacity assumptions behind its proposal and any limits that could lead to a different arrangement. Clarify whether the plan covers one live site or separate test and live environments, and how changes are checked before reaching visitors.

The site’s software affects the amount of care required. Updates may need more assessment or testing where the system is customised, has many dependencies, or is older and poorly documented. Ask which components the provider will update, how it checks for problems afterwards, and whether investigating or resolving issues caused by an update is included.

Support scope matters too. Support arrangements can differ in the kinds of requests accepted, the volume of work included, and the provider’s role in diagnosing a fault or coordinating with another supplier. A plan that only covers routine upkeep is not directly comparable with one that also handles troubleshooting and ongoing operational support.

One provider-authored price check updated in July 2026 reports UK website maintenance plan prices from £29 to £379 per month, based on 12 external provider prices plus the author's own. 4 Because those prices come from multiple providers, they should not be treated as a like-for-like benchmark or as a guide to what a suitable plan should cost.

For a useful comparison, ask each provider to describe the recurring work against your actual site: its integrations, environments, software and support needs. Keep one-off work and conditional expenses separate from that recurring scope, and compare what each proposal includes rather than treating unlike plans as equivalent.

Find out what the monthly fee leaves out

Two people point to a contract on a desk beside a pencil.

Read the exclusions as carefully as the included work. Check whether larger changes, investigations or costs from other suppliers are included or need to be agreed separately. Ask the provider to explain any vague wording and confirm the process before work begins.

  • Changes and content: Ask what counts as a minor change and where the boundary sits. Are new features, a redesign, substantial layout changes, copywriting, product uploads or other content work included, or separately scoped? If the plan has a limit, ask how it is measured and what happens when a request exceeds it.
  • Emergency and recovery work: Clarify whether urgent work, investigation of an incident and recovery after a failure are covered. Ask what the provider would do first, who authorises additional work and how any extra charge is calculated. Do not assume that routine maintenance includes every repair.
  • Third-party services: Check whether supplier fees, software licences, payment services, integrations and other external services are included in the recurring fee or billed separately. If another provider must act, ask who contacts them, who coordinates the work and whether their charges need separate approval.
  • Older or undocumented parts: If the site uses legacy software or has areas with limited documentation, ask whether they are covered, excluded pending assessment or require a separate scope. Establish what the provider needs to inspect before accepting responsibility for that work.
  • Hosting limits: Ask whether the proposal assumes particular levels of traffic, storage or hosting resources, and what would happen if the site outgrows those assumptions. Get clarity on whether the result could be a separate charge, a plan change or a request for approval.
  • Approval before extra work: Ask for the steps from request to completion: who provides the scope, how effort or charges are worked out, who in your business approves them and whether work waits for that approval. Agree how urgent exceptions are handled and how you will be told if the work changes.

Before signing, ask the provider to put unclear exclusions, limits and approval steps in writing. If the proposal still does not show what is recurring and what would be separately agreed, request a revised breakdown.

Compare proposals with a row-by-row checklist

Business reports and charts lie on a white table beside a notebook, pen and takeaway cups.

Use the same table for each proposal, copying the provider’s wording or recording its answer in each cell. Compare what the supplier will do, not just the fee: an empty or vague cell is something to clarify before you decide.

AreaWhat is coveredLimits or exclusionsHow to request itExtra charges
HostingRecord what hosting is included and which parts of the site it covers.Note capacity assumptions, exclusions and any conditions.Record who to contact about hosting issues and how.Ask what could be billed separately, including changes to hosting.
UpdatesList the systems or components the provider will update and what maintenance is included.Record any exclusions, change limits or work requiring approval.Note whether updates are scheduled or requested, and how you are told they are complete.Record how work outside the agreed scope is estimated and approved.
Backups and restoresNote what is backed up and what restore arrangements are described.Record any limits on backup coverage or restore requests.Write down who can request a restore and how.Clarify whether restores or recovery work can incur extra charges.
MonitoringList what the provider monitors and what action is included when an issue is found.Record what is not monitored and any stated limits.Note how issues are reported and who receives the updates.Ask whether investigation or remedial work is charged separately.
SupportRecord which types of fault or query are covered.Note exclusions and any written response or service commitments.Write down the contact route, information to supply and prioritisation process.Ask how work outside the support scope is charged and approved.
Minor changesDescribe the changes included, such as the kinds of content or adjustments covered.Record how the allowance is measured and what falls outside it.Note how to submit a change and who approves it.Ask what happens when the limit is exceeded and whether unused allowance carries over.
Third-party servicesList the external services the provider will manage or support.Note services or supplier work that are excluded.Record who contacts each supplier and how changes are handled.Separate the provider’s fees from third-party charges and clarify what happens if a service changes or stops.

Before comparing the completed tables, check any gaps in writing:

  • Who controls administrator, hosting and domain access? How is access managed if the supplier relationship ends?
  • What backup arrangements apply, who can request a restore, and what does the proposal say about restore testing and reporting?
  • How often will maintenance activity be reported, and what information will you receive?
  • What response or service commitments are actually written into the proposal? Do not treat general wording as a specific commitment.
  • How does cancellation work, what notice or charges apply under the proposal, and what does handover include? Confirm access, backups and relevant records.
  • If a cell is unclear, ask the provider to define the scope, limit and process for extra work in writing before comparing the fee.

Choose cover that matches the site's role in the business

A woman holding a clipboard stands among clothing rails and displays in a boutique.

Choose cover according to what the website does for the business and who can act when something goes wrong. A brochure site that rarely changes may need a different arrangement from a site that handles enquiries, bookings, sales or staff workflows. The decision is about who will do the work and carry the responsibility, not simply the size of the recurring fee.

  • Map the site’s role. Note which customer or staff tasks depend on it, what stops if a key page or function fails, and who needs to know. This helps you judge how much support and checking the business needs.
  • List the moving parts. Record the content system, important integrations and any processes that pass information between the site and other tools. Make sure the person responsible can recognise when a change has disrupted an enquiry, booking or data hand-off.
  • Be realistic about internal capacity. Self-management can suit a business with a named owner, suitable technical capability and time to carry out and check the work. Decide who will keep track of tasks, verify that the site still works and arrange help if an issue exceeds their skills.
  • Use a supplier where the defined work is useful. An external arrangement may suit a business that has identified specific work it wants a supplier to do. Check that the proposal names those tasks, explains how to raise a problem and makes limits and extra work clear.
  • Consider a mixed arrangement. Your staff might handle routine content changes while a supplier looks after technical tasks. Write down who owns each task and how a concern is passed between them, so work is not missed or duplicated.
  • Keep the agreement usable. Before committing, retain the agreed scope, exclusions, access arrangements, reporting expectations and handover terms. Confirm who controls the accounts and how access or responsibility will transfer if the arrangement ends.

Compare the proposed fee with the work, limits and responsibility it actually covers. If those details are unclear, ask for them in writing before deciding. If you are still defining the support you need, clarify the tasks and responsibilities before approaching a supplier.

Sources

  1. 1. Small organisations guide to cyber security: Protecting your devices, National Cyber Security Centre. Accessed 27 October 2026.
  2. 2. Small organisations guide to cyber security: Backing up your data, National Cyber Security Centre. Accessed 27 October 2026.
  3. 3. Supported Versions, WordPress.org. Accessed 27 October 2026.
  4. 4. Website Maintenance Cost UK: What You'll Really Pay (2026), Jamie Grand. Accessed 27 October 2026.

Photographs are illustrative stock images, not DevAgency staff, clients or products.

Next step

Answer a few questions about your maintenance & hosting project, your current systems and what should change. We reply with a written proposal.

Discuss website maintenance