Website maintenance
What should a WordPress maintenance service actually include?
Updates are one part of website care. Use this checklist to compare what is covered, how changes are checked and who acts when a problem appears.
A maintenance proposal can sound reassuring without telling you very much. “Regular updates, backups and security” leaves several questions unanswered: how often, checked by whom, and what happens when something breaks?
The right plan depends on what your website does. A brochure site and a busy shop have different recovery needs. Before comparing monthly prices, write down the functions your business relies on and the disruption you could reasonably tolerate. Then use the same questions to assess every proposal.
Backups with an agreed recovery plan
Ask which files and database records are backed up, where copies are stored and who can restore them. A backup on the same hosting account may be unavailable during an account-wide incident. You also need to know how long copies are retained and whether access is independent of the main website.
Frequency should follow the business. If a store takes orders throughout the day, a daily backup can leave a meaningful gap. Agree how much recent data could be lost and how restoration would be handled. Ask for an actual restore check at an agreed interval, rather than relying only on a successful-backup notification. The WordPress backup handbook covers both the installation and its database.
Updates with a way to check and reverse changes
A controlled update process needs a current backup, a rollback method and a list of checks appropriate to the site. On a complex installation, use staging for changes that could affect payments, bookings, memberships or custom code. Keep sensitive production data out of a test environment unless its handling has been agreed.
After updating, check more than the homepage. Test navigation, key layouts and the forms or transactions the business depends on. Security fixes may need a faster response than routine changes, so ask how urgent updates are assessed. WordPress advises backing up before updates in its official update instructions.
A useful website care cycle
- Protect
Keep recoverable backup copies.
- Change
Update with checks and rollback.
- Test
Try the business-critical journeys.
- Report
Record actions, risks and ownership.
Monitoring with somebody responsible for the alert
Ask what is monitored and who receives the notifications. An uptime check can tell you that a page responds while the contact form quietly fails to deliver enquiries. Malware scans, account reviews and business-function checks answer different questions and should be described separately.
The practical test is ownership: if an alert arrives on a Friday evening, who investigates, during which support hours, and what can they change? A plan should state its response arrangements. A response-time target is the time to acknowledge or start assessing an issue; it is not automatically a promise to resolve every issue within that period.
If an infection keeps returning, our guide to recurring WordPress hacks explains the wider recovery questions to ask.
Performance checks that reflect the real website
Keep a baseline for important pages and compare it after substantial changes. Large new images, extra tracking scripts and heavy page-builder sections can change how a site behaves even when its maintenance tasks are complete. The report should explain the finding and recommended action in plain language.
A single automated score is an incomplete picture. Check mobile usability and meaningful interactions, and distinguish a controlled test from data about real visitors. Google describes Core Web Vitals as measures of loading, interactivity and visual stability. They provide useful signals, without proving that the whole customer journey works.
Clear boundaries for support and development
Find out whether content edits, plugin conflicts, malware recovery, hosting problems and custom development are included, limited or quoted separately. Ask how third-party licence renewals are paid for and whether you retain access if you change providers. The same applies to staging sites and backup storage.
For example, fixing a broken existing enquiry form and building a new property-search feature are different jobs. Both may be worthwhile, but the agreement should make the distinction before you need help. A maintenance plan should also name one reliable place to submit requests so an urgent issue does not disappear into a personal message thread.
A short report that helps you make decisions
A monthly summary can be brief: changes made, backup and restore status, important checks, incidents, and items that need your approval. It should identify the actual site and reporting period. A long list of automated green badges adds little if nobody can explain what was checked.
- Can I see what changed and whether it was checked?
- Is the recovery process documented and accessible?
- Are unresolved issues and extra costs clearly listed?
- Do I know how to get help and what the plan covers?
Choose a plan whose responsibilities you understand. The strongest maintenance relationship gives you fewer unanswered questions when the website needs attention.
Sources and further reading
Technical references used for this guide. The checklists and examples are our practical recommendations, adapted to the subject.
WordPress development, website care and practical web integrations. Meet the agency.
