Website maintenance, because a website is software

What maintenance means, and how much of it you need

Maintenance is two different jobs wearing one word, and separating them is the first useful thing anyone can tell you. The first is keeping the lights on: security and software updates, backups you could actually restore from, uptime monitoring, a valid certificate, a domain that does not lapse, and a periodic check that your contact form still delivers to an inbox somebody reads. The second is upkeep: a new service page, a changed phone number, updated hours, photos from last week's job, a price that is no longer true.

Both matter, and they are not the same spend. Bundling them under one word is how owners end up either paying monthly for a plan that does almost nothing, or ignoring the site until it embarrasses them.

The first job exists because a website is software, not a printed brochure. It sits on a stack of things that keep moving whether you look at them or not. Browsers change what they accept. Plugins develop security holes, get patched, or get abandoned. The mail service that delivers your form submissions changes a setting. A payment processor retires the integration version your checkout was written against. None of that is dramatic on any given Tuesday, which is exactly why it gets ignored until it is expensive.

How much you need depends far more on how the site is built than on how big your business is. Roughly:

• A lean static site, plain files with no database and no plugin stack, has very little that can break. Hosting, the domain, the occasional edit, and a periodic check that the forms still work.
• A WordPress or plugin-heavy site is the opposite. More moving parts, more updates, and a real chance that patching one thing breaks another. This is where most maintenance money goes, and for good reason.
• A site with logins, bookings, or a live checkout needs the most, because a quiet failure costs the most. An online store that stops taking orders on a Saturday does not send you an email about it, and custom features carry more surface area than a plain page.

So the honest framing is not that everyone needs a plan. It is this: find out what your site is made of, keep the cheap insurance regardless, and buy upkeep in proportion to what the site earns you. If you do not know, the free website report card is a fair place to start before you talk to anybody, including us.

What gets done, and how often

Here is the actual list, without the padding that usually fills a care-plan page. Not every site needs every line, and part of an honest scope is naming the ones you can skip.

The recurring plumbing.

• Software and security updates. Patching the platform, the theme, and the plugins, in an order that does not take the site down. On a lean custom build this list is much shorter, which is one of the better arguments for building lean.
• Backups, and the part nobody checks. Taking a backup is easy. Knowing you could restore from it is what gets skipped, so the useful version of this job includes testing a restore rather than trusting a green checkmark.
• Uptime and certificate monitoring. Knowing the site is down before a customer tells you, and that the certificate is about to expire before a browser warns your visitors.
• Form and lead-path testing. The most common silent failure on a small business site: a form that submits without complaint and quietly delivers nowhere. The whole path gets tested: the form, the delivery, the inbox, and the spam folder it may land in.
• Broken links and missing pages. Links rot as things get renamed and pages retired. Finding them is dull, routine work, which is precisely why it should be routine.
• Speed checks. Watching for the slow creep. A photo somebody uploaded at full camera resolution. A script added for a trial that never got removed.
• Domain, DNS, and mail records. So a domain does not lapse and email does not stop delivering because a record got changed during some unrelated task.

The content upkeep.

• New service and area pages as you add work or towns.
• Text edits, price changes, hours, staff changes, seasonal notices.
• New photos of real jobs, sized properly instead of dropped in raw, and the details in search kept consistent with your Google Business Profile, so the same name, number, and address appear everywhere.

The part that gets forgotten. Tracking breaks too. Analytics tags get dropped during a redesign, or a conversion event stops firing after a form is rebuilt. The charts keep drawing, so nothing looks wrong, and decisions get made on numbers that stopped counting. Keeping measurement honest belongs in upkeep, and analytics and conversion work covers the deeper end of it.

Frequency is duller than the list. Security and backups run on a steady schedule, form and link checks on a rhythm rather than a whim, and content edits on your calendar, whenever something in the business changes. That is the whole cadence.

Why we scope this against your site instead of a tier chart

Most maintenance is sold as bronze, silver, and gold. Three columns, a grid of checkmarks, and the same number every month regardless of what your site is made of. Easy to sell, easy to bill, and it is why so many owners pay for a plan that has nothing to do with their actual risk.

