Website maintenance cost depends on the website’s platform, functionality, current condition and support requirements. The useful starting point is a list of responsibilities: what needs checking, who handles changes and how problems will be resolved.
A website that looks unchanged can still depend on updated software, active licences, reliable forms and working integrations. For an enquiry-led business, a broken contact form may matter more than a visible design issue. Maintenance should reflect how the website supports the business.
What should routine website maintenance include?
A care plan should identify the checks and actions that apply to your site, together with their frequency. Avoid relying on a broad label such as “ongoing support” without a description of the work.
- Software updates: define who reviews and applies changes to the platform, theme and plugins, and how important functions are tested afterwards.
- Backups and recovery: clarify what is backed up, where copies are kept, how long they are retained and who can restore them.
- Enquiry checks: test the path from form completion through confirmation to receipt in the intended inbox.
- Availability and errors: agree how failures are detected, who receives alerts and how issues are escalated.
- Access and renewals: keep ownership of the domain, hosting and essential accounts clear. Identify the person responsible for each renewal.
- Change records: retain a useful account of updates, fixes and unresolved issues so the next decision has context.
Why do different websites need different levels of care?
A brochure website with occasional edits has different operational needs from a store processing orders every day. Custom integrations, frequent publishing and multiple editors introduce more things to check when a change is made.
The existing condition also matters. An outdated installation, undocumented custom code or missing account access may require initial investigation before routine maintenance can begin. Ask whether this initial work is separate from the ongoing arrangement.
Response expectations affect the scope too. Specify the difference between acknowledging a request, starting an investigation and resolving the issue. A response commitment is not automatically a promise that every problem can be fixed within the same period.
Does hosting cover website maintenance?
Hosting and website maintenance can be provided together, but their responsibilities differ. Check the actual service agreement. A hosting provider may handle infrastructure while leaving website functionality, content changes and plugin compatibility to the website owner or developer.
Ask who investigates if the site loads normally but enquiries do not arrive. The cause could involve the form, mail configuration or a third-party service. Clear ownership makes it easier to follow the whole problem through.
What deserves attention on a WordPress website?
Start with an inventory of active themes, plugins, licences and custom features. Keep track of what each component does before changing it. Test the customer journey after significant updates, especially forms, payments, navigation and mobile layouts.
A complete WordPress recovery plan needs both the files and the database. The official WordPress backup guide explains the distinction. Ask for evidence that a backup can be restored, not simply confirmation that a backup task ran.
Decide how much recent information the business could afford to lose. That decision helps define an appropriate backup schedule and recovery process. A frequently updated website may need a different approach from a site that changes only occasionally.
What should be scoped separately?
New page designs, substantial copywriting, custom functionality and a full redesign are different kinds of work from routine upkeep. Small edits may be included in a care plan, but their limits should be stated.
Search optimisation also needs a clear boundary. Keeping the site technically healthy supports visibility, while keyword research, content development and ongoing search analysis require their own work plan. Read our SEO audit checklist if visibility is the main concern.
Questions to ask before arranging support
- Which tasks are included, and how often are they carried out?
- Who owns the accounts, licences and backup copies?
- How are urgent problems reported and prioritised?
- Which edits are included, and how is additional work agreed?
- What happens when a third-party service causes a problem?
- How will work and outstanding issues be reported?
- What access and documentation will be handed over if the arrangement ends?
Discuss care for your existing website
Send Fovoya your website address, platform if known and the issues or recurring tasks you need help with. Describe which customer actions are most important. That gives us a practical starting point for discussing care and support.
Discuss website maintenance · Explore website care and support
