Article4 Minute Read

Website Maintenance: What Actually Happens After Launch

Security updates, backups, monitoring, performance and content: what website maintenance involves, how often each task should happen, and how to budget for it.

Author

Michael Getu

Last Update

Website Maintenance: What Actually Happens After Launch

Launch day feels like the finish line. It is closer to the starting line. A website is software running on servers, connected to other software, all of which changes constantly. Left alone, a site slowly breaks: a plugin update conflicts with the theme, a form integration stops sending enquiries, a security patch is missed, page speed drifts, and the content goes stale.

Maintenance is what keeps the site you paid for working as well in year three as it did on launch day. Here is what it involves and how to plan for it.

Security updates

Every website depends on software that receives security fixes: the CMS, plugins, themes, frameworks, libraries and the server itself. Attackers scan the web automatically for sites running versions with known vulnerabilities, so delays matter.

  • CMS-based sites such as WordPress need core, plugin and theme updates applied regularly, ideally tested on a staging copy first
  • Custom-built sites need their dependencies updated and scanned for known vulnerabilities
  • Hosting platforms need their own updates, which managed hosting usually handles for you

Unused plugins, old admin accounts and forgotten test pages should be removed. Every one is a possible way in.

Backups

Backups are the insurance policy for everything else.

  • Back up both the files and the database, automatically, at least daily for sites that change often
  • Store backups somewhere separate from the website's own server
  • Keep several versions, so you can restore from before a problem started rather than after
  • Test a restore regularly. A backup that has never been restored is a hope, not a backup.

Monitoring

You should find out about problems before your customers do.

  • Uptime monitoring alerts you when the site goes down
  • Error monitoring catches problems in forms, checkouts and scripts
  • SSL certificate expiry should be tracked, or renewed automatically
  • Search Console shows crawl errors, indexing problems and security issues reported by Google

Performance

Sites tend to get slower over time as images, scripts and tracking tags accumulate. Check Core Web Vitals on key pages every quarter and look for the usual causes: oversized images, new third-party scripts, plugins loading assets on every page. The thresholds and fixes are covered in our technical SEO checklist.

Functional checks

Integrations break silently. An email provider changes its settings, a CRM connection expires, a payment provider updates its API. Once a month, test the journeys that make you money:

  • Submit every form and confirm the enquiry arrives where it should
  • Run a test purchase or booking
  • Check that newsletter sign-ups reach your email platform
  • Click through the main navigation on a phone

Content and SEO

A website that never changes loses relevance with search engines and visitors. Plan for:

  • Updating service pages, prices, team information and case studies as the business changes
  • Publishing regularly if search is part of your strategy
  • Fixing broken links, internal and external
  • Reviewing which pages bring traffic and improving the ones that almost rank

A maintenance calendar

How often Task
Continuously Uptime and error monitoring, automated backups
Weekly Security updates for CMS sites, check for alerts
Monthly Test forms and checkout, review Search Console, update dependencies
Quarterly Performance review, broken link check, restore test, access review
Yearly Content audit, design refresh where needed, review hosting and tools

Budgeting for maintenance

Maintenance costs depend on the type of site. A simple static site on managed hosting needs very little. A WordPress site with many plugins, or an e-commerce store, needs regular attention. A custom web application needs ongoing development capacity.

Most businesses handle it in one of three ways:

  • A monthly retainer with the team that built the site, covering a set number of hours for updates, fixes and small changes
  • An in-house person who owns the site, with developer support for larger work
  • Ad hoc fixes when something breaks, which is the cheapest option until the day it becomes the most expensive

Include maintenance in the original budget conversation. Our guide to website development costs explains how ongoing costs compare to the build, and the website launch checklist sets up most of the monitoring described here on day one.

Ownership makes maintenance easier

Whoever maintains the site needs access to everything: hosting, domain, repository, CMS and third-party services. If those accounts are in your name, you can change who maintains the site at any time, without negotiating for access to your own product.

Our tech outsourcing team stays available after delivery to keep the products we build running at their best, whether through a maintenance arrangement or on-demand support as your needs evolve.