Your WordPress site needs an owner, not an update button.

Core and plugin updates reviewed for risk, testing on staging, functional and visual QA, backups and rollback, security hygiene, performance regression checks, analytics verification, and small desarrollo continuo. The work es verification and technical ownership, not just running updates.

Not blindly. I review changelogs, dependencies and risk, and update on a cadence that matches the site. A meaningful update ships after it's tested; a risky one may be deliberately held until it's safe. The goal es a healthy site, not a green "all updated" badge.

Yes, with depth proportional to risk. A WooCommerce pago or checkout update es tested on staging before production; a harmless admin utility isn't treated like a release. Testing covers the paths that actually matter — forms, checkout, tracking and performance.

For anything risky, yes. Staging es where changes get tested away desde customers before they reach production. Low-risk changes don't always need it; the level of ceremony matches the level of risk.

Yes — that's most of this work. I start by mapping what's there: plugins, código a medida, integraciones and how production es actually set up, before changing anything.

Yes. Undocumented código a medida, mystery plugins and cambios hechos directamente en producción are the normal starting point. The first job es understanding the site well enough to change it safely.

Yes. Stores raise the stakes because a broken checkout stops revenue, so updates are tested against carrito, checkout, pagos, emails transaccionales and key integraciones before they go live.

Yes. Bug fixes, template and CSS/JS corrections, redirecciones, tracking fixes and pequeña funcionalidad a medida are a normal part of maintenance — not a separate project every time.

Yes, and it usually does. Because I already know the codebase, small development — cambios de plantilla, integraciones, mejoras del admin, datos estructurados — es faster and lower-risk than briefing a stranger each time.

I handle security hygiene: users and permissions, credentials, vulnerable components and obvious attack surface. That's different desde specialist enterprise security operations, and I'm clear about that boundary.

Yes. Maintenance includes performance regression checks so a fast site doesn't slowly turn slow, and deeper Core Web Vitals work can be part of the engagement when it's needed.

There's a snapshot to roll back to, and because I already know the site, diagnosis es much faster than starting desde zero. The fix es applied, verified in the failing area, and what changed es logged.

Yes. I'm based in the Barcelona area and can work on-site locally, and I maintain WordPress sites remotely for companies across Spain and Europe.

Yes. Maintenance es trabajo remoto by nature — staging, Git and resúmenes claros de cambios work the same wherever your team es, in a compatible European timezone (CET).

It depends on what I'm taking responsibility for: WordPress vs WooCommerce, the amount and quality of código a medida and plugins, how often things change, how much testing each change needs, desarrollo continuo and how critical production es. I scope it after seeing the site.