What website maintenance includes and costs

Website maintenance is the ongoing work needed to keep a website functioning, recoverable and useful after launch. It can include software updates, backups, security checks, fault investigation and testing important customer journeys. Content changes and wider improvements may be included, but that depends on the agreement.

The cost to maintain a website depends on its complexity, the consequences of failure and the work your provider accepts responsibility for. Hosting alone is not the same service as maintaining the whole website.

This guide explains what ongoing website maintenance should cover, how to compare plans and which questions to ask before signing. Published prices are individual provider examples. Worked calculations are illustrative and do not describe Vimso’s rates or a UK market average.

A maintenance agreement should name the owner

Questions behind the feature list

Area	Ask the provider	Evidence to request
Updates	Who checks the site after changes?	A record of updates and functional checks
Backups	What can be restored and how?	Files, database, retention and a tested recovery method
Alerts	Who responds, and when?	Support hours and an escalation route
Content	Which edits are included?	A defined allowance and approval process

On a small screen, swipe across the table or focus it and use the arrow keys.

In this guide

1. Start with what your website does for the business
2. Software updates need a checking process
3. Backups should support an actual recovery
4. Distinguish monitoring from someone responding
5. Test the functions that bring in business
6. Agree what content support includes
7. Understand hosting, licences and domain renewals
8. What do published maintenance prices tell you?
9. Use a worked budget to uncover missing costs
10. Decide whether to maintain it yourself
11. What a useful maintenance report should show

Start with what your website does for the business

A simple information site and an online shop do not have the same maintenance needs. One might collect a handful of enquiries each week. The other may accept orders throughout the day and depend on stock, delivery and payment connections working together.

List the functions that would cause a business problem if they failed. Include contact forms, booking tools, checkout, downloads and customer access. Note which services sit outside the website, such as an email platform or payment provider.

Then consider the effect of downtime or lost data. Could your team manage enquiries by phone for a short period? Would losing the latest orders create a serious operational problem? The answer should influence support, monitoring and recovery arrangements.

This is a better starting point than buying the longest list of maintenance features. You need a service that addresses the failures that matter to your business and makes responsibility clear when several suppliers are involved.

Software updates need a checking process

For a WordPress website, maintenance can include the core software, theme and plugins. Updates may address security issues, compatibility or functionality. They should be considered as part of keeping the whole system supported rather than simply clearing notification badges.

Ask how updates are assessed and applied. Is a backup taken first? Are significant changes tested on a separate copy of the website? Which pages and customer journeys are checked afterwards? Automated updates can be useful, but they do not remove the need to detect failures.

The WordPress update guidance recommends preparing a backup before updating. Your provider should also explain what happens if an update creates a problem and whether investigation or restoration is included in the plan.

Avoid assuming that every plugin can remain unchanged indefinitely. Unsupported software or incompatible dependencies may need replacement work beyond routine updating. A good agreement explains how those issues are reported, estimated and approved before additional charges are incurred.

Backups should support an actual recovery

A backup is a saved copy of the information needed to restore the website. For WordPress, that normally involves files and a database. Saving only the visible pages or only the database may leave important parts missing.

Ask how often backups run, how long they are kept and where they are stored. A copy held only in the same account as the live site can be vulnerable to the same account failure. Discuss appropriate separation and access controls.

Backup frequency should reflect how much recent information you can afford to lose. A website receiving regular orders may need a different arrangement from a site whose content changes occasionally. A daily backup does not necessarily protect every transaction since the last copy.

Also ask whether restoration is tested. The WordPress backup documentation explains the importance of both files and database copies. A reassuring backup notification is less useful than evidence that the recovery process works and somebody knows how to carry it out.

Distinguish monitoring from someone responding

Uptime monitoring checks whether the website appears available. Security monitoring may look for suspicious activity or known problems. These checks can identify issues, but a detection service does not automatically include a person resolving them at any hour.

Ask who receives alerts and when somebody reviews them. Does the plan cover business hours only? What happens during weekends or holidays? Is there an emergency contact route and does it have separate charges?

Clarify the difference between a response target and a resolution target. A provider might acknowledge an issue quickly while needing more time to investigate. The agreement should explain priorities, communication and what depends on an external supplier.

No maintenance provider can honestly promise that a website will never be attacked or fail. Look for sensible access controls, supported software, clear incident handling and recoverability rather than absolute security claims that cannot be demonstrated.

Test the functions that bring in business

A page can load normally while its form sends nothing to your inbox. Maintenance should include agreed checks of the functions that matter, not just confirmation that the homepage responds. Identify those journeys when you set up the service.

For an enquiry form, check validation, submission, delivery and the visitor’s success message. For bookings, check the relevant availability and confirmation process. Payment testing needs a safe agreed method that does not create unintended customer transactions.

Keep the tests proportionate and authorised. Do not send real customer messages or create paid orders casually as a routine check. Use test modes where available and record which checks were performed and any limitations.

