You have three proposals on the table. All of them promise daily backups, monitoring at every hour, fast response and expert care. They look nearly identical, and the only visible difference is the layout of the PDF. You cannot ask a friend who has used them, and you cannot walk into an office. Somewhere on the other side of the world, a team is asking you to trust them with your website.
The good news is that most claims can be checked, if you know how to turn a promise into a question. This guide shows you how to verify a website maintenance company’s claims before you sign, and how to keep verifying them afterwards. You do not need to be technical. You need patience, a few plain questions and a willingness to ask for evidence.
Most claims are not lies, they are undefined
When people complain about maintenance providers, it is rarely because of an outright invention. It is because a word meant one thing to the seller and another to the buyer. “Backups” can mean a copy kept on the same server as the site, which is useless if that server fails. “Monitoring” can mean an automatic ping every few minutes or a person who looks at a dashboard on Mondays. “Support” can mean someone answers any question or that you may email and wait.
So the aim is not to catch anyone out. It is to pin each word down until you could explain it to a stranger. A provider who welcomes that exercise is usually one you can work with. One who gets irritated is telling you something.
It also helps to know what normal looks like. The page on web maintenance and support from an India-based team spells out the usual monthly work, and it makes a handy baseline: anything a proposal promises beyond that should be written down in detail, and anything missing should be asked about.
How to verify a website maintenance company’s claims, one by one
| The claim | What it might really mean | What to ask for |
|---|---|---|
| “Daily backups” | A copy exists, somewhere. Possibly files but not the database, possibly on the same server. | Where are they stored, what do they include, how many days are kept, and when was a restore last tested? Ask to see a restore done on a test copy. |
| “Uptime of 99.9%” | A target, often measured by the host or the provider’s own tool, and often excluding planned work. | Who measures it, how often, what is excluded, and what happens if it is missed? You can also set up your own free monitor to cross-check. |
| “Constant monitoring” | An automated alert, perhaps going to a shared mailbox nobody reads at night. | What is monitored, who receives the alert, and what that person is allowed to do about it? |
| “Fast response” | An acknowledgement, not a fix. | Is it time to reply or time to resolve, in which hours, and which channel? Get it in the contract. |
| “Unlimited updates” or “unlimited changes” | Unlimited within an unwritten fair-use limit. | What counts as one change, and what happens at the limit? |
| “Malware-free promise” | Free cleanup if hit, with conditions, or only on certain plans. | What is the exact wording? What is excluded? |
| “SEO included” | Anything from basic hygiene checks to nothing. | Which named tasks, and what is reported? Honest providers do not promise positions. |
| “Expert team” or “certified” | Marketing language. | Who exactly will touch my site? Can I talk to that person? |
| “We manage many sites” | Could be true, could be an old figure. | Can I speak to one current client? A named reference beats a number. |
The pattern is the same each time: replace an adjective with a noun, a number or a name. If a claim cannot be restated as something you could check, it is a feeling rather than a promise.
Uptime figures deserve a closer look
Percentages sound precise and are easy to misread. A figure of 99.9 per cent over a year still allows a little under nine hours of downtime. Whether that is acceptable depends on your business. A hairdresser’s brochure site can live with it. An online shop in the middle of a sale cannot.
Ask three things: what counts as down (a total outage only, or also a broken checkout?), what is left out (planned work, host failures, attacks), and where the number comes from. If you want to understand what a monitor actually watches, website uptime monitoring explains the basics. Then run an independent monitor of your own for the first few months. Most are free for a single site, and the comparison costs you ten minutes to set up.
Check the company itself, not only the claims
With a provider in another country, the basics of identity matter more, not less. Before the contract, find out:
- Who you are contracting with. A legal business name, an address and a registration where one applies, written on the agreement and the invoices.
- Who the humans are. A named contact and a way to reach a second person if the first is away.
- Whether the website matches reality. Does it describe a team, or only slogans? Do the details line up across the site, the contract and the invoice?
- What others say, off their own site. Look for reviews and mentions on independent platforms. Treat all of them with some caution, since reviews can be bought, but a total absence of independent presence is information too.
- Whether you can talk to a client. A reference who agrees to a ten-minute call is worth far more than a polished testimonial.
Some of these are covered in more depth, with the specific points for India, in how to vet an Indian website maintenance company.
What good evidence looks like
Not all proof is equal, and it helps to decide in advance what you will accept. Strong evidence is dated, specific to a real site, and something you could confirm for yourself. A backup log with timestamps, a report that names exact plugin versions, a monitor you can view directly, a client who will take your call: all of these hold up.
Weak evidence is the kind that looks good and tells you nothing. Badges and logos with no explanation, a row of company names with no context, screenshots with no date, round numbers such as “hundreds of sites” and phrases like “industry-leading”. None of it proves anything false. It simply cannot be checked, so give it no weight.
Notice also how a provider reacts when you ask for the strong kind. Someone who runs a tidy operation tends to have a sample ready or can produce one quickly. Someone improvising has to build it on the spot, or finds a reason not to.
Try them before you commit
You can learn a lot from small, cheap experiments during the sales stage.
- Send a real question and see what you get back. Is it specific to your site, or a template? Do they ask about your platform, your plugins, your checkout?
- Ask for a sample report. It should name what was updated, what was found and what was left alone. A report full of green ticks and no detail is decoration. What a website maintenance report should tell you sets out what to look for.
- Request a short test task. A small, paid, clearly bounded job, such as fixing a minor layout issue, shows how they communicate, how they handle access and whether they ask before touching things.
- Ask them to explain a technical term to you. The ones worth hiring can do it without condescension.
- Ask what they will not do. Every serious provider has limits. If the answer is “nothing, we do everything”, be careful.
Read the fine print for what hides behind the claims
Most of the unpleasant surprises sit in the terms rather than the sales page. Look for these:
- Minimum commitments and what notice is needed to end them.
- Who owns the logins, backups and licences, and what is handed back on exit.
- Whether content edits, plugin licences or emergency work cost extra.
- Which hours the response promise covers, and in which time zone.
- What the provider is not responsible for, such as problems caused by third-party plugins or the host.
The questions are the same ones you would ask about any contract, and the website maintenance proposal checklist turns them into a form you can fill in while comparing offers side by side.
Keep checking after you sign
Verification does not end on the day of the first payment. Once a month, do a small round of your own that costs five minutes:
- Compare the report with what you can see yourself. Is the version number of a plugin what they say? Does the date of the last backup make sense?
- Submit your contact form and confirm the email arrives.
- Log in to your own hosting account and check nothing unexpected has changed.
- Look at whether people in your team with access still need it.
- Note anything the report promised that did not happen.
Keep a short record: date, what you checked, what you found. If you ever need to raise an issue, a dated note is much stronger than a feeling that things have been slipping.
If a claim does not hold up
When you verify a website maintenance company’s claims and one fails, start with a calm written question, quoting the claim and the evidence. Most gaps are misunderstandings, and a decent provider will fix the wording or the service. If the answer is evasive, or the same gap repeats, you have learned what you needed to know. Having the logins, backups and hosting in your own name makes leaving straightforward.
The same standards apply to us. Anything we say about what we do should be written down in the quote before you pay, with a plain explanation you can check. A sample report is a fair request to make of any provider, and our free check of your site lets you judge how we communicate before you commit to anything.
Next in this series: What Affects a Website Maintenance Quote
