Website Maintenance.
Look after the foundations.
Check what the change affects.
Website maintenance handles the agreed technical upkeep of an existing site. We review its platform and dependencies, plan appropriate updates and checks, and document the recovery and provider responsibilities that support the work.
Maintenance should be specific to what the site actually runs. A static site, a CMS, and a custom application have different dependencies and ways to release changes. We identify important functions, assess available backups or source history, and use a suitable review process for the work. The aim is to reduce avoidable problems and make the system understandable, without promising that software can never fail.
Platform and dependency inventory
Document the agreed system, extensions, services, versions or support status, access, and responsible providers.
Maintenance priorities
Identify relevant updates, compatibility concerns, known issues, and tasks that should be handled separately.
Recovery requirements
Clarify the files, data, configuration, retention, restore access, and testing appropriate to the platform.
Clear responsibilities.
Useful ongoing work.
Your written scope confirms the depth and final format of the work. These are the components we can bring together for website maintenance.
- 01Platform and dependency inventory
Document the agreed system, extensions, services, versions or support status, access, and responsible providers.
- 02Maintenance priorities
Identify relevant updates, compatibility concerns, known issues, and tasks that should be handled separately.
- 03Recovery requirements
Clarify the files, data, configuration, retention, restore access, and testing appropriate to the platform.
- 04Scoped technical updates
Apply approved updates or changes through the agreed release approach and coordinate dependencies where needed.
- 05Post-change checks
Verify the agreed templates, forms, interactions, and other important functions affected by the work.
- 06Maintenance record
Explain completed changes, verification, remaining risks or provider dependencies, and recommended next actions.
Bring the right
specialist into the work.
This work connects to the related website, content, and operational support below. Explore the relevant service to see its distinct scope and deliverables.
Website Management
Website management gives the ongoing tasks on your site a clear owner and a practical plan. We coordinate the agreed updates, maintenance, checks, and improvements so you know what is being handled, what needs approval, and what comes next.
Explore website managementContent Updates
Website content updates turn approved business changes into accurate, well-presented pages. We manage the agreed text, images, links, documents, and selected metadata while checking the context in which the changes appear.
Explore content updatesA clear process.
An accountable team.
The work follows the business priorities, agreed capacity, responsible people, and review process. Open each step to see what happens and what it produces.
01Review the system and access.
We establish what the site runs, who controls each service, and which functions must keep working.
A maintenance inventory and coverage brief.
02Plan the changes and recovery route.
We assess dependencies and agree the update sequence, checks, and available restore approach.
An approved maintenance plan.
03Implement and verify.
We perform the scoped updates and check the relevant journeys and technical behavior.
A change and verification record.
04Document the next responsibilities.
We explain unresolved items, provider actions, and the next appropriate maintenance work.
A practical maintenance review.
The support in practice.
A CMS extension update might affect a form or page layout. A considered maintenance task accounts for the available recovery point, applies the approved change, checks the affected functionality, and records any follow-up instead of treating a successful update message as the whole job.
| The question or stage | What we examine | Why it matters |
|---|---|---|
| Preparation | Dependencies and available recovery | Know the system before making the change. |
| Update | The approved technical task | Use an approach suited to the platform. |
| Verification | The functions affected | Check that the business experience still works. |
To show how website maintenance can support a decision. Your support plan and priorities depend on the actual systems, workload, people, and constraints in your brief.
Agree the priorities.
Then scope the support.
The proposal defines the system, update coverage, recovery checks, testing, provider coordination, and response arrangements. Malware cleanup, major compatibility repair, unsupported software replacement, infrastructure work, and emergency response are separate unless included.
| Before we start | What we agree |
|---|---|
| The decision | The business priority, current systems, support need, and boundaries the work needs to address. |
| The deliverables | Management and delivery scope, format, review rounds, responsibilities, and handover. |
| The investment | Written fees, schedule, dependencies, and any separate third-party or implementation costs. |
We confirm the proposal before work begins. You can commission a focused improvement, agree an ongoing support plan, or connect specialist work to a broader service.
Discuss scope and timingUseful questions.
Straightforward answers.
Does maintenance guarantee the site will never be hacked or go down?
No. Maintenance can address defined upkeep and reduce avoidable problems, but no service can guarantee that every software, provider, or security failure will be prevented.
Do all websites need plugin updates?
No. The maintenance plan follows the actual technology. A site without a plugin-based CMS needs a different dependency and release review.
Will you back up the site before updates?
We agree the relevant backup or recovery process before changes. For a typical WordPress site, recovery requires attention to both files and database, not just one visible page.
Can you work with our existing hosting company?
Yes, when the necessary access and provider responsibilities are clear. We distinguish maintenance work from changes only the hosting provider can make.
What happens if an update reveals a larger problem?
We document it, assess the impact, and explain whether it fits the maintenance scope or requires a separate repair or replacement plan.
Is restoring a backup automatically included?
The scope defines restore responsibility, access, coverage, and testing. Having a file called a backup does not by itself establish that a complete restoration has been verified.
How is the work priced and prioritized?
Your proposal defines the workload, deliverables, review rhythm, responsibilities, and fee. We agree priorities within that capacity and identify work that needs a separate estimate. Software, hosting, advertising, creator fees, and other provider costs are listed separately when applicable.
Who will we work with?
You work with a human point of contact supported by the relevant specialists. We agree the communication and approval process, keep a record of decisions, and explain the next priorities in language your team can use.
Keep the ongoing work
connected.
For a related perspective, explore how a website, app, or landing page fits the job. Or return to all Manage services.