---
title: "WordPress maintenance and support, tested on staging"
description: "WordPress and WooCommerce maintenance: updates tested on staging, a database backup before touching production, and uptime, SSL and SEO monitoring."
url: https://lazarosantana.dev/en/services/wordpress-maintenance/
---

service · maintenance · updates and monitoring

# WordPress maintenance *and support*

I maintain WordPress sites and stores after launch. Updates are tested on staging before they reach production, and a dashboard watches uptime, performance, SSL and SEO. I have built or managed 27 sites across 5 countries.

[Request a quote](https://lazarosantana.dev/en/contact/#form) [See Boardly](https://lazarosantana.dev/en/projects/boardly/)

What I cover

Updates to WordPress, plugins and theme, and fixes

How

Local, staging and production, with a database backup before touching production

Monitoring

Uptime, performance, SSL and SEO in one dashboard

Mode

Remote from Havana

// what it solves

## What it solves

Concrete problems that already came up in a real project, not a list of promises.

01

### Updating without breaking

Changes go through staging before they reach the live store. Production is updated by hand and always with a database backup first.

02

### Knowing when the site is down

A scheduled check tells a site that is down from one that returns errors, and detects the WordPress version and plugins when the site exposes them.

03

### Nothing expires unnoticed

The dashboard checks the real validity of the SSL chain, the issuer and the days left. The alert fires before a certificate surprises anyone.

04

### A store that holds up in peak season

On a ticket store the cart AJAX was trimmed, Redis was added as an object cache and opcache was sized up. With XML-RPC closed and Turnstile against bots.

// proof

## Real proof

**27** sites built or managed, in 5 countries

**5** checks per site in Boardly: health, SSL, SEO, performance and accessibility

**3** environments on every change: local, staging and production

**4,500*+*** paid orders on acuamania.uy, the seasonal store with Redis and staging

Boardly is a project of my own with a public demo of fictitious data: there are no business results to report and the figures come from the repository. Changes between environments move with [ix-wp-envsync](https://lazarosantana.dev/en/projects/ix-wp-envsync/).

own project · public demo · open source

### A website monitor of my own

Boardly watches uptime, performance, SSL and SEO for several sites from one dashboard, with alerts and a monthly report.

*Boardly*

Boardly dashboard, the website monitor of my own

// how it works

## How it works

01 · review 02 · scope 03 · staging 04 · production 05 · monitoring

01

### First review

Before updating anything I check what is there: WordPress version, plugins and theme. If I did not build the site, the third-party code stays read-only and my changes go in as a patch.

- version
- plugins
- patches

02

### Scope

We agree what is included: updates, backups, monitoring and hours for changes. The method does not change, and the monitoring covers what surprises you most when it fails.

- updates
- backups
- hours for changes

03

### Staging first

Every change goes through local, staging and production. An update that fails shows up in staging, not in your store.

- local
- staging
- production

04

### Production

In production I update by hand and always take a database backup first. If something does fail, the [ix-wp-envsync](https://lazarosantana.dev/en/projects/ix-wp-envsync/) rollback restores the remote’s previous copy.

- previous copy
- rollback
- by hand

05

### Monitoring

A dashboard checks availability, performance, SSL and SEO and alerts you if the site goes down, a certificate expires or a score drops. How the alert reaches you is agreed with you.

- Boardly
- SSL
- alerts

I have a store someone else built and I don’t know which version it runs

I check WordPress, plugins and theme before touching anything

And the third-party plugins?

They stay read-only; my changes go in as a patch

example conversation

**Availability*✓ watched***

- site down or erroring
- WordPress and plugin versions

**SSL*✓ watched***

- certificate validity
- days until it expires

**SEO*✓ watched***

- title and description
- H1s and images without alt

**Performance*✓ watched***

- LCP, CLS and TTFB (PageSpeed Insights)
- 7- or 30-day charts

what I watch on every site

local *→* staging *→* production

ix-wp-envsync

staging first, backup before, production last

uptime · last 30 days

health *·* SSL *·* SEO

Boardly · demo with fictional data

// questions

## Frequently asked

### What does maintenance include, and what does it cost?

We agree it when we talk about scope: updates, backups, monitoring and hours for changes. Then you get a fixed price in writing before work starts. The method does not change: staging first, a database backup before, and production last.

### What if an update breaks something?

Because it is tested on staging first, the failure shows up there and not in the store. If it reaches production there is a previous copy: ix-wp-envsync saves one of the remote before every push and its rollback restores it.

### Do you maintain a site you did not build?

Yes. Before updating I check what is there: WordPress version, plugins and theme. Third-party or client plugins stay read-only and changes are kept as a patch.

### Will you tell me if the site goes down?

Boardly alerts in its dashboard and, if configured, on a Slack webhook when a site goes down, a certificate is about to expire or a score drops. How the alert reaches you is agreed when we talk about scope.

// let’s talk

## Got something like this in mind?

Tell me what you sell, to whom and what has to happen. I reply within 24 h.

[Request a quote](https://lazarosantana.dev/en/contact/#form)
