Start with the site you actually operate
A simple service website and an online operation with accounts, bookings or payments have different dependencies. Inventory the platform, important extensions, hosting, custom code and critical customer tasks. Then define the coverage around that setup.
This prevents a familiar gap: one provider assumes the host handles a problem while the host assumes it belongs to the website developer. A care plan should identify those boundaries before an incident makes them urgent.
Treat updates as managed changes
WordPress’s maintenance guidance includes keeping the site updated and maintaining backups. The practical question is how the update work will be handled for your site. Define the relevant preparation, the changes in scope and the checks that follow.
For a business website, a useful check may include the inquiry form, a key landing page or a supported booking journey. The dashboard showing a completed update is not the same as confirming that the customer-facing task still works.
Ask about recovery, not just backup frequency
Know what is included in a backup, where responsibility for it sits and how a restore would be initiated. An agreement should distinguish monitoring a backup from carrying out recovery work. The same applies to host-level copies and backups managed by another provider.
Ask who has the access needed to act and which recovery arrangements are actually covered. Clear responsibilities are more useful than a list of reassuring technical words that leaves restoration unassigned.
Make support allowances understandable
A monthly plan may include a defined allowance for minor edits or troubleshooting. Find out what counts toward that allowance, whether unused time rolls over and which requests require a separate scope. Hosting, paid licenses, emergency work and a redesign should not be assumed to be included without confirmation.
A good plan also explains the request channel and normal response expectations. Your team should know where to submit work and how priorities are agreed.
Keep care separate from growth strategy
Maintenance can protect the usefulness of the current site, while SEO, content planning and conversion improvements address different goals. They can be coordinated, but a basic update plan should not be sold as a complete growth program.
Run It Right can review an existing site and define a care engagement where the platform and condition are a good fit. If the foundation needs larger repairs, we explain that before treating an ongoing retainer as the solution.
Use a practical comparison checklist
When comparing providers, ask for plain answers to the questions below. The best fit is the plan with clear responsibilities for your website—not necessarily the longest feature list.
- Which platform and components are covered?
- What checks follow updates?
- Who monitors backups and who performs restores?
- What support time is included?
- Which costs and situations are outside the plan?
Connect this to your business.
Explore our website maintenance & care service for the approach, deliverables and next steps. For more buying questions, visit the FAQ hub.
Sources & further reading
Platform guidance can change. This article provides general information; your engagement defines the scope and responsibilities for your business.