Include external connections in the conversation. If a form depends on a separate email service, decide who investigates delivery problems. A maintenance plan that stops at the website boundary may leave an important business journey only partly covered.

Agree what content support includes

Technical maintenance and content editing are different tasks. A plan might keep software updated but leave your team responsible for changing prices, staff details and opening hours. Another plan may include an allowance for small edits.

Ask how the allowance works. Is it measured in minutes, requests or a defined list of tasks? Does unused time carry forward? Can the provider create a new page, or only update text and images on existing ones?

Clarify what your team must supply. Publishing an approved paragraph is different from researching and writing a new service page. Image selection, accessibility descriptions, proofreading and formatting also need an owner rather than being assumed.

Record turnaround expectations and an approval method. Urgent corrections should have a route that fits the business, while larger changes may need a separate estimate. Maintenance should keep the website accurate without becoming an undefined promise of unlimited design and development.

Understand hosting, licences and domain renewals

Some maintenance plans include hosting. Others require a particular host or charge for hosting separately. Ask which environment the website will use, who controls the account and what happens if the maintenance agreement ends.

Software licences may also be included only while you remain a customer. Find out whether a booking plugin, page builder or other extension depends on the provider’s licence. Ask what renewals would cost if you needed your own account later.

Domain registration and business email are separate items to check. Make sure the domain remains under your business’s control and that renewal reminders reach a monitored address. A maintenance subscription does not necessarily mean those bills are covered.

Create a simple ownership list showing each service, renewal date, account owner and support contact. This reduces the chance of a website failing because everybody assumed another supplier was responsible for a small but essential renewal.

What do published maintenance prices tell you?

Published prices show the cost of a particular offer, not a standard market tariff. Scope, hosting conditions, response arrangements and included work differ. A lower price may be suitable for one website and inadequate for another.

As examples checked on 2 November 2026, Business Image advertises maintenance at £25 per month plus VAT for sites hosted with it. Designbox advertises plans starting at £99 per month plus VAT, with a broader combination of hosting, maintenance and support. Check current scope and tax treatment directly before comparing.

Those examples do not establish that either offer suits your website or that the more expensive one is automatically better. Ask each provider to respond to the same list of requirements, including the functions and recovery needs you have identified.

Compare the total annual commitment, not just the smallest monthly number. Include setup work, hosting, paid software, content support and potential emergency charges. A plan that appears inexpensive can become costly if the ordinary work you need is routinely excluded.

Compare a complete annual commitment

£80Illustrative monthly total

×

12Months

=

£960Before applicable VAT

Example inputs: £60 maintenance plus £20 hosting each month. A separate £120 annual licence would bring this example to £1,080 before applicable VAT. These are invented planning figures, not Vimso prices.

Use a worked budget to uncover missing costs

Consider an illustrative proposal containing £60 per month for maintenance and £20 per month for hosting. The combined recurring amount is £80 per month, or £960 over twelve months, before any applicable VAT and other charges.

If a separately purchased software licence costs £120 annually, the illustrative yearly total becomes £1,080 before any applicable VAT. This is a budgeting exercise using invented inputs, not a supplier quote or a suggested standard price.

Now ask what happens when the website needs a new page or a major repair. If those jobs are outside the agreement, allow for them separately. Do not assume a monthly payment covers every possible change just because it is called a care plan.

Use the same calculation for each proposal. Record what is included, what is optional and what cannot yet be priced. An honest unknown is easier to manage than a total that looks precise because several necessary costs have been left out.

Decide whether to maintain it yourself

You can manage some maintenance internally if somebody has the time, access and knowledge to do it properly. That includes checking backups, applying updates responsibly and recognising when specialist help is needed. It should be an assigned role rather than a task everybody expects somebody else to remember.

Consider the cost of interruptions as well as the subscription saved. If the website breaks, who can investigate it without abandoning essential work? Does that person have access to the host, domain and relevant external tools?

A mixed arrangement can work. Your team might maintain content while a specialist handles technical updates and recovery. The boundary should be explicit so a failed form or expired licence does not fall between the two responsibilities.

Before taking over an existing site, ask for an inventory and a current working backup. Review outstanding issues and unsupported software. A maintenance provider may reasonably need an initial assessment or repair project before accepting ongoing responsibility.

What a useful maintenance report should show

A concise report should explain what was checked, what changed and what needs a decision. Update lists can be useful, but they should not hide failed backups, unresolved faults or important actions waiting for business approval.

Ask for meaningful exceptions. If an extension cannot be updated safely, you need to know why and what the proposed solution costs. If a form test failed, you need the business impact and next step, not simply a reassuring green dashboard.

Review the service when the website changes significantly. Adding payments, memberships or regular bookings can change the consequences of failure and the required support. A suitable plan should evolve with the business rather than remaining unchanged by habit.

If you want to discuss your website with Vimso, send an enquiry describing the platform, important functions and any current problems. Ask what support is available for that particular setup. A useful conversation begins with a defined need, not an assumption about an unpublished maintenance package.