Services
Website Maintenance Services
A website that isn't touched for a year accumulates outdated dependencies, unnoticed bugs, and content that's gone stale. Maintenance is the unglamorous work that keeps a site secure and functional after launch — dependency updates, small fixes, content changes, and keeping an eye on uptime and performance.
This is typically structured as an ongoing retainer or an as-needed arrangement, depending on how much change the site sees.
Problems This Solves
- arrow_rightOutdated dependencies that accumulate security vulnerabilities over time
- arrow_rightSmall bugs and content changes piling up with no one responsible for handling them
- arrow_rightA site that's slowly gotten slower as more has been bolted onto it without anyone reviewing performance
- arrow_rightNo monitoring in place, so downtime or errors go unnoticed until a customer reports them
What's Included
- checkDependency and security updates on a regular cadence
- checkBug fixes and small feature changes
- checkContent and copy updates
- checkUptime and error monitoring
- checkPeriodic performance and Core Web Vitals review
- checkBackups and deployment management
How I Work
Maintenance work runs on whatever cadence fits the site — a monthly check-in for low-change sites, or a standing retainer for sites with frequent content or feature updates. Requests come in, get triaged by urgency, and shipped without disrupting whatever else is running on the site.
Technology Stack
- arrow_rightWhatever the existing site is built on
- arrow_rightDependency update tooling
- arrow_rightError and uptime monitoring
- arrow_rightGit-based deployment workflow
Suitable For
Any live site or app that needs ongoing attention after the initial build — especially ones without an in-house developer to handle routine updates and the occasional urgent fix.
Frequently Asked Questions
Do you only maintain sites you originally built?add
No — I take on maintenance for existing React and Next.js sites built by other developers, though the first engagement usually starts with an audit to understand the codebase before making changes.
How quickly are urgent issues handled?add
Urgent issues — the site down, a broken checkout, a security vulnerability — get priority over routine work. The exact response time depends on the maintenance arrangement in place.
What counts as a 'small' change versus a new project?add
Content updates, bug fixes, and minor feature tweaks fall under maintenance. Anything that needs its own scoping and design work — a new section, a new integration — is treated as its own project, discussed before starting.
Do you handle hosting and domain issues too?add
Yes, where relevant — deployment configuration, DNS, SSL renewal, and the general infrastructure the site runs on.