Service
Website Maintenance
At a glance
Engagement model
- Deliverables
- 10 defined outputs
- Pricing
- Monthly retainer with a defined task allowance. Plans are scoped to platform, traffic and support expectations.
- Next step
- A short call, then a written proposal
- Software, plugin and dependency updates, tested on staging before deployment
- Scheduled backups with retention and documented restore procedure
- Security checks: configuration review, user access audit, common vulnerability scans
The context
What website maintenance actually involves
Websites are software. Frameworks release security patches, dependencies drift out of compatibility, forms silently stop delivering and a broken link appears every time a page is renamed. Maintenance is the difference between a site that quietly degrades and one that stays dependable.
Our maintenance engagements are deliberately unglamorous and clearly scoped: a defined set of recurring tasks, a support channel for requests, and a written record of what was done each month.
Problems this solves
Nobody is responsible for the site between projects
Updates get postponed, backups are assumed to exist, and the first sign of trouble is a broken page or a security warning from the host.
Enquiries go missing without anyone noticing
A form breaks after a spam-filter change or an email provider update, and weeks of leads disappear into a log nobody reads. We test the enquiry path continuously.
Small content changes take too long
Adding a team member, publishing an offer or changing a price becomes a multi-day back-and-forth. A retainer gives you a predictable way to request small changes.
Security exposure on unpatched platforms
Outdated plugins and dependencies are the most common route into small business sites. Regular patching on a staging copy first reduces risk substantially.
What you get
Deliverables, defined in advance
- Software, plugin and dependency updates, tested on staging before deployment
- Scheduled backups with retention and documented restore procedure
- Security checks: configuration review, user access audit, common vulnerability scans
- Bug fixes for issues within the maintained scope
- Broken link and error monitoring with periodic reports
- Uptime and performance monitoring with alerting
- Monthly content updates and small edits within an agreed time allowance
- Cross-browser and mobile compatibility checks
- Form and enquiry-path testing
- A written monthly summary of work completed and issues found
Why it matters
Business benefits
Fewer surprises
Recurring checks surface problems while they are still small — before a security incident or a week of missed leads.
Predictable support
You know who to contact, what is covered and how quickly to expect a response, instead of hiring a developer for each individual task.
A stable base for marketing
SEO and campaign performance depend on a site that loads, tracks and converts correctly every day of the month.
Process
How the engagement runs
- Step 1
Audit and onboarding
We document the current stack, access, backup status and known issues, then fix any immediate risks before starting the recurring schedule.
- Step 2
Monthly cycle
Updates and backups run on a fixed schedule; content requests are handled through a single request channel with an agreed time allowance.
- Step 3
Testing and reporting
Each change is verified on staging, then in production, and summarised in a short monthly report showing what changed and what remains open.
- Step 4
Escalation
Unexpected outages or security incidents are triaged immediately during business hours, with an agreed response window defined in the plan.
What a maintenance plan should include
A useful plan specifies: which platform and components are updated, how backups are stored and how often, what counts as a fix versus a new feature, how many content changes are included, what the response window is, and where requests should be submitted. Without those definitions, retainers turn into disputes about scope.
We publish those terms in the proposal before the engagement starts, so both sides know what "covered" means. Work outside scope — new pages, new functionality, redesigns — is quoted separately rather than absorbed or refused case by case.
Security and availability: realistic expectations
Maintenance reduces risk; it does not eliminate it. No provider can promise absolute security or uninterrupted availability, because hosting, third-party services and network infrastructure sit outside any single agency's control. What we can commit to is defined monitoring, prompt patching, tested backups and a clear incident response process.
Where a platform is end-of-life or a dependency cannot be safely patched, we say so and recommend a migration path instead of applying cosmetic fixes to a fragile system.
What we do not promise
- We do not guarantee uninterrupted availability or absolute security. Uptime depends on hosting and third-party infrastructure; our commitment is to monitoring, patching and response times defined in the plan.
- New features, new pages and redesigns are not covered by maintenance time and are quoted separately.
- Emergency response outside business hours requires a specific arrangement agreed in advance.
How pricing works
Monthly retainer with a defined task allowance. Plans are scoped to platform, traffic and support expectations.
Advertising spend, platform subscriptions and third-party licences are paid by you directly and are always shown separately from our fee.
See pricing approachQuestions
Website Maintenance FAQ
No. You can maintain it yourself or with another provider. We simply recommend that someone owns updates, backups and form testing, because those are the tasks most often missed.
Usually yes, after a short onboarding audit to understand the stack, access and any existing issues. If the codebase is too fragile to maintain safely, we will say so upfront.
Response windows are agreed in the plan based on severity. Typical business-hours plans triage site-down and security issues first, with content requests handled in the scheduled cycle.
Related
Services that work well alongside this
Start here
Ask about website maintenance
- Reply within one to two business days
- Written proposal with scope and fees
- No obligation and no pressure to proceed
Before you write
The more specific the context, the more useful the first reply. Useful things to mention:
- What the business sells, and to whom
- What is not working right now
- Any deadline or budget range already agreed internally
We do not publish guaranteed rankings, revenue projections or invented case results. If something cannot be judged without access to your accounts, we will say so.