Skip to content
NKNaveen Kapur Blog
Web & CMS

Website Maintenance Services: What a Monthly Plan Should Include

A website is not finished on launch day. Software goes out of support, certificates expire, forms break and backups fail quietly. Here is what a website maintenance plan should include, how often each task should happen and what to ask before you pay for one.

NK

Naveen Kapur

· Updated · 7 min read

A computer screen showing HTML code for a website
Photo: Mohammad Rahmani on Unsplash

Quick answer

Website maintenance services keep a live site safe, fast and working. A sound monthly plan covers off-server backups with a test restore, tested updates to the CMS, plugins and themes, security monitoring, uptime and form checks, SSL renewal, a Core Web Vitals check, Search Console errors and a short report. Quarterly, it should confirm the server's PHP version is still supported (PHP 8.2 security support ends on 31 December 2026) and remove unused plugins and old logins. Everything, including the domain and hosting, should stay in the owner's name.

Key takeaways

  • Maintenance is about four things: backups you can restore, supported software, security monitoring and checks that forms and pages still work.
  • A backup is only proven when it has been restored; test one every month on a copy of the site.
  • PHP 8.2 gets security fixes only until 31 December 2026 (php.net); WordPress recommends PHP 8.3 or greater.
  • Public TLS certificates are getting shorter: the CA/Browser Forum approved a cut from 398 days to 47 days in steps from March 2026 to March 2029, so renewal must be automatic.
  • In India, CERT-In's 2022 directions require body corporates to report listed cyber incidents, including website defacement, within 6 hours.
  • Domain, hosting, Search Console and analytics accounts should be in your name; the maintenance provider gets access, not ownership.

Many business websites are built well and then left alone. For a while nothing seems wrong. Then a contact form stops sending emails, a plugin update breaks the menu, the security certificate expires on a Sunday, or Google shows a warning that the site may be hacked. None of these are rare, and most are prevented by routine work that nobody was paid to do.

This guide explains what website maintenance services should include, how often each task should happen, and what to ask a provider. It applies to WordPress and to most other sites, with WordPress examples because so many business sites run on it.

What maintenance is, and what it is not

Maintenance keeps the site you have safe, current and working. It is not a redesign, new pages or new features; those are projects with their own scope. A good plan says clearly where maintenance ends, how many hours of small changes are included each month, and what anything beyond that costs.

Website maintenance checklist by frequency. Every week: backup runs with a copy kept off the server, core, plugin and theme updates tested first, uptime and form test, security alerts checked. Every month: restore one backup to a test copy, speed check against LCP 2.5 seconds, INP 200 milliseconds and CLS 0.1, Search Console errors, broken links and 404s. Every quarter: remove unused plugins, users and old admins, check PHP and server versions are still supported, content and price review, report sent to owner. Every year: domain and hosting renewals in your name, SSL renewal checked, logins reviewed and old access removed, plan and scope reviewed. A good plan names who does each task, keeps every account in your name and sends a short report each month
The routine work, by how often it should happen.

1. Backups you can actually restore

Every plan says "daily backups". Ask three follow-up questions. Where is the copy kept? A backup stored only on the same server disappears with the server. How long are copies kept? If a hack is found three weeks late, you need a copy from before it. When was a restore last tested? A backup that has never been restored is a hope, not a backup.

A sensible routine: an automatic daily backup of files and database, a copy stored with a different provider or account, at least 30 days of copies, and one test restore each month onto a staging copy of the site.

2. Updates, tested before they go live

A common way into a website is a known weakness in a plugin, theme or CMS version that was never updated. WordPress has supported automatic updates for plugins and themes since version 5.5, where administrators opt in plugin by plugin and theme by theme; by default WordPress runs auto-updates twice a day. Automatic updates are useful for small, trusted plugins. For plugins that run forms, payments or bookings, a provider should update a staging copy first, check the key pages and forms, then update the live site.

The server software matters too

Your site runs on a programming language and a database that also go out of support. WordPress's requirements page recommends PHP 8.3 or greater, MariaDB 10.11 or greater or MySQL 8.0 or greater, and HTTPS support. The PHP project's own support table (checked 27 Oct 2026) is below.

PHP versionActive support untilSecurity fixes until
8.231 Dec 202431 Dec 2026
8.331 Dec 202531 Dec 2027
8.431 Dec 202631 Dec 2028
8.531 Dec 202731 Dec 2029
Source: php.net supported versions. Versions older than 8.2 no longer get security fixes.

If your hosting still runs PHP 8.2 or older, plan the move to a newer version now, test it on staging first, and confirm every plugin supports it. Our guide to web hosting in India explains what to look for in a host.

3. Security monitoring

Security work in a maintenance plan is mostly routine: strong unique passwords and two-step login for every admin, removing old staff and agency logins, a firewall or security plugin with alerts that someone reads, and a weekly look at those alerts. Add your site to Google Search Console and watch its Security issues report, which tells you if Google has found hacked content or harmful downloads on the site. After a fix, you request a review there.

Indian businesses should also know about CERT-In's directions of 28 April 2022 under section 70B of the IT Act. They require service providers, intermediaries, data centres, body corporates and government organisations to report listed cyber incidents to CERT-In within 6 hours of noticing them, and the list includes defacement of a website or intrusion with unauthorised changes such as malicious code or links. The same directions ask these organisations to keep logs of their ICT systems for a rolling 180 days within India. Ask your provider who would notice an incident, who would tell you, and how quickly. Check with your legal adviser how the directions apply to your business.

4. SSL certificates that renew themselves

The padlock in the browser depends on a TLS (SSL) certificate that must be renewed before it expires. In April 2025 the CA/Browser Forum, the body of certificate issuers and browser makers, approved a ballot that cuts the maximum life of public TLS certificates from 398 days to 47 days, in steps starting in March 2026 and ending in March 2029. Manual yearly renewal will not keep up. A maintenance plan should use automatic renewal and include a monitor that warns you before any certificate expires.

5. Speed, forms and emails

Sites slow down over time as plugins, scripts and large images pile up. A monthly check against Google's Core Web Vitals is a simple test. web.dev lists the "good" thresholds as Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads. If the site fails these, that is a speed project; see our guide to website speed optimisation services.

Forms are where a business site earns its money. Test every form each week: submit it, check the email arrives, and check the lead reaches your CRM. If form emails land in spam, the cause is often missing email authentication; our article on SPF, DKIM and DMARC explains the fix.

A bright server room with rows of black and white cabinets under blue cables
Your website lives on someone's server: know whose, and where the backups go. Photo: Taylor Vick on Unsplash

6. Ownership and access

This is the least technical part and often the most important. The domain, the hosting account, Google Search Console, Google Analytics and any paid plugin licences should be registered in your business's name, with the provider added as a user. If a relationship ends, you remove their access; you do not ask for your website back. Keep a simple document listing each account, who owns it, who has access and when it renews.

What a monthly plan should include

AreaWhat the provider doesHow often
BackupsDaily automatic backup, copy kept off the server, test restoreDaily; restore monthly
UpdatesCMS, plugins and themes, tested on staging firstWeekly or as released
SecurityRead alerts, remove unused logins and plugins, check Search Console security issuesWeekly; access review quarterly
Uptime and formsUptime monitor with alerts; submit every form and confirm the lead arrivesContinuous; forms weekly
SSL and domainAutomatic certificate renewal with expiry alerts; renewal dates trackedContinuous; review yearly
Speed and SEO healthCore Web Vitals check, Search Console errors, broken linksMonthly
Small changesText, image and price updates within the agreed hoursAs requested
ReportWhat was updated, what broke, what was fixed, what needs a decisionMonthly
Use this as a checklist when you compare quotes.

What website maintenance costs

Prices vary widely, so compare scope, not only the monthly figure. The cost depends on the number of plugins and integrations (forms, payments, bookings, CRM), how many small-change hours are included, how fast the provider promises to respond, whether staging and off-server backups are included, and whether hosting is bundled. A cheap plan that only clicks "update all" each month can cost more later than a plan that tests updates and restores backups.

Questions to ask a provider

  1. 1Where are backups stored, how long are they kept, and when did you last test a restore?
  2. 2Do you test updates on a staging copy before the live site?
  3. 3Who watches security alerts and uptime, and how fast will you tell us about a problem?
  4. 4Which PHP version is our site on, and when will it be upgraded?
  5. 5How many hours of small changes are included, and what is the rate after that?
  6. 6Will the domain, hosting and Google accounts stay in our name?
  7. 7What does the monthly report contain?

Red flags

  • Backups kept only on the same server as the site.
  • "We update everything automatically" with no testing or rollback plan.
  • The domain or hosting registered in the provider's name.
  • No written scope for what is and is not included.
  • No report, or a report that lists only plugin names.

If you are planning a redesign rather than upkeep, read our guide to website redesign without losing Google traffic first. For help with a maintenance plan or a site that needs fixing, see our web design and development service. The service box below explains how we work.

Frequently asked questions

What do website maintenance services include?

A sound plan covers off-server backups with test restores, tested updates to the CMS, plugins and themes, security monitoring, uptime and form checks, automatic SSL renewal, a Core Web Vitals and Search Console check, a set number of hours for small changes and a monthly report.

How often should a website be maintained?

Backups daily, updates and form tests weekly, a restore test, speed check and Search Console review monthly, an access and software version review quarterly, and renewals and scope reviewed yearly.

Is WordPress maintenance different?

The tasks are the same, but WordPress sites usually have more plugins and themes to update. WordPress lets administrators turn on auto-updates plugin by plugin since version 5.5, and recommends PHP 8.3 or greater.

Which PHP version should my website use?

Use a version that still gets security fixes. On php.net (checked 27 Oct 2026), PHP 8.2 gets security fixes until 31 December 2026, 8.3 until 31 December 2027, 8.4 until 31 December 2028 and 8.5 until 31 December 2029.

Why do SSL certificates need automatic renewal?

The CA/Browser Forum approved cutting the maximum life of public TLS certificates from 398 days to 47 days in steps from March 2026 to March 2029. Short lifetimes make manual renewal risky.

Sources

  1. PHP: Supported versions
  2. WordPress.org: Requirements
  3. WordPress.org: Plugin and themes auto-updates
  4. CA/Browser Forum: Ballot SC081v3, reducing validity periods
  5. web.dev: Web Vitals
  6. Search Console Help: Security issues report
  7. CERT-In: Directions under section 70B(6) of the IT Act, 28 April 2022 (PDF)
#Website Maintenance#WordPress#Website Security#Backups#Business Guide

Found this useful?

Share it with someone who would like it.

Ask AI about this article

Choose what you want, then open it in your favourite assistant. The article link goes with it.

Summarise this article in 5 simple bullet points: "Website Maintenance Services: What a Monthly Plan Should Include" https://www.naveenkapur.com/blog/website-maintenance-services

NK

Written by

Naveen Kapur

Digital marketing, CRM and SaaS, business development, web and app design, and AI automation. Also a graphic and video designer.

Follow on LinkedIn