One request, one visible boundary
A small content change stays separate from a redesign, plugin migration, performance project, or production incident.
WordPress maintenance services
Maintain and change the WordPress site you already own—without editing production blind.
WPbyAI handles scoped WordPress website maintenance through a controlled copy: classify the stack, freeze the request, preview the exact version, approve the result, and receive a stated verification record.
Private Pilot: this route covers reviewed, scoped changes and C-verified handoff. It is not 24/7 incident response, unlimited human support, production deployment, or an active Managed Care plan.
Review before production
Changes are made against a controlled workspace or staging route, with a stable preview and a known parent version.
Know what was actually checked
The handoff identifies versions, tested flows, warnings, excluded areas, and the production step still required.
What happens next
A visible path, with a stop at every meaningful decision.
- 01
Classify the site
Confirm ownership, current host, WordPress/PHP/editor stack, available source or backup, and production risk.
- 02
Freeze the change
Turn the request into pages, acceptance criteria, plugin constraints, data rules, and a clear major-change threshold.
- 03
Preview and approve
Apply the change to an isolated copy, show the exact version, and return to the parent version if the result is rejected.
- 04
Verify and hand off
Run the agreed functional and search checks, then deliver the C-verified source package for customer-controlled hosting.
Included in this route
- Initial site and material classification
- A scoped change brief and major-change boundary
- Versioned preview rather than blind production edits
- Plugin/stack preflight where relevant
- A stated handoff, warranty, and deferred production-care boundary
Not assumed or promised
- 24/7 incident response or unlimited human support
- Automatic repair of every plugin, security, or hosting failure
- Premium plugin licenses that the customer does not own
- Production credentials submitted through the public pilot form
- Production deployment or Managed Care during the current pilot
Frequently asked questions
Scope first. Promises second.
What does a WordPress maintenance service include?
It should name the accepted changes, stack checks, preview route, verification evidence, exclusions, and production handoff. Updates, redesigns, incidents, hosting, and unlimited support should not be silently bundled together.
Can WPbyAI review an existing site from its URL?
Yes. An authorized public URL can start classification and fit review. Editable source, a backup, licenses, or controlled access may still be required before a safe change can be accepted.
Will WPbyAI edit my live production site?
Not in the current private pilot. The public route stops at a C-verified source handoff; production deployment and Managed Care require separate permissions, rollback evidence, and later product gates.
How is maintenance different from support?
Maintenance is the clearer route when the requested change and acceptance criteria are already known. Support begins with diagnosis when the symptom, root cause, material quality, or safe route is still uncertain.
Choose the right route
Different WordPress needs should not be forced into one vague plan.
WordPress Care Plans
Compare maintenance plans, recurring change capacity, and the future Managed Care boundary.
View this route →WordPress Support Services
Start with a broken flow, an unsupported site, or a request that first needs diagnosis.
View this route →Existing Site Intake
Bring a source package, backup, or authorized URL when the current site must be classified first.
View this route →Limited private pilot
Tell us what needs to change—and what material you control.
A URL is enough to start a fit review. Source, backups, credentials, and private data are requested only through a later controlled intake when necessary.