Choose the right maintenance task
Use WordPress support for CMS updates, PHP support for a runtime change, and recovery for a broken site. A monthly plan coordinates recurring work; a malware incident needs cleanup first. We inspect the existing setup and define the result before changing it.
Separate maintenance from repair
Map platform components, backups and customer journeys. An abandoned theme or broken custom integration may require repair before recurring updates become reliable. Maintenance coverage should reflect the actual site.
- Inventory components and key journeys.
- Review backup/update prerequisites.
- Choose backlog work or recurring care.
- Record changes and results.
Choose updates, care or cleanup
Keep a record of what changed, evidence of function and unresolved actions. Separate plugin licences, hosting responsibilities and developer work. Current components help address known problems without guaranteeing immunity from failure or attack.
| Need | Route | Boundary |
|---|---|---|
| Update backlog | One-time task | Compatibility repair separate |
| Regular checks | Care plan | Coverage and time agreed |
| Malicious changes | Cleanup assessment | Updates do not prove a clean site |
Example: scope checkout checks before an update
A store update includes approved checkout checks; replacing abandoned custom code needs a separate estimate. This is an illustrative scenario, not a customer case or a promised result.