


We either save you money or make you money



We either save you money or make you money

A practical UK buyer's guide to website maintenance contracts, including updates, backups, security, response times, hosting and handover.
A business website needs ongoing ownership after launch. Software changes, content becomes out of date, forms need checking and security risks develop. A website maintenance contract should make those responsibilities clear so the business knows who checks the site, who responds when something fails and what happens before a problem affects customers.
Many businesses buy website maintenance services without a precise definition of the work included. One supplier may provide hosting and automated updates. Another may test important customer journeys, investigate failures and manage changes. Both may describe the service as website support. The contract should make the difference visible.
Before requesting support prices, record the website’s current setup. Identify its domain registrar, DNS provider, hosting account, content management system, theme, plugins, forms, analytics, external integrations and any separate booking or commerce systems. Record who holds administrative access and who is authorised to make decisions.
Include all business-critical journeys. A professional services website may rely on enquiry forms and calendar bookings. An ecommerce site also depends on products, checkout, payments and customer notifications. A member organisation may have logins and protected information. Maintenance priorities should reflect those real dependencies.
Without this inventory, two quotations are difficult to compare. A low monthly fee can look attractive while excluding the systems that cause the greatest commercial disruption when they fail.
Routine maintenance normally concerns the continued operation of the existing website. The contract may cover compatible software updates, backups, monitoring, basic fault investigation and support requests. Improvements might include new page templates, redesigned journeys, system integrations or substantial content production. Define which category each task belongs to before work starts.
Ask whether support includes third-party systems and licence renewals. Where they are excluded, somebody within the business must retain responsibility for them.
Websites built on WordPress depend on several moving parts. The core software, theme, plugins and hosting environment can change independently. A sound maintenance procedure considers compatibility, takes an appropriate backup and tests the important journeys after relevant changes.
The official WordPress upgrade guidance describes update processes and recommends backing up before major work. The WordPress backup guidance distinguishes website files from the database. A supplier should explain how both are protected where relevant to the site.
A backup schedule is only part of the answer. Ask when the last successful restore was tested and whether the business has an agreed recovery point and recovery time. A backup stored in the same failed environment may not give the protection expected. The appropriate arrangement depends on the site’s commercial importance and the hosting setup.
A simple uptime check can establish that a server returns a response. It cannot establish that a contact form sends an email, a product can be purchased or a booking reaches the calendar. Build a short list of critical journeys and agree which ones are tested after material changes or at a suitable interval.
Some tests can be automated. Others need a controlled human check using a test account or safe submission. Make sure testing does not create live customer orders, disclose personal information or trigger unnecessary messages. Record the results and assign responsibility for faults found.
Performance monitoring also needs context. A homepage may load quickly on an office connection while a slow mobile experience affects potential customers elsewhere. Google’s Core Web Vitals documentation explains measures of loading, responsiveness and visual stability. Choose checks suited to the site’s real audience and important pages.
Ask the supplier to define its support hours, incident categories and escalation route. A serious security incident or unavailable checkout needs a different response from a routine text amendment. A promise of rapid acknowledgement is distinct from an agreement to restore service within a set period.
Specify who can declare an urgent incident, who communicates with the business and who authorises potentially disruptive recovery actions. Where the site depends on a hosting provider or another software supplier, clarify who coordinates the investigation and what is outside the maintainer’s control.
A failed booking form on a healthcare services website can stop appropriate enquiries reaching the team even when the homepage is available. A routine broken link on a historic article may cause inconvenience but less immediate commercial risk. A useful contract would establish different response priorities and a tested route for both.
This is an illustrative operating scenario, not a claim about a WLW customer.
Website security involves hosting, accounts, software, backups and operational practice. The WordPress hardening handbook provides official guidance on reducing avoidable exposure. Maintenance work should identify who manages administrative accounts, multifactor authentication where supported, software vulnerabilities and changes to permissions.
The business should retain appropriate control over the domain, hosting and major service accounts. Contractors need only the access required for their work. Agree how credentials and access are reviewed when a supplier changes or a team member leaves. Keep confidential records out of public pages and routine marketing reports.
Ask how the supplier will report security findings and what evidence confirms an action was completed. Avoid treating a security plugin’s green status as a guarantee that the entire website is secure.
A useful monthly report identifies what was checked, what changed, incidents encountered, unresolved risks and work recommended next. An update count alone provides little commercial reassurance. Include successful backup status, significant test results and the exact responsibility for any outstanding action.
Check who owns the website code, designs, content, domain, analytics account and connected services. Confirm that the business can receive an administrator handover and a current system inventory if it chooses another supplier. Contract terms should explain notice periods, renewal, third-party costs, licence ownership and the process for transferring work safely.
Supply each bidder with the same inventory and the same list of expected checks. Request a written list of inclusions, exclusions, support hours, emergency response terms and typical charges for work outside the retainer. Ask what is required before the supplier can accept responsibility for a site it did not build.
Do not judge a support service solely by its monthly price. Review the consequences of an unanswered enquiry, a failed payment or extended downtime against the level of support being purchased. Some smaller sites need a modest, clearly scoped plan. Complex integrations and business-critical transactions may justify more substantial monitoring and incident arrangements.
Reliable maintenance protects the website’s current value. A separate improvement plan can address weak journeys, poor search visibility, confusing pages and missed opportunities. Keep the workstreams connected so an improvement does not break a working integration or remove content that already serves customers.
Start with a clear inventory, a responsibilities matrix and evidence of a working recovery process. Then agree how to report faults and prioritise changes. The result should be a website the business can operate with confidence and a contract it can manage.
WLW reviews website operation, design, customer journeys and the supporting systems as part of its wider consultancy work. Explore our online presence audit or discuss website support and development with us.
Phone:
Email:
Address: