Web Development

What a Website Maintenance Plan Should Include

The jobs a website maintenance plan has to cover, how often each should happen, what you should receive as proof, and what a plan does not include, so you can compare offers or run it yourself.

What a Website Maintenance Plan Should Include

A website maintenance plan is a list of recurring jobs, each with an owner, a frequency and some proof that it happened. The plans that disappoint name the jobs and stop there: "updates and backups", with nothing about when, tested how, or shown where.

What follows is the full list, with the questions to ask about each line. Use it to compare offers from agencies, or as the checklist for running maintenance yourself.

Updates that someone tests

Three layers need updating, and a plan should say who looks after each:

  • The application: CMS core, plugins and themes, or for custom software the framework and its Composer and npm packages.
  • The runtime: the PHP version, and the database server version.
  • The server: operating system packages and the web server. On managed hosting the host does this. On a VPS or cloud instance somebody else must.

The runtime is the layer plans forget. Each PHP branch gets two years of active support and then two more years of security fixes only, as the PHP supported versions page shows. Moving to a newer branch before the old one runs out is a small project with testing, not a switch in the hosting panel, and the plan should say whether it is included.

For the application layer, ask how updates are applied. A sound answer has three parts: security releases go on within days, feature releases are tried on a staging copy first, and there is a stated way back if something breaks. Then ask what is tested afterwards. "We check that the site loads" is not the same as placing a test order or submitting the contact form. Our WordPress update checklist shows what a careful update involves on one platform.

Backups that have been restored

Every plan includes backups. Fewer can show you one that was restored. The details that matter:

  • What: the database and the files, including uploads.
  • Where: a copy outside the web server and outside the hosting account, so that a compromised or suspended account does not take the backups with it.
  • How often: matched to how much data you can afford to lose. Daily is plenty for a brochure site. A store or a learning platform writes orders and progress all day and needs database backups far more often.
  • How long: several weeks of history, because malware and quiet data damage are often noticed long after they start.
  • Restore tests: on a schedule, to a staging copy, with the time it took written down. That time is how long your worst outage lasts.

Ask for the date of the last restore test. It is the single most revealing question about any maintenance offer.

Monitoring that reaches a person

Monitoring exists so that you hear about a problem before a customer tells you. A useful setup watches more than the home page:

  • an uptime check from outside the server every few minutes, on an inner page that needs the database;
  • a check of the path that earns money, such as logging in or adding a product to the cart;
  • expiry dates for the SSL certificate and the domain;
  • disk space, memory and the error log;
  • scheduled tasks and queues, which fail silently and take emails, renewals and reports with them;
  • a test form submission that must arrive in an inbox, since broken email delivery is the fault that goes unnoticed longest;
  • Google Search Console, for indexing errors and security warnings.

An alert is only worth something if a person receives it and is expected to act. Who that is, during which hours, and how quickly, is the subject of the support terms. We explain how to read those in support SLAs explained.

Security work, not a security plugin

Updates are most of security, but a plan should name the rest:

  • a regular review of user accounts, removing people who have left and reducing permissions nobody needs;
  • two-factor login for administrators;
  • file-change or malware scanning, with someone reading the results;
  • firewall and login-protection rules that are reviewed, not installed once and forgotten;
  • a check for plugins and packages whose authors have abandoned them. For custom PHP applications, composer audit lists installed packages with known vulnerabilities.

Then ask the awkward question: if the site is compromised anyway, who cleans it up, how soon do they start, and is that work inside the plan or billed separately? No honest provider promises a site will never be breached. A clear incident procedure is worth more than a guarantee.

Change requests and the monthly report

Most plans include a pool of development time for small changes. Check how many hours there are, whether unused time carries over, how requests are submitted and how soon they are picked up. Ask where the line falls between a small change (new text, a swapped image, an extra form field) and a project (a new feature, a redesign, an integration), which should be quoted separately. A plan with no change time at all turns every typo into an estimate.

The report is your proof that the rest happened. It should fit on a page or two and list the updates applied, the backup status and last restore test, any downtime with its cause, security events, hours used and on what, and recommendations for the next quarter. Without a report you cannot tell a maintained site from one that was simply left alone and happened not to break.

The whole plan on one calendar

How oftenJobs
All the timeUptime, error and expiry monitoring. Automated backups.
WeeklyReview and apply security updates. Confirm backup jobs completed. Read scan results and the error log.
MonthlyFeature updates after a staging test. Test forms, checkout and login by hand. Check page speed. Send the report.
QuarterlyRestore a backup to staging. Review user accounts. Review the plugin or package list.
YearlyReview the PHP and database versions against their support dates. Renew the domain, certificates and licenses. Review hosting size and cost. Walk through the recovery procedure.

The right frequency shifts with the site. A store in its busy season deserves weekly checks of things a brochure site can leave for a month.

What a website maintenance plan is not

Disagreements about maintenance usually start with something the client assumed was included. These are normally outside a plan unless it says otherwise:

  • Hosting. It is sometimes bundled, and then you should know which company is responsible for the server itself.
  • New features and redesigns. Maintenance keeps what exists working. It does not grow the product.
  • SEO and content. Writing pages and building rankings are separate services.
  • License fees. Premium plugins and themes renew every year. Find out who holds the licenses and who pays.
  • Unlimited work. "Unlimited edits" always has a definition somewhere. Read it.
  • Recovery from a third party's failure. If the payment provider or the email service has an outage, a maintainer can tell you so, but cannot repair it.

Running it in-house or handing it over

A simple site with a small set of well-known plugins can be maintained by anyone careful who puts the calendar above in their diary and keeps to it. The work is not difficult. It is easy to postpone, and that is how sites end up two years behind.

Hand it over when the site takes payments or holds customer or learner records, when it runs custom code that updates can break, or when maintenance is nobody's job and so it does not get done. Our maintenance and support service covers everything listed above, and the platform-specific versions go deeper: WordPress maintenance, Laravel maintenance and Moodle maintenance. We build and maintain our own plugins and our own LMS product, so we know what it takes to keep shipped software supported.

Frequently asked questions

Do I need a maintenance plan if my hosting is "managed"?

Usually yes. Managed hosting typically covers the server, and on some platforms automatic core updates and backups. It does not test your site after an update, fix a plugin conflict, review user accounts or act when a form stops sending. Ask the host for the exact list and fill the gaps.

What is the difference between maintenance and support?

Maintenance is scheduled, preventive work: updates, backups, checks and reports. Support is reactive: someone responds when a thing breaks or a request comes in, within agreed times. Many plans sell both together, but they are priced and measured differently, so look for each in the offer.

Can maintenance be paused for a few months to save money?

It can, but the work does not disappear. Updates pile up, each skipped release makes the eventual jump larger and riskier, and security fixes go unapplied in the meantime. If budgets are tight, cut the change hours and keep updates, backups and monitoring running.

Does a small brochure site need all of this?

It needs the same categories at a smaller scale. Updates, an off-site backup, an uptime check and renewal reminders take little time each month on a simple site. What it can skip is frequent backups, transaction checks and most of the reporting.

Add WorldWin Coder to your preferred sources

Add worldwincoder.com as a preferred source on Google, or open this article in your AI assistant to use it as a source.

Swati Priyadrshni
· Founder & CEO at WorldWin Coder

I'm Swati Priyadarshani, Founder & CEO of LMS Advisor and Co-Founder of WorldWin Coder Pvt. Ltd. (est. 2019). Over the last 10+ years, I've helped enterprises build learning platforms that actually get used - not just deployed.

Keep reading

Have something to build, fix or move?

Tell us where you are. A developer reads every inquiry, and you get next steps and a free quote within one business day.