The invoice arrives, and it is not the one you expected. You have been paying a monthly fee for a year, you asked for a new booking page, and now there is a separate quote for it. Your first thought is that you are being charged twice. The provider’s first thought is that nobody ever promised a new page.
Almost every argument about this comes from the same place: nobody wrote down what website maintenance plans do not cover, so each side filled the gap with a reasonable assumption. This post is for the owner who would like to avoid that conversation. It goes through the usual exclusions, the grey areas where plans genuinely differ, and the questions that make the boundary visible before you sign.
What website maintenance plans do not cover, in plain terms
A maintenance plan is upkeep. It keeps the site you already have healthy and working. Anything that changes what the site is, or adds something that did not exist, normally sits outside it. That one distinction explains most of the list below.
New features and new pages with real work behind them
Swapping a phone number is upkeep. Adding an enquiry form that sends each answer to a different person is a build. The same goes for booking calendars, customer accounts, a second language, a quote calculator or a members area. If it needs planning, testing and a decision about how it should behave, expect it to be quoted separately.
Plans usually allow a certain amount of content editing, such as changing text, replacing images or publishing a page you have already written. Where “editing” ends and “building” begins is the single most useful thing to get in writing.
A redesign, or a change of look
New colours across the whole site, a new homepage layout or a move to a different theme is design work. It touches every page, it needs your approval at several stages, and it can change how the site ranks. Maintenance can run alongside a redesign, but it does not absorb one.
Writing, photography and anything creative
Someone can publish your blog post. Someone else has to write it. The same applies to product descriptions, case studies, product photos and short videos. A maintenance team works on the site’s health and the pages you hand over; it is not a marketing department.
Search, ads and social campaigns
A site that loads quickly, has no broken pages and stays secure gives search engines fewer reasons to distrust it. That is a healthy foundation. It is not a ranking strategy, and it does not run your ads. If a plan quietly includes “SEO” for the same monthly fee, ask what exactly is being done and how you will see it.
Subscriptions that belong to other companies
Hosting, your domain name, a premium theme licence, a paid plugin, an email marketing tool, your online store’s payment processor: each of these has its own renewal, sold by someone else. A maintenance team can remind you, check expiry dates and apply updates, but the renewal itself is normally billed to you by the supplier. Do not assume a plan swallows them.
The in-between tasks that cause most disagreements
Some tasks sit on the line, and different providers draw it in different places. Neither answer is wrong. What matters is that you know which one you have bought. If you want to see one provider’s line laid out in full, the page on website maintenance services India shows what an India-based team covers each month and what it leaves out, which gives you something concrete to compare other offers against.
| Task | Often inside a plan | Often charged on top | Question to ask |
|---|---|---|---|
| Cleaning up after a hack | Scanning and monitoring | The cleanup itself | Is cleanup included, or only the watching? |
| Fixing a plugin that broke after an update | Rolling back or fixing what the team updated | Problems from changes someone else made | Who is responsible if my own editor causes it? |
| Small design tweaks | A spacing or colour fix on one page | Layout changes across many pages | What is the limit before it becomes a quote? |
| Moving to a new host | Sometimes a basic handover | Full migration with testing | Is a migration a separate job? |
| Speed improvements | Routine upkeep that stops things slowing down | A dedicated speed project | Is a one-off speed project priced separately? |
| Training your staff | Answers to quick questions | A recorded walkthrough or session | How are longer explanations handled? |
Monitoring is not the same as repair
This is the confusion that costs people the most. A security scan tells you something is wrong. It does not clean the site. Uptime monitoring tells you the site is down. It does not mean the person watching will also fix whatever caused it, at no extra charge, within a stated time. Read the wording closely: “monitoring” and “fixing” are two promises, and a plan may offer only the first.
Problems you cause yourself
An editor installs a new plugin on a Friday and the checkout stops working. A colleague deletes a page. Someone pastes code from a forum into the theme. Most providers will help, but they treat it as a fix rather than as upkeep, because the cause was outside the plan. If several people edit your site, say so up front, and ask how that is handled.
Problems that began before the plan did
If you hand over a site that has been neglected, with a year of unapplied updates and a theme that no longer receives fixes, expect a first piece of work that is not routine. Catching up is a project. Staying caught up is the plan. A sensible team looks first and tells you which is which.
Why the boundary is not a trick
It is fair to feel suspicious when a monthly fee comes with a list of things it does not cover. In most cases the list is the honest part, and knowing what website maintenance plans do not cover is what lets you judge whether the fee is fair. A fixed monthly arrangement works because the work is predictable: updates, backups, checks, small corrections. The moment it has to absorb a redesign, it either becomes enormously expensive or the provider quietly does less of everything else.
The warning sign is not an exclusion list. It is a plan with no exclusions, or one that is vague about them. If something is described as “unlimited” or “everything you need”, ask what happens on the tenth request in a month and who decides when a change counts as small.
For an overseas buyer, the risk is slightly bigger
When you work with a team in another country, you cannot lean over a desk and say “surely that was included”. Messages cross time zones, an unclear request can lose a day, and a misunderstanding about scope often arrives as a surprise invoice on a day when you cannot easily talk it through. This is not a reason to avoid working with a team abroad. It is a reason to be more precise on paper.
Write the boundary down: a short checklist
You do not need a long contract to avoid most misunderstandings. You need a page, agreed by both sides, covering these points:
- A list of included tasks, in ordinary words: updates, backups, security checks, uptime monitoring, reports, small content changes.
- A limit on content changes, stated as something countable, such as a number of edits or an amount of time, so both of you can tell when it is reached.
- A list of excluded work, with the words “quoted before it starts” next to anything that is not routine.
- How a request is classified: who decides whether a change is small, and how you are told.
- What happens after a failure: whether fixing a breakage is part of the plan, and what the provider needs from you to do it.
- Who holds each account: domain, hosting, premium licences, analytics, and who pays each renewal.
- How you leave: what you receive if you stop, including backups and the access list.
A proposal checklist for website maintenance goes through the same ground from the buyer’s side if you are comparing written offers.
What to do when you need something that is not covered
You will need work outside the plan sooner or later, and that is normal. The aim is to make the conversation boring. A good routine looks like this.
- Describe the outcome, not the method. “Customers should be able to book a time slot” is more useful than “install a calendar plugin”.
- Ask for the quote in writing first. It should name what is included, what is not and what you need to supply, such as text or images.
- Ask whether it can wait. Some jobs are urgent, many are not, and bundling several into one piece of work is often tidier than a string of small ones.
- Keep requests in one thread. One email chain or WhatsApp group with a clear subject saves the question of what was agreed in March.
If a particular thing has actually broken rather than being a new request, ask whether it should be handled as a separate WordPress bug fixing job or falls inside your plan. And if what you really want is a different-looking site, the honest route is a proper website redesign, planned on its own, with maintenance continuing quietly in the background.
Is a monthly plan the right shape at all?
Sometimes the reason a plan disappoints is that it was never the right shape. If your site is small, changes rarely and has someone in-house who is comfortable applying updates, paying only when something goes wrong can be sensible. If it takes orders, collects enquiries or receives paid traffic, the routine work is worth having done on a schedule. There is a plain comparison in pay per fix versus monthly maintenance, and it is worth reading before you decide how much you want inside the plan and how much you would rather buy as needed.
A few mistakes to avoid
- Assuming a name means a scope. “Care plan”, “support plan” and “maintenance package” are marketing labels. Only the list of tasks tells you what you are getting.
- Comparing plans by length, not content. A long feature list that includes things you will never use is not better than a short one that covers what you need.
- Treating a quiet month as wasted money. A report that says nothing changed and nothing broke may be the plan working. The point is to know that, not to guess it.
- Not reading the exclusions until something breaks. Read them first, while no one is stressed.
Before you sign
Ask any provider what a maintenance plan does not include, and listen to how they answer. You do not need one who agrees to everything, and you should be wary of one who agrees to everything quickly. You need one who can tell you, calmly, which side of the line a request falls on and why. Not sure what your own site needs today? A free review of your current site gives you a starting picture before you decide what to buy.
Next in this series: Safe Website Access for an Overseas Team
