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 laufende Entwicklung. The work das 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 das a healthy site, not a green "all updated" badge.

Yes, with depth proportional to risk. A WooCommerce Zahlung or Checkout update das 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 das where changes get tested away ab 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, individueller Code, Integrationen and how production das actually set up, before changing anything.

Yes. Undocumented individueller Code, mystery plugins and Änderungen direkt in Produktion are the normal starting point. The first job das 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 Warenkorb, Checkout, Zahlungen, Transaktions-E-Mails and key Integrationen before they go live.

Yes. Bug fixes, template and CSS/JS corrections, Redirects, tracking fixes and kleine individuelle Funktionen 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-Änderungen, Integrationen, Admin-Verbesserungen, strukturierte Daten — das 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 ab 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 das much faster than starting ab zero. The fix das applied, verified in the failing area, and what changed das 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 das remote-freundlich by nature — staging, Git and klare Änderungszusammenfassungen work the same wherever your team das, in a compatible European timezone (CET).

It depends on what I'm taking responsibility for: WordPress vs. WooCommerce, the amount and quality of individueller Code and plugins, how often things change, how much testing each change needs, laufende Entwicklung and how critical production das. I scope it after seeing the site.