WordPress Care & Security

Care for WordPress proactively. Reduce risk. Prepare for recovery.

WordPress Care & Security provides ongoing WordPress maintenance for businesses: controlled core, theme and plugin updates, scheduled backups, and documented security and functional checks. We agree scope, responsibilities and service hours to suit your system.

Review your website and care needs Explore all services

Your operations advantage

Understand the system. Organise care. Prepare decisions.

Ongoing care combines controlled changes, technical checks and prepared recovery procedures. Your team receives documented findings and proposed next actions.

Understand the current position

Your team receives a system inventory, documented findings and clear ownership of the managed areas. Open decisions remain visible.

Organise recurring care

Updates, backup runs and agreed functional checks are organised as recurring work. The monthly report shows completed activities, results and blockers.

Prepare for incidents

Documented recovery exercises, named contacts and escalation routes help your team understand the next steps during an incident. Scope and boundaries are agreed in advance.

What you receive

What do our WordPress maintenance services include?

Maintenance, security, recovery and transparency are connected in one ongoing service.

controlled WordPress, theme and plugin updates
scheduled backup runs with outcome checks and documented recovery exercises
agreed security checks with AegisPress
agreed functional, performance and availability checks
initial assessment, notification and escalation of issues during agreed service hours
clear maintenance evidence and prioritized improvements

Defined operations

Care starts with a documented review of your system.

Before takeover, we review the agreed components, access, licences, hosting and update readiness. Identified legacy issues, gaps in the review and necessary stabilisation are documented and scoped separately.

Starting scope

technical onboarding for one production WordPress instance and one staging environment
controlled core, theme and plugin updates with agreed functional checks
scheduled daily backup runs with outcome checks
agreed uptime and security checks with AegisPress plus a documented quarterly recovery exercise
monthly operations report and a defined escalation route within agreed service hours

What changes the investment

WooCommerce, multisite, multilingual and custom-plugin setups
availability criticality, traffic and tighter response windows
additional change, development or editorial capacity

Planned separately

hosting, premium licences and third-party support
content changes and development outside the plan
stabilisation, in-depth incident response, forensics and rebuilding unless expressly included

Business clients only. All prices are net of applicable taxes. Timeline starts once required inputs and approvals are available. Only the individual proposal or agreement defines binding scope, fees, service levels and contracting entity.

Evidence built into delivery

Review the work and its recorded results.

Changes, backup runs, recovery exercises and open findings are documented so your team can review the work and decide what comes next.

Technical baseline

Components, versions, known risks, access and ownership are recorded before takeover.

Restore and change evidence

Backups, recovery tests and material changes remain documented in a reviewable record.

Clear operating report

Status, anomalies, completed work and next priorities are brought together clearly each month.

Explore all services Explore trust & compliance

Your care scope

Know what is managed and what needs a decision.

The takeover report brings together the system inventory, reviewed areas, known findings and gaps in the review. Your team receives a responsibility map and an agreed care plan; required stabilisation is scoped separately.

Agree the functional checks

Before engagement, we name the journeys to check after managed changes, their test steps and acceptance criteria. Examples include form validation, language switching or a test checkout. Only agreed journeys and test conditions are covered; not every integration or live transaction.

Define backup and review coverage

The care plan specifies backup contents, retention, a copy separate from production, access and handling of failed runs. Recovery exercises record the recovery point, test environment, scope, outcome and open findings.

Keep ownership clear

Working days, time zone, holidays, reporting channel, human review cadence, priorities, contacts and cover are defined before engagement. The handover arrangements cover documentation, access, licences and backups when the agreement ends.

What happens when something goes wrong?

During agreed service hours, initial assessment using the agreed checks, client notification and escalation belong to the starting scope. There is no fixed response, restoration or resolution time. Additional work is described and approved through the agreed route; existing service commitments and statutory duties remain unaffected.

A form fails after a managed update

Where the form is an agreed test journey, we check it after the update and record any discrepancy. We assess the impact and the agreed rollback or correction route. Work already owed under the engagement remains part of that obligation; replacing an unsupported integration needs separate scoping.

A security check flags an issue

We assess the signal using the agreed checks, notify the designated contact and document the recommended next step. In-depth investigation, forensics or rebuilding is scoped separately unless included. A signal alone neither proves nor rules out a compromise.

Care you can review

Your monthly report: what is done, what needs a decision?

See what was carried out within the agreed scope, what the results show and where your team needs to decide. Work not completed and checks still in progress are marked as open.

Work and results

Completed changes and agreed checks, with their outcomes and any outstanding verification.

Backups and recovery

The status of backup runs and recovery exercises due within the reporting period, including failures and areas not tested.

Priorities and decisions

Findings assessed by impact, recommended next steps, responsibilities and any approval or additional scope needed.

From takeover to routine

Four steps to dependable WordPress operations.

The takeover report records reviewed areas, known findings and gaps in the review. Required stabilisation is agreed before routine care begins.

Assess the takeover

Hosting, WordPress, components, access, backups and known risks are inventoried.

Stabilize the baseline

Identified gaps and blockers are prioritised. Additional work, approvals and prerequisites for starting care are agreed.

Operate with control

Updates, backups, monitoring and checks run on a defined rhythm.

Improve deliberately

Operational, performance and security insights become clear next actions.

Proactive operations

Automated monitoring. Controlled change.

Automated checks run at agreed intervals and provide signals. Human review and handling take place within agreed service hours; automated monitoring does not mean 24/7 standby. Unknown vulnerabilities and software or infrastructure failures remain possible.

Best suited to

Companies seeking organised WordPress care within agreed service hours. Requirements for continuously staffed standby or fixed recovery targets need a separate suitability and capacity review before a proposal is made.

FAQ

Questions about WordPress maintenance and care.

Scope, costs, service hours, client cooperation and additional work are clarified before takeover.

How much do WordPress maintenance services cost?

Onboarding starts at EUR 1,490 and ongoing care at EUR 790 per month, excluding applicable taxes and for business clients only. Requirements for WooCommerce maintenance, multisite, custom integrations and test journeys affect the scope. The individual proposal or agreement defines binding services and fees.

Can you take over an existing WordPress website?

Yes, following a takeover review of the agreed areas. We document identified findings and gaps in the review. Valid licences, required access, suitable infrastructure and necessary stabilisation are agreed before care begins.

What happens during an urgent incident?

During agreed service hours, the starting scope covers initial assessment using the agreed checks, client notification and escalation. In-depth investigation, forensics and rebuilding require separate scoping unless included. Fixed response or resolution times are not promised. Existing service commitments and statutory duties remain unaffected.

Are paid plugin and theme licenses included?

Existing or newly required third-party licenses are documented transparently. The specific care plan states exactly which licenses are included.

Is complete security or availability guaranteed?

Ongoing care is intended to reduce risk. Complete security, uninterrupted availability, attack detection and successful recovery are not guaranteed. Our duties of care and statutory obligations remain in place. Scope and dependencies are agreed transparently.

What cooperation is required?

The client provides agreed access, valid licences and necessary approvals, and coordinates changes to managed systems. Hosting and third-party responsibilities are specified; our own selection, configuration and escalation duties remain in place.

Operate WordPress dependably

Give your website clear technical ownership.

Tell us about your website and care needs. Please do not send passwords or confidential documents; access is arranged later through a suitable channel.

Review your website and care needs