Servizio · Website maintenance
Website maintenance
A site left in the hands of the agency-hosting-freelance-plugin chain becomes a blind spot: it breaks, nobody sees, then the blame hunt starts. Maintenance removes that chaos from the table.
Daily backups, uptime monitoring, controlled updates, security patches, base WAF and urgent fixes within 24 working hours. If a form stays broken for 6 days, that's not a technical detail: those are lost inquiries.
It's not technical theater, it's operational oversight. You know who intervenes, what's been done, and where the restore points are. The site stays governed even after launch, without waiting for clients to flag the disaster. Period.
01 — Awareness
The site doesn't maintain itself
After launch come updates, expirations, bugs, vulnerabilities and technical responsibilities often left in the void.
- 01
Invisible offline
The site goes down and nobody knows until a client calls. By then it's no longer a technical problem: it's reputation, lost sales, and a panicked recovery race.
- 02
Vulnerable plugins
Outdated WordPress plugins, old themes and frozen dependencies open known holes. Automated attacks don't wait for the meeting with the agency or the ticket with the provider.
- 03
Nobody responsible
When a backup needs restoring, the relay starts: hosting, agency, developer, account manager. Meanwhile the site stays broken and nobody takes the problem in hand.
02 — What you get
6 features- 01
Backup and restore
Automatic daily backups of site and database, with on-demand restore when you need to roll back. No hunting for scattered files, old zips, or half-broken copies saved somewhere.
- 02
Continuous uptime monitoring
24/7 uptime monitoring with alerts when the site doesn't respond. The problem gets seen before it becomes an angry client phone call or a day lost figuring out what happened.
- 03
Updates without chaos
CMS, plugin and dependency updates handled with judgment, not clicked at random in production. First we look at what changes, then we intervene. Random plugins left behind become technical debt, not destiny.
- 04
Tracked urgent fixes
For blocking failures, intervention within 24 working hours with clear priority. Broken forms, blank pages, server errors, frozen checkout: diagnosis, fix, documentation. End of story.
- 05
Patches and base WAF
Security patches applied when known vulnerabilities emerge, with base WAF to filter dirty traffic and trivial attempts. It doesn't make the site invincible, but it cuts many doors left open through neglect.
- 06
Readable monthly report
Every month you receive a comprehensible report: uptime, backups, updates, anomalies, interventions, and points to keep an eye on. No jargon to cover the void. Just real technical state and next priorities.
03 — How I work
5 phases- 01
Discovery call
30 free minutes to understand the real need. I listen, ask questions, take notes. No cold quotes: I need to know what you're actually building first.
- 02
Quote
Flat fee with clear scope, timeline and costs. No surprises: if something falls out of scope I tell you upfront, not when the invoice lands.
- 03
Design / Strategy
Wireframes, moodboard or audit with action plan — depends on the service. You see the direction before any code or content gets touched.
- 04
Build
Development, technical work or operational execution. Agreed check-ins along the way, none of that "let's sync end of month".
- 05
Launch & follow-up
Go-live + 30 days of assistance included. Documentation, training if needed, and an open door for the small things later.
04 — AFTER LAUNCH
Maintenance is where the theater ends
The site launch is just day zero. After come CMS updates, plugins that change behavior, expiring SSL certificates, shared hosting that slows down, public vulnerabilities, forms that stop sending emails and backups nobody ever tried to restore. The chain of providers is the problem: whoever made the theme doesn't manage the server, whoever manages the server doesn't touch WordPress, whoever sold the project replies with three people in CC. Meanwhile the site is yours, the damage is yours, the rush is yours. Monthly or annual maintenance puts continuous technical oversight in place: monitoring, updates, backups, patches, alerts, urgent fixes and a readable report. It doesn't promise magic. It removes improvisation. Period.
05 - What you get
Deliverables
| No. | Deliverable | Format | Timing |
|---|---|---|---|
| 01 | Daily backup setup | Backup job | week 1 |
| 02 | Backup restore test | Checklist | week 1 |
| 03 | Uptime monitoring | Alert dashboard | week 1 |
| 04 | Planned updates | Maintenance log | monthly |
| 05 | Base security hardening | Config report | week 1-2 |
| 06 | Access and error logs | Log review | monthly |
| 07 | Monthly technical report | PDF report | monthly |
| 08 | Emergency intervention | Ticket + log | on-demand |
| 09 | Tested rollback | Restore note | post-update |
| 10 | Critical renewal monitoring | Schedule | ongoing |
07 - Related services
08 - Free audit · 15 minutes
When was the last backup tested?
I check backups, updates, uptime, SSL and fragile points. 15 minutes on Meet, no maintenance package pushed by force.
No obligation - reply within 24h
09 — Frequently asked questions
6 answersThe questions I hear all the time.
What happens if the site goes offline?
Monitoring sends an alert when the site doesn't respond. From there we verify if the problem is hosting, DNS, CMS, plugins, database or SSL certificate. If it falls within the managed technical perimeter, we intervene within 24 working hours. The point is to avoid the first alarm coming from an annoyed client.
Do you also handle existing WordPress sites?
Yes, after an initial check. First we need access, plugin state, theme, hosting, backups, domain and SSL. If the site is full of abandoned components or badly modified code, it gets flagged immediately. Maintenance shouldn't cover a technical bomb with a coat of paint.
Can updates break the site?
Yes, they can. That's why they shouldn't be done in bursts by clicking "update all". First we check versions, compatibility, critical plugins and backup state. If something doesn't add up, we proceed cautiously or flag the risk. Updating without judgment is roulette, not maintenance.
What does the monthly report include?
The report includes uptime, backups performed, updates applied, anomalies detected, interventions made, security patches and notes on renewals. It's written to be understood by who runs the business, not just by who reads server logs. It has to clarify site state, not fill pages.
Can you handle domain and SSL?
Yes, if access is available and the registrar allows it. We monitor expirations, renewals and SSL certificates, so they don't become sudden emergencies. Expired domain and broken SSL are trivial problems, but when nobody monitors them they block everything. You decide whether to leave them to chance.
What if the site was made by another agency?
It can be managed, but first the real state of the project needs to be read. Some agencies deliver tidy sites, others leave duplicate plugins, saturated shared hosting and incomplete access. The audit exists exactly to understand what can be overseen immediately and what needs fixing first.
10 - Start here?
Ready to start?
A 30-minute call to figure out what's actually needed. No PowerPoint.