A monthly website maintenance plan should include, at minimum, software and plugin updates, off-site backups with tested restores, uptime and error monitoring, security hardening and malware scanning, performance checks, and a small allowance of content or development time. Anything less is a hosting invoice with a nicer name. Maintenance exists because a website is software that depends on other software. WordPress core, Drupal core, themes, modules, plugins, PHP, the database engine, and TLS certificates all change on their own schedules, and the gaps between them are where outages and breaches happen.
Table of Contents
- The non-negotiable core of any plan
- What separates a real plan from a checkbox plan
- Performance, SEO, and the checks worth monthly attention
- What should be excluded, or priced separately
- Sizing a plan to the site you actually have
- Frequently Asked Questions
The non-negotiable core of any plan
Updates come first. On WordPress that means core, theme, and plugin versions; on Drupal it means core and contributed modules, plus Composer dependency updates. Security releases should be applied quickly, while feature releases can wait for a staging test. Backups are second, and the word that matters is *off-site*.
A backup stored only on the same server dies with the server, and a backup nobody has restored is an assumption rather than a safeguard. Ask how often backups run, how long they are retained, where they live, and when the last restore test happened. Third is monitoring. Uptime checks tell you the site is reachable; error and log monitoring tells you it is working. A site can return a perfect 200 status while its checkout form silently fails, so a plan should watch forms, payments, and critical paths, not just the homepage.
What separates a real plan from a checkbox plan
A checkbox plan runs updates straight onto the live site and hopes. A real plan uses a staging environment — a private copy of the site — applies updates there, checks the pages that matter, and only then pushes to production. It also has a documented rollback: restore the backup, revert the deployment, or roll back the single plugin that broke. Security hardening is the other dividing line.
Automatic updates alone are not security. Look for malware scanning, file-integrity checks, a web application firewall or equivalent edge protection, enforced strong authentication with two-factor on admin accounts, a periodic audit of user accounts and roles, and removal of unused plugins and themes, which are a common entry point precisely because nobody watches them. Finally, a real plan reports. A monthly summary should state what was updated, what broke and how it was fixed, uptime for the period, backup status, any security events, and performance numbers. Without a report, you are paying for work you cannot see.
Performance, SEO, and the checks worth monthly attention
Performance work belongs in maintenance because performance decays. New plugins add scripts, uploaded images grow, caches get misconfigured, and database tables fill with revisions, transients, and orphaned rows. A monthly pass should review Core Web Vitals field data in Search Console, re-check caching and image optimization, and clean the database.
Search-related housekeeping is cheap and genuinely useful at monthly cadence: Be clear about the boundary. Maintenance keeps technical SEO from regressing; it does not produce content, build links, or run campaigns. Those are separate services, and a plan that quietly folds "SEO" into maintenance is usually doing the checklist above and calling it strategy.
- Crawl for broken internal links and 404s, and fix or redirect them
- Confirm the XML sitemap is present, current, and submitted
- Check for accidental `noindex` tags or a blocking robots.txt rule after any deployment
- Review Search Console coverage and manual-action notices
- Verify redirects still resolve in one hop after content changes
What should be excluded, or priced separately
Most disputes about maintenance come from scope, not quality. Clarify in writing whether these are included: Development hours are the most common friction point.
A plan with "two hours of changes" is useful for small edits and useless for a new template. Ask how hours are tracked, what the minimum billing increment is, and what happens when a month's work exceeds the allowance.
- Hosting, domain registration, CDN, and premium plugin or module licences
- New features, redesigns, and page builds, versus fixes to existing functionality
- Emergency response outside business hours, and the response-time target
- Hack recovery and cleanup, which many plans cap or exclude entirely
- Major version migrations, such as a Drupal major upgrade or a PHP version jump
Sizing a plan to the site you actually have
Risk drives requirements more than page count does. A brochure site with ten pages and no logins can live comfortably with weekly backups, monthly updates, and basic uptime monitoring. An e-commerce store taking payments, or any site holding personal data, needs daily or continuous backups, prompt security patching, PCI-relevant hygiene, and monitoring on the transaction path. Custom code raises the stakes in both directions.
A site with bespoke plugins, custom modules, or a custom theme cannot be updated blindly, because an update may break code nobody else maintains. Those sites need staging, version control, and a provider who understands the codebase — which is why maintenance for a custom build costs more than for an off-the-shelf theme. Watch for warning signs during the sales conversation: no staging environment, no mention of restore testing, no named response-time target, no monthly report, and no written scope. Also ask the unglamorous question of who holds the credentials and whether you can get full administrative access and a copy of your backups on request. Portability is part of maintenance, and it is easiest to arrange before you need it.
Frequently Asked Questions
Is a monthly plan necessary if the CMS updates itself automatically?
Automatic updates handle only part of the job, and they can break a site without anyone noticing. They do not test the result, restore a backup, scan for malware, audit accounts, or tell you when a form stopped submitting.
How do I verify the backups are real?
Ask for a restore test to a staging URL and look at the result. Also confirm where copies are stored, how long they are kept, and whether the database and uploaded files are both included.
Does maintenance cover getting hacked?
Often not, or only up to a capped number of hours. Read the clause before you sign, because cleanup, reinfection checks, and search-engine blocklist removal can take far longer than a month's allowance.