A tier chart prices the plan against the seller's convenience instead of your site's moving parts. Two businesses in the same trade, same town, same revenue, can need wildly different upkeep: one runs six static pages, the other runs a booking system, a customer login, and a store. A tier chart drops them both in silver.

We work the other direction, and want four answers before quoting anything ongoing: what the site is built on, how many outside services it depends on, what a full day of downtime would cost you, and how often you genuinely need something changed. Those four determine the work. Everything past that is packaging.

This is also why we build sites the way we do. Much of what people pay for in maintenance is the cost of complexity somebody else added: a page builder plugin, a slider plugin, a forms plugin, then a caching plugin to fix the slowness the first three caused. A site without that stack has less to keep patched. How we build has the longer version, and custom web design covers a lean build.

One honest note about scope. The routine work above is the steady part, and it runs on a schedule. The deeper passes, a full performance audit with real browser traces, an accessibility review against WCAG, an adversarial security review, automated browser testing that clicks through the site the way a customer would, are capabilities we reach for when a site needs them, not a monthly ritual we bill everyone for. We would rather name them as tools on the shelf than dress them up as a standing service.

It is also fair to say plainly who we is. Kelly Webmasters and Marketers is one person in Orlando, working remotely with local service businesses around the country. No overnight support desk, no rotating queue of technicians. What you get instead is that the person answering your text about a broken form is the person who wrote it. For most small businesses that is the right trade. For an operation needing guaranteed round-the-clock coverage it is not, and we would rather say so on the first call than in month three.

What a month looks like

A good maintenance month is boring, and the boredom is the product. Here is the shape of it.

It starts with a look at what you have. Before any arrangement, we go through the site: what it is built on, which plugins or outside services it leans on, where the forms deliver, whether backups exist, and whether anything is already broken. This is where the surprises live. A contact form pointing at an employee who left two years ago is a common find.

Then a written scope, in plain language. What is covered, what is not, and how much editing per month is included before something becomes a project instead. Vague scope is how maintenance relationships go bad, so we would rather over-specify up front and have you strike half of it.

Then the routine. Updates and backups on a schedule. Forms, links, and speed checked on a rhythm. When something is found it gets fixed, and you get a note in English rather than a log file you will not open.

Then the requests. This is the part owners feel week to week. You send a photo and a sentence, and the page changes. New service, price change, a truck photo for the home page, a notice about holiday hours. Text it to (407) 694-2055. We would rather have a messy text than watch you sit on a change for three months because submitting it felt like paperwork.

And a short report, not a dashboard tour. What was updated, what broke, what was fixed, what changed. If you want the deeper measurement view, that belongs in analytics, and it should tell you whether the site is producing calls and forms, not only whether it stayed online.

Two things we do not do. We do not touch a site we did not build without telling you first what we are about to change, and we do not hide behind a ticket system. Everything is month to month with no long contract, and you own the domain, the files, the content, and every account. If it stops being worth paying for, you leave with the site intact and nothing to untangle.

The failures nobody notices until later

Three quiet failures do most of the damage on neglected sites, and none of them look urgent on the day they start.

The form that stopped sending. It still shows a thank-you message and still looks fine on the page. Meanwhile delivery stopped weeks ago because a mail provider changed a setting, or because the address behind it belongs to somebody who left. Owners usually discover this by wondering why the phone got quiet, which is a terrible detection system. It is also the cheapest thing on this page to check on a schedule.

The measurement that quietly went blank. Analytics gets dropped during a redesign, or a conversion event stops firing when a form is rebuilt. The reports keep producing charts, so nothing looks broken, and decisions get made on numbers that stopped counting. We run first-party lead dashboards on more than 20 of the sites we manage, for exactly this reason: a lead you can see landing in one place is harder to lose track of than a lead scattered between a mail inbox and a form service nobody logs into.

The slow drift. Nothing breaks. The site just gets a little older every month. Photos from a service you no longer offer. A page about a town you stopped driving to. Text written for how the business ran four years and two trucks ago. None of it is an emergency, and all of it quietly costs you credibility with the person deciding whether to call. Search notices as well. Rankings respond to pages that stay current, links that work, and pages that load at a reasonable speed. Nobody can promise you a position or a date for one, and anyone who does is guessing, but a maintained site competes from a better starting line than one left alone for three years.

