Maintenance
What a Website Maintenance Plan Should Cover After Launch
What ongoing website and app maintenance includes: updates, backups, monitoring, security patches, small changes and clear limits between care and new work.
Launch day is the start of a website's life, not the end of the project. Software, browsers and threats keep changing, and a site that is left alone slowly becomes slower, less secure and harder to update.
Updates and security patches
The server software, the programming language version, libraries and any plugins all receive updates, many of them security fixes. A maintenance plan should say how often updates are checked, how they are tested before going live, and how urgent security fixes are handled.
Backups you can actually restore
A backup is only useful if it can be restored. Ask how often the files and database are backed up, where the copies are kept, how long they are kept, and when a restore was last tested. Keeping at least one copy away from the main server protects against a single point of failure.
Monitoring
Uptime monitoring tells you when the site goes down. Error logs and performance checks show problems that visitors notice before you do, such as slow pages or a broken form. Someone should be responsible for reading these and acting on them.
Small changes
Most businesses need small edits: new prices, a changed phone number, a new team member or a seasonal banner. A good plan states how many hours or changes are included each month and how quickly they are done.
Where care ends and new work begins
A new feature, a redesign or a new integration is new work, not maintenance. Writing this line down in advance avoids disputes and lets both sides plan. It also keeps the monthly fee predictable.
Domains, hosting and renewals
Domain names, SSL certificates and hosting plans renew on fixed dates. A missed renewal can take a site offline. Keep these accounts in the business's name and make sure renewal reminders reach someone who will act on them.
A simple checklist
- Update and patch schedule, with testing
- Backup frequency, retention and restore tests
- Uptime and error monitoring
- Included small changes and response time
- A clear boundary for new work
- Renewal dates for domain, certificate and hosting
With these in place, the site keeps working the way it did on launch day, and improvements can be planned instead of rushed.
