WordPress maintenance in Barcelona, with technical ownership.

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 ongoing development. The work is 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 is a healthy site, not a green "all updated" badge.

Yes, with depth proportional to risk. A WooCommerce payment or checkout update is 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 is where changes get tested away from 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, custom code, integrations and how production is actually set up, before changing anything.

Yes. Undocumented custom code, mystery plugins and changes made directly in production are the normal starting point. The first job is 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 cart, checkout, payments, transactional emails and key integrations before they go live.

Yes. Bug fixes, template and CSS/JS corrections, redirects, tracking fixes and small custom functionality 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 — template changes, integrations, admin improvements, structured data — is 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 from 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 is much faster than starting from zero. The fix is applied, verified in the failing area, and what changed is 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 is remote-friendly by nature — staging, Git and clear change summaries work the same wherever your team is, in a compatible European timezone (CET).

It depends on what I'm taking responsibility for: WordPress vs WooCommerce, the amount and quality of custom code and plugins, how often things change, how much testing each change needs, ongoing development and how critical production is. I scope it after seeing the site.