“We watch your site” is the most common promise in a website maintenance retainer and the least defined. Some studios mean a monthly plugin update. Others mean someone looks at uptime alerts around the clock. Before you pay for a retainer, make the vendor say what watching includes, in a list you can check against.
Here is what a website maintenance retainer should cover, what it usually does not, and how to tell whether the watching is real.
What does a website maintenance retainer need to include?
At minimum: updates to the CMS, themes and plugins; tested backups; uptime monitoring with a named person who gets the alert; a security check on a fixed rhythm; and a way to ask for small changes. If any of those is missing from the proposal, ask why.
Updates are the part everyone expects, but the detail matters. Are they applied on a copy of the site first, or straight on the live one? A plugin update that breaks the checkout page at 2 p.m. on a Friday is a bad way to discover the answer. Good practice is to test on a staging copy, then apply, then look at the pages that earn money.
Ask also what happens to updates that cannot be applied safely, such as a plugin that is abandoned or a theme that conflicts. The vendor should flag it and propose a replacement, not leave it sitting there.
How do you know backups and uptime monitoring actually work?
A backup you have never restored is a hope, not a backup. Ask when the last restore test happened, where the copies are stored, and whether they sit on the same server as the site. If the server fails and the backups die with it, the retainer protected nothing.
For uptime, the questions are simpler. How often does the monitor check? Does it test just the home page, or also a form and the checkout? Who receives the alert, and within what window are they expected to respond? “Monitored” with no response window tells you very little.
It also helps to see something. A short monthly note stating that backups ran, updates were applied, and nothing went down takes ten minutes to write and tells you the work happened. When it is missing for two months in a row, that is your answer.
Which tasks sit outside the retainer?
Most retainers separate maintenance from change. Keeping the site healthy is one job; adding a page, rewriting a service description or building a new feature is another. Our post on content changes versus deploys explains why that split keeps tickets from stalling.
Also check what happens after a hack or a major break. Cleaning up a compromised site is usually a separate project, not a routine task. Some retainers include a limited number of hours for emergencies; others bill by the hour. Whichever it is, write it down before you need it. Where you want a one-time hardening pass first, the security pass is a sensible starting point.
One more gray area: performance and SEO. Keeping speed from degrading is maintenance. A new SEO plan is a project. Agree on which one you are buying.
How should you compare retainer offers?
Put the proposals in columns and compare what is actually promised: update rhythm, backup storage and test frequency, monitoring window, response time for a problem, monthly report, hours available for small changes, and what is excluded. Price comes last, because a cheaper retainer that skips restore tests costs more on the day something fails.
Ask for the access terms too. You should own your domain, hosting account and admin logins, and the vendor should work through accounts you can revoke. That avoids being locked in. The website support service page describes BeWebco’s support options, and the FAQ covers common questions.
Checklist for the next renewal
- Updates tested before they go live.
- Backups stored off the web server, with a recent restore test.
- Uptime alerts go to a named person with a response window.
- A short monthly report arrives without being chased.
- Small changes and emergencies have stated hours and rules.