WordPress maintenance is the ongoing work around an existing site: understanding its components, reviewing updates, keeping a recovery route and checking that important functions still work. This page explains that workflow; the separate hosting page covers the server offer.
A useful maintenance cycle accounts for plugins, theme, compatibility and recovery before checking the changed site.
- Component review
- Supported updates
- Functional checks
Start with the site's dependencies
Record WordPress, active plugins and theme, vendor licences, custom code, forms, scheduled work and external services. Identify the owner of each business-critical function. A plugin being installed does not establish that it is supported or has valid update access.
Before, during and after an update
- Review the change. Check the vendor's release notes and compatibility information, including any required runtime or database changes.
- Confirm recovery. Identify a usable copy and the data it covers before changing the site.
- Test where appropriate. Use an agreed staging environment for changes that need review, with test activity separated from real customer actions.
- Check the functions. Review navigation, media, enquiry delivery, logins and the affected integrations. Stores need authorised checkout and order-flow checks.
- Record the result. Note versions, the checks performed, unresolved issues and who owns the next action.
WordPress's update guidance recommends backing up before an update. Its plugin guidance also explains update availability and compatibility checks.
Routine care and additional work
Supported WordPress core and plugin update care is part of the published managed hosting offer, subject to the agreed scope. A broken custom integration, abandoned component, redesign or major rebuild may need separately scoped work. Premium vendor licences may remain the customer's responsibility.
The coverage guide is the reference for included care versus additional technical management. There is no separate maintenance price or unlimited-repair promise on this page.
When the site receives orders or member activity
Plan around data arriving during the change. Restoring an older database can affect newer records. Agree the acceptable recovery point and reconciliation work before authorising a replacement. Use the recovery checklist and store-specific hosting guide.
Keep the developer and hosting roles clear
Agree who changes code, who owns licences, who approves publication and where a problem is reported. Monitoring can identify a symptom; human investigation and remediation coverage follow the Service Summary.
WordPress maintenance questions
Does an update notification mean the change is safe?
It identifies an available update. Review compatibility, recovery and the functions affected before treating the change as accepted.
What happens if a vendor stops supporting a plugin?
Review replacement or redevelopment options with the site owner. Do not assume a routine update can make an abandoned component supported.
Can you help with an existing WordPress site?
Start with the public URL and component list. We assess hosting compatibility and the work required before confirming service.
Related WordPress guidance
Review your WordPress maintenance coverage
Tell us the public site URL, platform and the work you need. We will confirm the scope and responsibilities before quoting.
Ask about your site