What to check, how often, and who's actually responsible — a practical checklist, not a sales pitch.
Quick answer: Website maintenance breaks down into daily checks (uptime, security alerts), weekly checks (backup verification, broken links, forms/checkout testing), and monthly checks (core/plugin updates, a full restore test, performance review). Responsibility splits three ways — your hosting provider handles server infrastructure, your developer or maintenance plan handles updates and backups, and you as the owner handle content and flagging issues. See our Website Maintenance Services page for commercial plans and support terms.
Task frequency scales with how business-critical your site is — a high-traffic e-commerce store needs tighter monitoring than a low-traffic brochure site. This is confirmed during a free consultation, not applied as one flat checklist for every site.
A backup that's never been restored is unverified — teams often discover a backup was silently failing only when they actually need it. Restore testing (not just backup scheduling) is what makes a backup plan trustworthy.
| Check | What to Look For | Frequency |
|---|---|---|
| CMS/plugin updates | Security patches applied promptly, tested on staging first for major updates | Monthly (security patches: as released) |
| Uptime | Automated monitoring alerting within minutes of downtime | Continuous |
| Broken links | Internal and outbound links returning 404s | Weekly |
| Forms | Enquiry/contact forms actually deliver submissions to the right inbox | Weekly |
| Checkout | Full test purchase completes, payment gateway confirms correctly | Weekly (e-commerce) |
| Task | Site Owner | Developer / Maintenance Plan | Hosting Provider |
|---|---|---|---|
| Content updates | Primary | On request | — |
| CMS/plugin updates | — | Primary | Server-level patches only |
| Backups | Verify exists | Primary (scheduling + restore testing) | Often provides base backup tool |
| Server uptime | — | — | Primary |
| Broken link/form checks | Flag issues noticed | Primary (scheduled checks) | — |
| SSL certificate | — | Confirms it's active | Primary (issues/renews) |
Illustrative example of what a monthly maintenance report looks like — labelled example data, not a real client's report.
| Uptime | 99.9% (example) |
| Backups completed | 30/30 days (example) |
| Restore test | Passed (example) |
| Plugin/core updates applied | 6 updates (example) |
| Broken links found & fixed | 2 (example) |
| Form/checkout tests | Passed (example) |
From startups to enterprises — brands that grow with MetaReach