WordPress maintenance
WordPress maintenance with checks before every significant change.
Updates are one part of maintenance. We check compatibility, preserve a way to roll back and make sure the website's essential features continue to work.
A defined scope, quotation and agreed checks.
Know what changed and why.
We begin by reviewing WordPress, the theme, active plugins, hosting and custom changes. We identify critical functions such as orders, forms, memberships, bookings and connections to external services.
We then agree the scope: regular updates, technical issues, content changes or development. Security work reduces risk, but cannot guarantee that a website will never be attacked.
SCOPE OF WORK
How we can help
The exact activities are set out in the proposal for your project.
Updates with compatibility checks
We review changes to WordPress, the theme and plugins. For higher-risk updates, we use a staging copy where the environment allows it.
Backup and recovery
We define what is backed up, where the copy is stored and how it can be restored. We check that the database and files belong to the same version.
Checks of essential features
After changes, we test the agreed user journeys: sign-in, forms and search, and, for WooCommerce, product pages, basket and checkout.
Troubleshooting
We investigate PHP errors, plugin conflicts, broken layouts and notification delivery problems. We identify the cause before changing working components.
Performance and resources
We review images, requests, resource-heavy plugins and caching. We measure improvements while retaining the functionality you need.
A clear record of the work
We document changes, checks and remaining dependencies. New features are agreed as separate tasks when they fall outside the maintenance scope.

Attention to detail
Check first. Then change.
Before a significant change, we check backups and dependencies. Where the project allows, we prepare a staging copy and compare essential pages and forms before transferring the verified change to the live website.
Discuss your projectPROJECT PROCESS
From the first conversation to a checked result
Initial review
We gather information about the website and the issue. Access is shared through an agreed secure method.
Work plan
We prioritise critical fixes and regular tasks, and agree a maintenance window, backup and any expected downtime.
Implementation and report
We make the changes, check essential features and provide a short report covering the result and any next steps.
BEFORE WE BEGIN
Help us get started sooner
- Your website address and a description of the issue or regular maintenance required.
- When you first noticed the issue and what changes preceded it.
- Information about hosting and available backups.
- A list of paid themes and plugins, and whether their licences are active.
BEFORE YOUR ENQUIRY
Frequently asked questions
Can you maintain a website built by another team?
Yes, after an initial review. This establishes what is installed, which licences are needed and whether custom changes could be lost during a standard update.
Can I request a one-off fix?
Yes. Describe the issue and send the website address. After reviewing it, we agree the task and price without requiring a subscription.
Will orders and customer records be preserved?
Yes, they form part of the data that must be preserved. We plan changes and backups around store activity and do not restore an old database over new orders without a separate plan.
What if an update breaks the website?
We prepare a backup and rollback plan in advance. We decide whether to restore files, fix the incompatibility or postpone the update, taking account of data created since the backup.
Need a specific fix or regular maintenance?
Describe what is happening and provide the website address. We will identify the next check needed.