A fourth category sits between maintenance and a new project: the site that has drifted so far that upkeep is the wrong tool. If it is several platform versions behind, built on extensions nobody supports, and slow in a way no caching fixes, patching it monthly is renting a problem instead of solving it. We will say so, and price a rebuild honestly, including the case where a rebuild costs less across two years than the maintenance would. If it comes to that, we will build you a free mockup of the replacement first.

What upkeep costs here

There is exactly one published figure attached to ongoing work here, and it is deliberately narrow. For the calculators and small apps we build, Tool Care is $75 a month per tool. That covers keeping one tool running: hosting it, keeping it working as browsers and dependencies move underneath it, and fixing it when it breaks. Flat, per tool, month to month.

Website maintenance itself does not get a published number, and we will not invent one for a web page. It is the tier chart problem again: a figure that is fair for a lean five-page brochure is wrong for a store with a live checkout, and a figure fair for the store is robbery for the brochure. So we look first and quote after, flat and month to month.

What honestly moves the number:

• What the site is built on. Lean and custom, or a platform with a plugin stack that has to stay patched. The biggest single factor, and it is not close.
• How many outside services it depends on. Every integration is another thing that can change under you: payments, booking, mail delivery, review widgets, chat.
• How often you need changes. A site you touch twice a year and one with a new page every month are different amounts of labor, and labor is nearly the whole bill.
• What downtime costs you. A site that quietly books a few jobs a month can wait until tomorrow. One that is your main source of work cannot.
• Whether we built it. Maintaining something we wrote costs less than learning somebody else's code first. We will still take on sites we did not build, and will say plainly if the first month needs a cleanup.

For a general read on agency pricing, the what should you pay tool gives you one with no sales call attached, and our guide to what a website costs covers building and then keeping a site. If ongoing search work is what you are weighing, what SEO costs is a separate question on a separate line.

That matters more than the number itself. Hosting, maintenance, and growth work should appear as three lines, not one. When a maintenance quote looks high, it usually has SEO, ads, or a redesign folded in. Those may be worth buying, but they are separate decisions at separate prices, and you should be able to cancel one without losing the others. Everything here is month to month, and you own the site, the content, and the accounts.

When you should not buy a maintenance plan

We would rather talk you out of a monthly bill than collect one for work your site does not need. A plan is probably wrong if:

• Your site is a small static brochure you barely touch. No store, no logins, no forms carrying anything critical, and no real cost if it sat untouched for a month. Keep hosting and backups, call when something changes, and skip the recurring line.
• Somebody in-house already does it. If a family member or an employee handles the edits and the updates and does not mind the work, that is a fine arrangement. The question worth asking them is whether a backup has ever been restored, not whether backups exist.
• You need guaranteed coverage overnight and on holidays. One person in Orlando cannot honestly promise that, and we will not write it into an agreement to win the work. If you need a round-the-clock rotation, you need a shop that has one.
• You want maintenance to fix a traffic problem. It will not. Updates and backups keep a site healthy, they do not make more people find it. If the phone is quiet, start with local SEO or lead generation, not a care plan.
• The site should be replaced rather than patched. Sometimes the right advice is to stop paying to keep something alive, and we will say so, even though a rebuild is a bigger conversation than a monthly fee.
• You want us to manage a platform we do not work in. We maintain plenty of things we did not build, but there are setups where somebody in that ecosystem daily will serve you better and cost less. We will say so instead of learning on your dime.
• You are shopping for the lowest possible number. There is always a cheaper plan. Some are a script that runs updates and never checks the result, which is how a broken form goes unnoticed for six months. If price is the only variable, we are not the cheapest and we know it.

If none of that describes you, the work is straightforward: find out what the site is made of, cover the cheap insurance, keep the content current, and stop paying for anything beyond that. We are Orlando-based and have worked with local service businesses nationwide since 2008, long enough to know what neglect costs and to be honest about what a monthly fee can and cannot do. Want an outside look first? Ask for one, or call (407) 694-2055. No charge for a straight answer, and the rest of what we do is listed under services.