WordPress maintenance and ongoing support

Routine maintenance covers predictable recurring work such as supported updates, backups, health checks and verification. New features, redesigns and substantial compatibility rewrites should be scoped separately so the retainer remains understandable.

WordPress currently recommends keeping core, plugins and themes up to date. The important operational question is how those updates are tested on a site that contains custom code, payments or integrations.

A backup has limited value if nobody knows its retention, storage location or restore process. Business sites should know which database, uploads, configuration and external records are recoverable and how long a restore is expected to take.

Before a high-risk update, the restore path should be known rather than discovered during an outage.

Custom themes, old plugins, PHP changes and WooCommerce updates can alter behavior without producing an obvious fatal error. Acceptance checks should cover forms, checkout, scheduled jobs, key admin screens and integrations relevant to the site.

Maintenance for a brochure site and maintenance for an order-processing store are therefore different scopes.

The maintenance agreement should say what counts as routine work, what becomes an incident, and what requires a separate development estimate. It should also define response channels and who can approve emergency changes.

This avoids both unlimited-support expectations and the opposite problem where a business assumes an urgent production failure is covered but the supplier does not.

A longer plugin list does not automatically mean more maintenance value. A better review asks whether updates are current, backups are usable, critical customer journeys work, security warnings are handled and recurring defects are declining.

The goal is a production site that remains dependable as its dependencies change.