A known baseline
The website is stable enough to maintain, or has completed an agreed recovery, Audit or Delivery phase.
WordPress Maintenance & Support
Keep your WordPress site stable, current and ready for change.
WordPress Maintenance & Support provides controlled updates, backup verification, compatibility checks, monitoring and defined ongoing help after an agreed baseline is accepted.
When recurring maintenance is the right route
Maintenance protects a known operating state. It is not the first step for an actively broken site or an unknown technical root cause.
Recurring operational work
The team needs controlled update cycles, verification, reporting and defined support—not an undefined development retainer.
Business-critical workflows
Forms, booking, checkout, publishing, tracking or other named journeys need repeatable checks after change.
Maintenance Readiness & Onboarding
| Starting profile | One-time onboarding | Typical fit |
|---|---|---|
| Stable standard site | $500 USD | Ready access and backups, a standard dependency surface and a known stable baseline. |
| Stable complex site | $1,000 USD | Booking, commerce, integrations, custom code, several critical workflows or server coordination. |
| Stable high-complexity scope | $1,500 USD | Several environments, complex dependencies, incomplete documentation or a bounded multisite scope. |
Typical onboarding takes 2–3 working days after access readiness. It establishes an inventory, safety path and documented maintenance baseline. A small bounded readiness correction may be included; active instability, a broken critical workflow or material remediation receives a separate quote.
Compare Ongoing Maintenance plans
Compare the same recurring maintenance baseline at two levels of site complexity and operational responsibility.
| Dimension | Ongoing Maintenance — $300 USD per month | Broader-scope Ongoing Maintenance — $500 USD per month |
|---|---|---|
| Best fit | One accepted stable WordPress site with a standard stack, managed hosting, a small number of critical workflows, moderate update complexity and a low change frequency. | One accepted stable WordPress site with greater operational responsibility, such as booking, commerce, integrations, custom code, page-builder risk, several critical workflows, higher business criticality or regular provider coordination. |
| Shared recurring baseline | Monitoring and backup oversight, controlled updates, validation of agreed critical workflows, human triage and a human-readable monthly report. | The same recurring baseline. |
| Controlled cadence | One controlled human review, update and validation cycle each week, supported by the existing automated monitoring and detection layer. | The same weekly controlled cycle, with the deeper validation and coordination required by the more complex site. |
| Main difference | Standard testing and coordination appropriate to a known stable baseline. | Deeper staging-first validation, dependency awareness and coordination appropriate to the more complex site. |
| When Custom is needed | Route to Custom when the responsibility exceeds a stable single-site baseline. | Route to Custom for multiple sites, multisite or portfolio governance, significant Linux or server responsibility, high change frequency, custom-application responsibility, active third-party delivery teams or after-hours coverage. |
Both plans begin only after an accepted stable baseline. Critical security issues are assessed promptly within covered business hours, without a guaranteed resolution time. Continuous Improvement is separate from base Maintenance. Work that becomes Recovery, Audit or Delivery receives a separate scope. Custom Maintenance can include coordination with third-party teams and vendors.
Start with an onboarding baseline review
- Inventory the maintenance surface. Confirm sites, hosting, WordPress, themes, plugins, page builders, licenses, integrations and owners.
- Verify the safety path. Review backups, staging, recovery readiness, release access and the critical workflows that require checks.
- Accept or redirect the baseline. A suitable site enters recurring care; unresolved instability routes first to Technical Audit, Update Recovery or Modernization Delivery.
- Agree the operating boundary. Define cadence, included modules, reporting, support boundaries, escalation and response commitments.
A controlled recurring cycle
1. Review
Check available updates, compatibility information, public maintenance signals, recent incidents and planned business changes.
2. Prepare
Confirm backup and recovery readiness, use staging where appropriate and define the workflows that must pass.
3. Change
Apply agreed updates or small changes in controlled batches instead of treating every available update as automatically safe.
4. Verify
Check the named customer, editorial and measurement workflows affected by the cycle.
5. Report
Record completed work, observations, residual risks and the next planned review.
6. Escalate
Move recovery, redesign, migration or larger engineering work into a separately approved scope.
What the recurring scope can include
WordPress and dependency care
Core, theme, plugin and page-builder update review, compatibility checks and controlled releases.
Backup and recovery readiness
Verification that agreed backups, staging and rollback paths remain usable before higher-risk change.
Critical-workflow checks
Repeatable checks for forms, booking, checkout, publishing, analytics or other agreed business journeys.
Monitoring and reporting
Public availability and maintenance-signal review, change records, observations and risk escalation.
Hosting and server care
Linux / Server Administration and hosting maintenance only when responsibility is explicitly included.
Defined support and improvement
A clearly limited scope for small support or improvement work, with larger changes reviewed separately.
Choose Ongoing Maintenance or Continuous Improvement
The two modes may coexist in one recurring agreement, but their scope, priorities and escalation boundary must remain visible.
Ongoing Maintenance
Protect an accepted baseline through controlled updates, compatibility review, recovery readiness, critical-workflow checks, reporting and risk escalation.
Continuous Improvement
Use a separately scoped and approved backlog for small purposeful enhancements. Larger features, redesign, refactoring or migration remain separate Delivery work.
A real proposal should include a coverage matrix showing sites, environments, dependencies, workflows, cadence and responsibilities, plus a representative report structure for completed work, observations, residual risk and next actions. Any example is prepared from verified operating practice rather than presented as a completed client report.
Preserve familiar tools when they remain suitable
Maintenance does not require replacing a working theme, editor or page builder. The goal is to stabilize and improve the tools the team already understands, manage compatibility deliberately and recommend migration only when evidence justifies a separate decision.
Maintenance, Recovery, Audit and Delivery solve different problems
| Route | Use it when | Primary outcome |
|---|---|---|
| Maintenance & Support | A known baseline needs controlled recurring care. | Update cycles, checks, reporting, defined support and escalation. |
| Update Recovery | A specific workflow is currently broken or unreliable. | Restore agreed critical workflows and establish a safer baseline. |
| Technical Audit | The cause, risk or remediation boundary is unclear. | Findings, likely root causes and a prioritized remediation backlog. |
| Modernization Delivery | A finite implementation outcome and acceptance boundary are clear. | Phased production change, validation, documentation and handover. |
Commercial and responsibility boundaries
The agreement should state what is checked, what is changed, when work is performed, how exceptions are escalated and which responsibilities remain with the client or third parties.
Scoped around the real maintenance surface
The published maintenance levels are selected or adjusted according to the number of sites, dependencies, workflows, environments, hosting responsibility and support boundary.
Not unlimited development
Redesign, new features, migration, major refactoring and other project work require separate evidence, scope and acceptance.
Not an automatic guarantee
Round-the-clock incident response, guaranteed uptime or security, inherited defects, malware response and third-party fees are not included unless explicitly agreed.
Discuss WordPress Maintenance & Support
Discuss Maintenance & Support
Describe the current ownership model, critical workflows and recurring risk that support must control.
Direct ongoing WordPress evidence
SunAuto is a custom continuous-improvement engagement with broader responsibilities than the two standard monthly plans; its scope and pricing are agreed separately.
WordPress project
SunAuto continuous improvement
Following consolidation, SunAuto continued as an ongoing engineering and continuous-improvement engagement covering content lifecycle, integrations, performance, imports, caching and governed releases.
Available service
Page-builder maintenance capability
PathToProject publishes controlled page-builder updates, compatibility work and ongoing improvement as a supported WordPress capability.
Frequently asked questions
Can WordPress Maintenance & Support start on any website immediately?
No. The site first needs an accepted, sufficiently stable baseline. When existing failures, unknown technical causes or a large change backlog make routine updates unsafe, start with Technical Audit, Update Recovery or a bounded Modernization Delivery phase.
What can a recurring maintenance cycle include?
The agreed cycle can include update and compatibility review, backup verification, staged changes where appropriate, critical-workflow checks, public monitoring, reporting and separately scoped small support or improvement work. The exact modules and cadence are defined during onboarding.
Are emergency response, unlimited development or uptime guarantees included?
No by default. The offer does not imply round-the-clock incident response, unlimited change work, guaranteed uptime, guaranteed security or automatic responsibility for unknown inherited defects. Any response commitment or exceptional coverage must be explicitly scoped.
Can we keep our current theme or page builder?
Yes, when it remains fit for purpose. Maintenance follows the preservation-first principle: stabilize and improve the tools the team already understands, then escalate replacement or migration only when evidence justifies a separate decision.
What is the difference between Ongoing Maintenance and Continuous Improvement?
Ongoing Maintenance protects an accepted baseline through controlled updates, verification and reporting. Continuous Improvement uses a separately scoped and approved backlog to make small, purposeful changes. Larger features, redesign or migration remain separate Delivery work.
Will the scope show exactly what is covered and what the report contains?
Yes. A proposal defines coverage for sites, environments, dependencies, workflows, cadence and responsibilities. A representative report structure can be reviewed during scoping.
Free public WordPress assessment
Not sure whether ongoing maintenance is the right first route?
Start with the free WordPress Scan. It reviews publicly observable WordPress, response, delivery, maintenance and search signals, then gives you a bounded modernization assessment and a clearer next step. No admin access is required.
The Scan does not confirm private technical root causes. If the report surfaces a signal that matters and you are unsure what to do next, ask us to help interpret the evidence.