A WordPress care plan should define updates, backups and recovery, monitoring, performance checks, and support responsibilities. The right frequency and response expectations depend on the website’s risk, how often it changes, and the impact of downtime. Confirm the scope in writing rather than assuming every plan includes the same coverage.
Updates and change management
Clarify who maintains WordPress core, plugins, and themes. Ask how compatibility is checked, when a staging environment is used, and how a failed update can be rolled back. A successful update should include a check of important workflows, such as contact forms, checkout, booking, and account access.
Backups are only useful if recovery works
Ask what is backed up, where copies are stored, how long they are retained, and who can restore them. The schedule should reflect how much recent content or transaction data the business can afford to lose. Agree on a restore-testing process and recovery expectations; a backup notification alone does not prove that the site can be recovered.
Monitoring and security responsibilities
- Name the systems being monitored and the hours when alerts are reviewed.
- Define the distinction between detection, acknowledgement, investigation, and resolution.
- Clarify responsibility for hosting, DNS, certificates, user access, and third-party services.
- Document incident escalation, emergency contacts, and any work billed outside the plan.
- Review unused accounts, plugins, and access permissions as part of routine maintenance.
Performance and content checks
A care plan can include monitoring loading performance, broken links, indexing problems, form delivery, and important mobile tasks. Agree on which checks are included and which require a separate optimization project. Use field data when available and keep diagnostic tests comparable; one synthetic score is not the complete user experience.
What should the reporting show?
A useful report states what changed, which checks were completed, problems found, actions taken, and work still needed. Include backup and restore-test status, significant incidents, and upcoming renewals. Reports should help the owner make decisions rather than list activity without explaining its effect.
Questions to ask before signing
- Which tasks and third-party licenses are included?
- What are the support hours and response expectations?
- Who owns the hosting account, domain, backups, and administrator access?
- How are major fixes or development requests estimated?
- How can the site and its documentation be handed to a new provider?
Choose care for your site’s needs
Review our website care and optimization service and WordPress development service. If you are planning a rebuild, use our website budget guide to separate launch costs from ongoing operations. The WordPress backup documentation explains the distinction between database and file backups.
This is a scope checklist, not a statement that every Haketi plan includes every item. The agreed proposal or service contract defines the coverage for your website.