A site stuck on old CMS and language versions is a risk that grows on its own: plugins that stop getting updates, known holes never closed, and sooner or later something breaks at the worst moment.
For L'Altro Service I moved WordPress and PHP forward by years, checked that every plugin survived the jump, and left the URL structure untouched — so twenty years of rankings didn't disappear in one afternoon.
Whether it's a retainer or work on call, we agree that up front, not after: CMS, plugin and dependency updates, backups, fixes and ongoing SEO work. You write to me, not to a ticket disappearing into a CRM.
what it includes
- CMS, plugin, theme and dependency updates
- Scheduled backups, verified rather than just switched on
- Fixes and small changes after launch
- Ongoing SEO monitoring and tuning
related case studies
faq
What happens after launch?
A site isn't finished the day it goes live. I handle CMS, plugin and dependency updates, backups, fixes and ongoing SEO work. Whether that's a retainer or work on call is something we agree up front, not afterwards.