Web & Software
Website Maintenance
A website is never really finished - software needs updating, links break, and small content changes accumulate. This service keeps a live site secure, current, and working without requiring an in-house developer.
Website maintenance is the ongoing technical care of a live website after launch: keeping software current, watching for downtime, protecting against common security issues, and making the small content and functionality changes a business needs week to week. It is distinct from a redesign or new build - maintenance assumes the site's structure is right and focuses on keeping it healthy and current.
For sites built on a content management system such as WordPress, this typically includes core, plugin, and theme updates, which matter because outdated software is one of the most common ways websites are compromised. For any platform, it also includes monitoring uptime, checking that forms and key functionality still work, and responding when something breaks unexpectedly rather than waiting for a customer to report it.
Buyer fit
Is this the right service for you?
Maintenance is the right service whenever a live website exists and no one internally has the time or expertise to keep it current.
Good fit when
- Businesses without an in-house developer who need someone accountable for keeping the site secure and working.
- Sites on WordPress or similar platforms that accumulate plugin and core updates requiring careful testing before applying.
- Organizations that need routine small content changes handled reliably without a new project scope each time.
- Anyone who has experienced a site going down, getting compromised, or silently breaking without noticing.
Less suitable when
- Sites needing a structural redesign or platform change - see website redesign or the relevant platform page.
- One-off content or design changes better scoped as a small project than an ongoing retainer.
- Brand-new builds with no live site yet - maintenance begins once a site is in production.
Scope
What's included
A maintenance arrangement is typically built around a recurring schedule with defined response expectations for issues.
Core, plugin, and theme updates
Scheduled updates applied and tested in a staging environment before going live where feasible.
Backups
Regular automated backups stored separately from the live server, with a tested restoration process.
Uptime monitoring
Automated checks that alert the team if the site goes down or responds abnormally slowly.
Security review
Periodic checks for known vulnerabilities, suspicious file changes, and outdated software versions.
Performance checks
Ongoing review of page speed and flags for pages that regress after updates or content additions.
Content and small change requests
A defined process and allowance for routine text, image, and minor functionality updates.
Not included in this service
- • Large new feature development or structural redesign, which is scoped as a separate project.
- • Recovery from an existing, undisclosed compromise discovered after the arrangement starts - assessed and quoted separately if found.
- • Content strategy or marketing campaign work, covered under digital marketing services.
Process
How the work happens
Maintenance runs on a recurring cycle with an escalation path for anything unexpected between scheduled checks.
- 1
Baseline audit
Review current software versions, backup status, and known issues before the arrangement starts.
- 2
Recurring update cycle
Apply and test updates on a set schedule, with staging review for higher-risk changes.
- 3
Monitoring
Automated uptime and error monitoring runs continuously, with alerts routed to the maintenance team.
- 4
Change requests
Routine content or small functionality changes are logged, actioned, and confirmed within the agreed allowance.
- 5
Reporting
A periodic summary of updates applied, issues found, and outstanding recommendations.
Decision support
How much maintenance coverage do you need?
Coverage level should match how business-critical the site is and how quickly issues need attention.
| Situation | Recommended path | Why |
|---|---|---|
| Site is core to lead generation or revenue | Full maintenance with monitoring and fast response | Higher recurring cost, lower risk |
| Site is informational with lower traffic | Lighter maintenance - updates and backups only | Lower cost, slower response expectations |
| Site changes rarely and content is stable | Quarterly review instead of a full retainer | May still need updates applied for security |
Measurement
How results are checked
Maintenance quality is tracked with concrete records rather than a general sense that 'someone is looking after it.'
- Update logs show what was applied, when, and whether testing found any conflicts.
- Backup restoration is periodically tested, not just assumed to work.
- Uptime and incident records show how quickly issues were detected and resolved.
- Outstanding security or performance recommendations are tracked until resolved or explicitly deferred.
Engagement factors
What affects scope and pricing
Maintenance scope and pricing are shaped by these factors more than anything else.
- Platform and complexity of the site - a simple brochure site and a large e-commerce catalog need different attention.
- Response-time expectations for downtime or urgent issues.
- Volume of routine content or small change requests included each period.
- Whether the site has custom code that needs manual testing after each update.
FAQ
Common questions about website maintenance
What happens if our site goes down outside business hours?
Monitoring alerts are set up to flag downtime as soon as it is detected; actual response timing depends on the coverage level agreed in your maintenance arrangement.
Do you fix a site that is already broken or hacked?
Recovery and cleanup work can be scoped once the current state is assessed; ongoing maintenance is priced separately from a one-time recovery project.
How often are updates applied?
This is agreed as part of the arrangement - many sites are updated on a monthly cycle, with critical security updates applied sooner.
Can you also make small design or content changes?
Yes, routine content and small functionality changes are typically included up to an agreed allowance, with larger requests scoped separately.
Do we need maintenance if our developer already handles some updates?
Maintenance can complement an internal team by covering monitoring, backups, and routine tasks, freeing internal developers for larger project work.
Ready to talk about website maintenance?
Share a bit about your situation and goals — we'll follow up to confirm scope and next steps.