The plan tiers above answer what it costs. What follows is the detail people actually ask about before buying: what tends to be wrong when somebody starts looking, what has changed to make upkeep matter more, what is deliberately not included, and which platforms we work on.
Jump to: Symptoms · Why it matters now · What is not included · Platforms · Maintenance vs AMC · Maintenance vs Support · Before you hire
The symptoms that usually bring people here
Most people do not search for website maintenance because they have decided it is good practice. They search because something specific is happening.
The site has got slower
And nobody can say when it started, because the change was gradual rather than sudden.
Enquiries have dropped
The contact form turns out to have stopped sending. Silently, weeks ago.
A browser warning appeared
A certificate expired, so visitors now meet a security screen before they reach the site.
The dashboard is full of notices
Updates are waiting and nobody wants to click them in case something breaks.
Something broke after an update
And there is no recent backup to go back to.
The person who built it has moved on
Nobody knows where the logins are, or who the hosting is registered to.
What these have in common is that none of them announce themselves. A site does not tell you the form has stopped working. The enquiries simply stop, and it reads as a quiet month.
Why upkeep matters more than it did five years ago
Three things have changed, and none of them are marketing.
Page experience is part of how Google assesses a page
Google names three Core Web Vitals — Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift — measuring how quickly the main content appears, how quickly the page answers a tap, and how much the layout moves while it loads. A site that measured well two years ago can drift out of the good range without anyone touching it, as content accumulates and third-party scripts pile up. Drift is only visible if somebody is measuring.
Security fixes arrive continuously, not annually
WordPress core, themes and plugins publish security releases on a rolling basis, and the details of what was fixed are public — that is how the fix reaches everyone. The gap between a patch being published and your site applying it is the window that matters, which is why skipping a few months differs in kind from skipping a few days.
Hosts retire old PHP versions, on their schedule
PHP versions reach end of life and stop receiving security fixes, so hosts must move sites forward. On a site whose plugins are current this is routine. On one that is a year behind it is frequently the change that finally breaks something — at a date somebody else chose.
What a maintenance plan does not include
Worth stating plainly, because this is where most disagreements about website support and maintenance services begin.
- New features. Anything that did not exist before — an appointment system, a customer login, a second language — is a build, and it gets its own quote.
- Redesigns. Changing how the site looks is design work, not upkeep.
- Writing your content. Publishing text you supply is included within the allowance your plan carries; writing it is copywriting.
- SEO and advertising campaigns. Keeping a site healthy helps rankings, and it is not a search campaign. Anything sold as both is one of them wearing the name of the other.
Content changes are included within a limit that varies by plan. Larger pieces of work are quoted before they start rather than absorbed quietly and billed later.
We maintain WordPress, and that is deliberate
What we sell is WordPress maintenance services specifically, including WooCommerce stores. If your site runs on something else, it is worth a conversation rather than an assumption — but we would rather say so than list six platforms and learn yours on your time.
There is a practical reason for the narrowness. A provider who touches WordPress every day recognises a plugin conflict from the symptoms. One working across six platforms is reading the same error message you already read. On a store, that difference is measured in the hours your checkout is down.
Website Maintenance vs Annual Maintenance Contract (AMC)
If you have been researching ongoing website care in India, you have probably seen both terms used almost interchangeably: website maintenance and AMC (Annual Maintenance Contract). They are closely related, but not identical, and the difference matters when you are comparing quotes from different providers.
Most Flexible
Website Maintenance
- Ongoing technical upkeep — updates, backups, security monitoring, small fixes — on a recurring schedule, usually monthly
- Sold as a flexible, month-to-month service — start, pause, or cancel anytime
- Scope defined by a simple service tier (Basic, Business, Growth)
- Easier to upgrade, downgrade, or cancel as needs change
Formal Contract
Annual Maintenance Contract (AMC)
- A formal, fixed-term contract — almost always 12 months
- Often paid upfront or in larger instalments
- More common with traditional IT vendors serving larger businesses, government bodies, or organisations needing a signed contract for internal budgeting
- Harder to exit mid-term without a penalty
Which one should you choose? For most small businesses, a month-to-month maintenance plan is the more practical choice — the same technical coverage without a year-long commitment. An AMC makes more sense if an organisation specifically requires a formal annual contract for internal approval, or prefers one annual payment over recurring monthly billing.
WebMaintor offers month-to-month website maintenance services rather than a fixed AMC — no long-term lock-in, cancel with 7 days notice. If you are specifically searching for an annual website maintenance company because your organisation needs a formal yearly contract for internal approval, get in touch — we can structure one.
Website Maintenance vs Website Support — What Is the Difference?
These two terms get used loosely, and since WebMaintor runs two separate services — a dedicated WordPress support service alongside maintenance plans — it is worth being precise about which one actually solves a given problem.
Preventive
Website Maintenance — Preventive, Scheduled
- Runs whether or not anything is currently broken
- Updates applied on a routine, backups taken automatically, security scans run monthly
- Goal: prevent problems before they happen, catch small issues (a failed backup, an outdated plugin) early
Reactive
Website Support — Reactive, On-Demand
- Triggered by something specific already being wrong — a plugin conflict, a white screen, a broken form
- Does not run on a schedule; responds to a described problem
- Delivered with a quote and a fix within a defined turnaround
Where the two overlap: a good maintenance plan often prevents the need for support in the first place — most WordPress emergencies trace back to a missed update or an unmonitored backup. Many small businesses use both: a maintenance plan for ongoing prevention, plus occasional one-off support for a specific bug that needs fixing right away.
Which do you need? If nothing is currently broken and the goal is prevention, website maintenance is the right fit. If something specific is broken right now, WordPress bug fixing or general WordPress support will get it fixed faster. Most WebMaintor maintenance plans already include priority support for exactly this reason.
In practice most businesses want both, which is why so many searches for this put the two words together. The maintenance half keeps the site updated, backed up and monitored so that fewer things break. The support half is who you contact on the day something does anyway. Buy only the support and you pay per incident, and you usually hear about problems from a customer rather than from a monitor. Buy only the maintenance and you have no named person when checkout stops working on a Friday evening.
Our plans are built as website support and maintenance together for exactly that reason: the scheduled work runs every month, and the same people answer when you write in. If the reactive half is all you actually need, our guide to website support sets out what that covers and when it is the sensible choice.
Not sure which one applies? Describe what is happening and we will point to the right service rather than the more expensive one. For a full walk-through of what to check yourself first, see the website maintenance checklist.
Four Checks Before You Hire a Web Maintenance Service
Most of this decision is not about technical skill. Almost anyone can run updates. What separates web maintenance services worth paying for from ones that quietly do nothing is whether you can tell the difference from the outside — and that comes down to four things you can check before signing anything.
- Do you get a report, and does it say anything? “Maintenance completed” is not a report. It should name what was updated, what the security scan found, and what changed in speed or uptime. If a month was quiet, the report should say that too.
- Is a backup taken before the update, or after? Before is the whole point. After an update has broken something, a fresh backup preserves the breakage.
- What is the response time when something breaks, and is that time inside the fee or billed separately? Agree it before you need it, not during.
- Who holds the logins? You should. A web maintenance company that controls your hosting, domain and admin access has made leaving expensive, and that is a business decision they made about you.
Ask whether they work on WordPress every day
Most small business websites in India run on WordPress, so in practice you are comparing WordPress website maintenance services rather than generic ones. It is worth asking outright. A provider who touches WordPress every day recognises a plugin conflict from the symptoms; one who works across five platforms will be reading the same error message you already read, at your expense.
The question to ask is not whether they know WordPress. Everybody says yes. Ask how many WordPress sites they currently look after and what broke on one of them last month. The answer to the second question tells you more than the first.
Freelancer, agency, or maintenance company?
All three do the same work. What differs is what happens on a bad week.
A freelancer is usually the cheapest and often excellent, and the risk is availability — one person cannot answer while they are on a flight or ill. An agency that builds sites and offers maintenance on the side is fine while you are a current client and tends to deprioritise you once the build is finished. A maintenance company does only this, which means the schedule is the product rather than the leftover.
None of those is automatically right. If your site is a brochure that changes twice a year, a freelancer is proportionate. If a day of downtime costs you real money, buy the version where somebody is contractually on the hook.
What website maintenance plans should actually contain
Comparing plans is difficult because everybody lists the same words. The useful comparison is narrower — for any plan you are shown, ask what is not in it:
- Are content edits included, or billed per change? This is the single biggest difference between two plans at the same price.
- Is the backup stored somewhere other than the same server? A backup on the server that failed is not a backup.
- Does website support cover the person who broke something themselves, or only faults the provider caused?
- Is there a lock-in, and what happens to your backups and access on the day you leave?
Our own answers are on this page and in the published pricing: month to month, no lock-in, a written report every month, and everything stays yours. If a provider has quoted you for management rather than maintenance, that is a different product at a different price and worth understanding before you compare the two. If you would rather compare what a plan costs across the market first, the website maintenance cost guide sets out the real numbers.