Guides
How to Choose a Website Maintenance Company
A practical guide to evaluating website maintenance providers: what good looks like, which questions to ask, and the red flags that should make you walk away.
- Published
- Reading time
- 7 min read
Choosing a website maintenance company is harder than it looks. Most providers list similar features: updates, backups, security, monitoring and support. On a comparison page they can appear almost identical, yet the difference between a careful provider and a careless one only becomes visible when something goes wrong, such as an update that breaks checkout or a backup that will not restore.
Your website is often your shop window, your lead generator and, for e-commerce businesses, your till. Handing it to someone else is a decision about risk, not just a purchase. The aim of this guide is to help you look past the feature list and assess how a provider actually works.
We will cover what to define before you start, the capabilities that matter most, the questions to ask in a sales conversation, and the warning signs that suggest you should keep looking.
Start with your own requirements
Before contacting anyone, write down what you need. Providers can only be compared fairly against a clear brief.
- What platforms do you run? WordPress, WooCommerce, Magento, Shopify, a custom PHP or Node.js application, or a mix.
- What is business-critical? A brochure site that generates occasional enquiries has very different needs from a store taking orders around the clock.
- Who hosts it? Shared hosting, a managed host, a VPS, or your own cloud account. This decides whether the provider also needs to look after the server.
- What hours matter? If you sell internationally or run campaigns at weekends, office-hours-only support may not be enough.
- What do you want to stop doing yourself? Updates, plugin conflicts, content changes, hosting tickets, certificate renewals.
A short requirements list like this also helps you match to a sensible plan size. Our maintenance plans page shows how scope typically scales from a single brochure site to complex multi-server estates.
The capabilities that matter most
A safe update process
Updates are the most frequent maintenance task and the most common cause of self-inflicted outages. Ask how updates are applied. A careful provider will:
- Take a fresh backup immediately before updating.
- Apply updates on a staging copy first where the platform allows.
- Run checks on key journeys such as forms, login, basket and checkout.
- Deploy to production and recheck.
- Have a documented rollback route if something fails.
Blindly enabling automatic updates on everything is not a maintenance process. It may be appropriate for some low-risk components, but it should be a deliberate decision, not a substitute for testing. Our article on what happens when you don't update WordPress explains why skipping updates is not the answer either.
Backups that are tested, not assumed
Almost every provider says they take backups. Far fewer can show you evidence that they restore them. Ask where backups are stored, how long they are kept, whether they are held off-site and separately from the hosting account, and when they last performed a test restore. We cover the common failure modes in why website backups often fail.
Security as routine, not as an add-on
Good maintenance includes baseline security work: removing unused plugins and accounts, enforcing strong authentication for administrators, applying security patches promptly, monitoring for malware and file changes, and managing a web application firewall where appropriate. Ask what happens if your site is compromised. Is clean-up included, charged separately, or excluded entirely?
Monitoring with a human response
Uptime checks every few minutes are easy to set up. What matters is what happens when an alert fires at 2am. Ask who receives alerts, what they do, and how quickly they are expected to act for different severities.
Clear reporting
You should be able to see what was done each month without asking. A useful report lists updates applied, backups taken and tested, security findings, uptime and performance observations, and recommendations. If a provider cannot show a sample report, that tells you something.
Questions to ask a maintenance provider
Use these questions in your conversations. The answers are often more revealing than the proposal.
| Question | What a good answer includes |
|---|---|
| How do you apply updates? | Pre-update backup, staging-first where possible, functional checks, rollback plan |
| When did you last test a restore for a client? | A specific process and a schedule, not "our backups are reliable" |
| Where are backups stored and for how long? | Off-site, separate from the host, defined retention periods |
| What does your SLA define? | Severity levels, response targets for each, support hours and escalation route |
| What is excluded from the plan? | A clear list, such as new development, design changes or third-party licence costs |
| Who will we deal with? | A named point of contact backed by a wider team |
| How do you store our credentials? | A credential vault, least-privilege accounts, no shared passwords by email |
| What happens if we leave? | Full handover of access, backups and documentation |
| Can we see a sample monthly report? | Yes, with real structure rather than a marketing summary |
Check platform and technical fit
General competence is not enough; the provider needs relevant experience with your specific stack. A team that maintains hundreds of simple WordPress brochure sites may not be the right fit for a busy WooCommerce store with custom integrations, or a Magento installation with a complex extension stack and its own server.
Ask about:
- Platform depth. How many sites on your platform do they maintain, and what versions? Can they explain the platform's own upgrade path, such as major Magento or PHP version upgrades?
- Hosting and server skills. If your site runs on a VPS or cloud account, can they patch the operating system, tune the web server and database, and manage firewall rules? Or will they only touch the application layer?
- Integrations. Payment gateways, ERP or CRM connections, stock feeds and marketing tools often break during updates. Ask how they test these.
- Custom code. If your site includes bespoke themes or plugins, check whether the provider can maintain them or will only update third-party components.
Asking for an illustrative walkthrough of a recent, comparable piece of work is reasonable. You are looking for specifics: how they spotted a problem, what they changed, how they tested it and how they communicated with the client.
Red flags to watch for
Some warning signs come up repeatedly when businesses switch providers after a bad experience.
- Guarantees that cannot be honoured. Nobody can promise 100% uptime, first-page rankings or a site that can never be hacked. Responsible providers talk about reducing risk and responding quickly.
- Vague scope. "Unlimited support" or "we'll handle everything" usually means disputes later about what is actually included.
- No staging or rollback process. Updating live sites without a safety net is a common cause of outages.
- Shared or emailed passwords. Credential handling is a good indicator of overall security discipline.
- No written SLA. Without one, response times are whatever happens to be convenient.
- Lock-in. Refusing to hand over access or backups when you leave is a serious concern.
- Silence. If you only hear from a provider when the invoice arrives, you cannot tell whether work is being done.
Comparing proposals fairly
Price matters, but compare like with like. A lower monthly fee may exclude restore testing, security clean-up, out-of-hours response or staging environments. When comparing proposals, map each one against your requirements list and note what is included, what is charged extra, and what is not offered at all.
It is also worth asking how the provider handles work outside the plan. Clear rates or estimates for out-of-scope work, agreed before work starts, avoid surprise invoices. Our article on website maintenance costs explains the factors that typically drive pricing.
Onboarding: the first real test
The way a provider onboards you shows how they will work for the rest of the relationship. A thorough onboarding should include an initial technical assessment, secure handover of credentials, documentation of your assets and integrations, baseline backups that are verified, and monitoring set up before routine maintenance begins. If a provider wants to skip straight to "we'll start updating next week", ask why.
At SupportSafe we follow an assess, onboard, maintain, monitor, report and improve cycle, and you can see how that works in practice through our website maintenance service.
Making your choice
The right maintenance company is the one whose process you can see and verify. Look for staging-first updates, tested backups, clear security responsibilities, a written SLA, transparent reports and an easy exit. Ask direct questions and expect direct answers.
If you would like to see where your website currently stands before speaking to any provider, start with a free website health check. It gives you an independent baseline you can use to compare proposals, including ours.