Website maintenance and WordPress development both keep a website useful, but they solve different types of problem. Maintenance is recurring care for a live site. WordPress development is defined technical work that changes how a WordPress website looks, behaves, or connects to other systems. A business may need either service, or both at different points.
Choose website maintenance when the main need is routine updates, backups, monitoring, troubleshooting, content changes, access reviews, and regular checks of forms or customer journeys. Choose WordPress development when the site needs a new template, a substantial form or integration, custom functionality, coordinated technical fixes, or a larger change to existing WordPress code. Hosting is separate from both unless it is expressly included.
What is the difference between website maintenance and WordPress development?
The simplest distinction is the type of responsibility involved.
Website maintenance is an ongoing operating service. It keeps an existing website accurate, functional, recoverable, and supported through agreed recurring checks and smaller tasks. The work is based on the platform, condition, integrations, and level of help the website needs.
WordPress development is technical implementation on a WordPress website. It is normally used for a defined change or group of changes that needs planning, coding, configuration, testing, and approval. The result may be a new template, a changed component, a better form journey, an integration, a technical correction, or another improvement to the way the site works.
This comparison shows the usual difference. The final route depends on the existing website and the work involved.
| Area | Website maintenance | WordPress development |
|---|---|---|
| Primary purpose | Keep a live website working, current, checked, and supported | Make a defined technical change to a WordPress website |
| Typical work | Updates, backups, monitoring, routine troubleshooting, content changes, access checks, and journey testing | Templates, components, forms, integrations, custom behaviour, coordinated fixes, and larger performance changes |
| Timing | Recurring or ongoing | A quoted task or project with an agreed start and completion point |
| Platforms | Can cover WordPress, WooCommerce, Shopify, Wix, and other suitable platforms | Specific to WordPress and WooCommerce |
| Commercial arrangement | Quoted after a review of the site and ongoing responsibilities | Starts from £750 for focused WordPress work |
| Common result | A clearer routine for keeping the website dependable | A tested change to the website’s design, code, functionality, or connections |
What does website maintenance usually include?
Maintenance should be based on an agreed list of responsibilities rather than a vague promise to look after everything. A simple brochure website may need relatively few checks. An ecommerce, booking, membership, or integration-heavy website may need more frequent attention.
Software, platform, and compatibility checks
On WordPress and WooCommerce, maintenance can include controlled updates to WordPress core, themes, plugins, and extensions. Important changes should be backed by a usable recovery route and followed by checks of the parts most likely to be affected. WordPress’s own guidance recommends keeping the software current and backing up before upgrades.
On hosted platforms, the provider manages more of the underlying software, but themes, apps, settings, custom code, and integrations still need oversight.
Backups, monitoring, and recovery readiness
A maintenance routine may check that backups are completing, that the retention period is understood, and that somebody knows how restoration would work. It can also cover uptime alerts, error notices, security-related warnings, and other evidence that a live problem needs attention.
Forms, bookings, checkout, and other customer journeys
A page can load normally while an important action has failed. Maintenance can include real tests of enquiry forms, booking routes, checkout, payment messaging, confirmation emails, and connected systems. The frequency should reflect the commercial importance of the journey.
Content, access, and routine changes
Smaller text, image, product, service, form, and policy updates can sit within maintenance when the agreement says so. User access, administrator accounts, domains, licences, and important supplier details may also need periodic review.
For a fuller recurring schedule, use the Website Maintenance Checklist for Business Websites.
What does WordPress development usually include?
WordPress Development is appropriate when the request changes the site rather than simply maintaining the existing arrangement. The work can be small and focused, but it normally needs its own technical assessment, implementation, testing, and approval.
Templates, layouts, and reusable components
A business may need a new page template, a revised header or footer component, a different product layout, improved responsive behaviour, or a reusable block that the existing site does not provide. These changes can affect several pages and therefore need controlled testing across screen sizes and content variations.
Forms, integrations, and technical workflows
Adding a simple field to an existing form may fit routine support. Building a multi-step enquiry process, connecting a form to a CRM, changing booking logic, or coordinating data between systems is more likely to be development work.
Custom behaviour and coordinated technical fixes
Development can include repairing theme or plugin conflicts, changing custom code, improving a slow template or database-heavy process, creating a safer replacement for unsupported functionality, or coordinating several technical fixes that need to be tested together.
WordPress separates presentation from broader functionality in its development guidance. Depending on the purpose, a change may belong in a theme, a plugin, or another suitable component. A responsible developer should place the work where it can be maintained safely rather than forcing every change into one file or tool.
Where do maintenance and WordPress development overlap?
The boundary becomes clearer when the initial task and the resulting work are separated. Maintenance may reveal the problem. Development may be the correct way to solve it.
An update causes a form problem
Detecting the failure, restoring a stable version, and identifying the affected component can be part of maintenance. If the permanent fix requires changed code, a replacement integration, or a rebuilt form journey, that work may become a separate WordPress development task.
A routine content request needs a new layout
Replacing text and images within an existing page can fit maintenance. Creating a new reusable layout, introducing new responsive behaviour, or changing several templates together is development.
Monitoring identifies a performance problem
Checking loading behaviour and identifying a slowdown can sit within maintenance. Reworking theme code, database queries, scripts, or a complex plugin setup may require a defined development project.
A small form change becomes a new process
Changing a label or recipient may be routine. Adding conditional steps, file handling, CRM routing, notifications, permissions, or new data processing needs may require technical planning and testing beyond normal support.
When should a request be treated as a WordPress development project?
A separate development quote is usually clearer when one or more of the following applies:
- The request introduces a new feature, template, integration, or technical workflow.
- Several connected parts of the website need to change together.
- Custom code must be written, replaced, or materially changed.
- The work could affect checkout, bookings, payments, customer accounts, or stored data.
- A staging site, technical specification, migration plan, or structured testing process is required.
- The likely time cannot be covered sensibly by the routine tasks in an ongoing support agreement.
- A third-party theme, plugin, or integration needs substantial corrective work.
A larger visual or structural problem may instead need a Website Redesign. If the current site no longer reflects the offer, navigation, page structure, or customer journey, treating every symptom as a separate development fix can be less efficient than reviewing the wider website.
Is website maintenance only for WordPress websites?
No. Our Website Maintenance & Support service is platform-neutral and can cover WordPress, WooCommerce, Shopify, Wix, and other platforms that can be managed competently after review. The tasks differ because each platform divides responsibility in a different way.
- WordPress and WooCommerce: the website normally has direct responsibility for core software, themes, plugins, extensions, hosting compatibility, and updates.
- Shopify: Shopify manages the hosted platform, while the business still needs oversight of themes, apps, products, collections, payments, delivery settings, staff access, content, and integrations.
- Wix: Wix manages the hosted platform, while forms, bookings, ecommerce settings, apps, domains, permissions, content, and customer journeys still need checking.
WordPress development is different because it is specifically a technical service for WordPress and WooCommerce websites.
How do cost and timing differ?
Website Maintenance & Support is quoted after the website, platform, access, integrations, current condition, and expected level of help have been reviewed. The ongoing fee should reflect the recurring responsibilities, request volume, response expectations, and any limits that have been agreed.
Focused WordPress Development starts from £750. The final price depends on the current code and setup, the change required, the number of connected components, third-party dependencies, testing, and the condition of the existing website.
Managed WordPress Hosting is separate. Standard WordPress hosting is £30 per month or £360 per year, while WooCommerce or higher-resource hosting starts from £45 per month. Hosting provides the agreed hosting environment and related administration. It does not automatically include WordPress updates, content changes, development, or the wider maintenance service.
For a broader view of build and recurring costs, see How Much Does a Business Website Cost in the UK?.
What should be agreed before either service begins?
Clear responsibilities reduce uncertainty and make it easier to identify when a request needs a separate quote. Before ongoing maintenance or a development project begins, confirm:
- The website, environments, and third-party systems covered.
- The tasks included and the work that remains separate.
- Who controls the domain, hosting, licences, administrator accounts, and recovery details.
- How requests are submitted, prioritised, approved, and recorded.
- What response expectations apply to routine and urgent problems.
- How backups, staging, testing, and rollback will be handled where relevant.
- Who supplies and approves business information, legal wording, product data, and regulated content.
- What happens when investigation reveals larger development, redesign, SEO, security, or specialist work.
An inherited WordPress website should be reviewed before firm commitments are made. Outdated components, unsupported code, missing access, undocumented changes, or previous security problems can affect what is safe to maintain and what needs correction first.
Can a business need maintenance and WordPress development at the same time?
Yes. A WordPress website may have an ongoing maintenance arrangement for routine care while defined improvements are quoted as separate development projects. This keeps the regular service predictable without forcing larger changes into an unlimited support promise.
For example, maintenance might cover updates, backups, form tests, content changes, and monitoring. A separate development project could then add a CRM integration, replace an unsupported booking component, or create a new template. After the project is tested and launched, its recurring checks can be added to the maintenance agreement if appropriate.
The two services work well together when the boundary is clear: maintenance protects the live website, while development changes it in a controlled way.
Common questions about website maintenance and WordPress development
Can a website maintenance provider support a WordPress website built by another developer?
Yes. Many website maintenance providers support WordPress websites built by other developers or agencies. Before taking responsibility for an existing website, the provider should review its hosting, WordPress version, theme, plugins, custom code, backups, and administrator access. Unsupported components, security concerns, or undocumented changes may need attention before ongoing support can begin. A suitable existing website does not need rebuilding simply because a different developer created it.
Can I pay for a one-off WordPress repair without a maintenance contract?
Yes. WordPress developers can carry out separately quoted repairs and technical changes without requiring an ongoing maintenance agreement. One-off work might include fixing a broken form, resolving a plugin conflict, correcting a layout problem, or repairing existing functionality. The quote should explain what will be investigated, which changes are included, how the work will be tested, and whether any additional problems would require separate approval. Ongoing monitoring and software maintenance are separate unless specifically included.
Do I need to change my hosting or domain when hiring a website maintenance provider?
No. You can generally keep your existing hosting and domain when arranging website maintenance. The provider will need suitable access and must be satisfied that the hosting environment allows the website to be maintained safely. If the hosting is unreliable, outdated, or incompatible with the website’s requirements, a move may be recommended. Changing your maintenance provider does not require transferring ownership of your domain, and your business should retain control of its important accounts.
What should I do if a WordPress plugin is no longer supported?
Start by identifying what the plugin does and whether it remains compatible with your current WordPress setup. Confirm that a suitable backup is available before making changes. An unsupported plugin may need replacing, particularly if it has security vulnerabilities or is causing compatibility problems. Removing it without checking its dependencies could break forms, layouts, checkout, or other website features. A developer can assess the available replacements, plan the change, and test the affected functionality. More substantial replacement work may need a separate development quote.
Should I expect 24-hour emergency support from a standard website maintenance agreement?
No. You should not assume that a standard website maintenance agreement includes 24-hour or out-of-hours emergency support. Availability, response times, and the handling of urgent incidents vary between providers and service agreements. Before committing, confirm how website outages are reported, when support is available, which problems are covered, and whether emergency work incurs additional charges. Your hosting provider may also have a separate role in resolving server or infrastructure problems.
Does a one-off WordPress development project include ongoing website maintenance?
No. A one-off development project normally covers defined changes, appropriate testing, and handover rather than continuing website maintenance, unless the agreement specifically includes it. Any responsibility for correcting defects in the completed work should be established in the project terms. Future WordPress updates, plugin monitoring, backups, content changes, and additional development are separate responsibilities. You can arrange ongoing maintenance with the same developer, another suitable provider, or manage it internally.
Can WordPress changes be made without taking my website offline?
Yes. Many WordPress changes can be prepared and tested on a staging website before being introduced to the live site. This helps reduce disruption to visitors and customers. However, changes involving WooCommerce checkout, active orders, booking systems, customer accounts, or stored data may require additional planning and sometimes a short interruption. The developer should assess the risks, identify what needs testing, and agree any expected downtime before implementing changes that could affect customers.
Need help with an existing website?
Start with the problem and the result you need.
Tell us whether the website needs ongoing care, a defined WordPress change, or both. We’ll review the current position and recommend the most useful next step.
WordPress responsibilities were checked against current official WordPress site maintenance guidance, WordPress updating guidance, and the WordPress developer guidance on themes and functionality. Exact plugin, theme, hosting, and integration requirements depend on the live website and can change over time.
