Quick Answer: Types of Website Maintenance
There are five types of website maintenance. Corrective maintenance fixes faults that already exist. Preventive maintenance runs checks that stop faults forming. Adaptive maintenance updates a site to match new browsers, devices, and rules. Perfective maintenance improves speed, design, and conversion on a site that already works. Emergency maintenance responds to downtime, hacks, and data loss. Most websites need all five, and the balance between them decides what maintenance costs. Sites that only pay for corrective and emergency work spend the most.
Below is what each type covers, how often it is needed, what it costs, and who should handle it.
What Are Types of Website Maintenance?
Most articles on this topic list tasks and call them types. Backups, plugin updates, speed checks, and broken link fixes. Those are useful lists, but they answer a different question. They tell you what work happens, not what kind of work it is.
The difference matters when you are buying maintenance or planning a budget.
There are two ways to sort maintenance, and they sit on top of each other.
By purpose. Why the work is being done. This gives you the five core types below. It tells you whether you are repairing, preventing, adapting, improving, or firefighting.
By work area. Where the work happens. Security, updates, performance, content, SEO, design, and functionality. This tells you which part of the site is being touched.
Both are real, and you need both. Purpose tells you what your maintenance is costing you and why. The work area tells you what is actually getting done. A plan that covers every work area but only ever does corrective work is still a plan that will keep breaking.
This guide covers the five core types first, then the work areas, then how they fit together. Before that, can you read what website maintenance is?.
The 5 Core Types of Website Maintenance
1. Corrective maintenance
What it is: Fixing something that is broken right now. A form that stopped sending. A page throwing an error. A layout that collapsed on mobile. Corrective work is reactive by definition. The fault came first.
Common examples:
- Repairing a broken contact form
- Fixing a 404 on a page that should exist
- Correcting a layout that breaks at a certain screen size
- Removing spam submissions and tightening filters
- Fixing an integration that stopped syncing
- Repairing broken internal links
How often: Unpredictable. On a well-maintained site, a few small items a month. On a neglected site, constantly.
Typical cost: Charged hourly or pulled from retainer hours. Usually $75 to $200 per hour, depending on the provider.
Who handles it: A developer or agency. Simple content fixes can be done in house, but anything touching code, forms, or integrations needs someone technical.
What happens if you skip it: Faults stack up. Each one on its own looks small, so it gets deferred. Six months later the site has a dozen known problems, and nobody wants to touch it because nobody is sure what else will break.
The trap: Corrective work feels like the only maintenance that matters, because it is the only kind you can see. Something is broken; you fix it, the problem goes away. That visibility is exactly why teams overinvest here and underinvest everywhere else.
2. Preventive maintenance
What it is: Scheduled checks and small updates that stop faults forming. This is the type that produces no visible result, which is why it is the first thing cut and the last thing that should be.
Common examples:
- Testing forms end-to-end on a schedule
- Confirming backups ran and testing a restore
- Reviewing user accounts and access levels
- Scanning for broken links
- Watching page speed before it becomes a problem
- Checking SSL and domain expiry dates
- Reviewing custom code and third-party scripts still in use
How often: Weekly for the fast checks, monthly for the fuller ones. This is the one type with a fixed rhythm.
Typical cost: The cheapest per hour, because the work is known ahead of time and does not happen under pressure. Usually 2 to 4 hours a month for a standard business site.
Who handles it: Best suited to a retainer or an automated system with a person reviewing the output. Alerts nobody reads are not preventive maintenance.
What happens if you skip it: Nothing, for a while. That is the difficulty. Skipping preventive work has no immediate cost, so it never feels urgent. The cost arrives later as corrective and emergency work, at several times the price.
Why it is the highest value type: Every hour of preventive work removes several hours of corrective work later. It is the only type that reduces the size of the other types.
3. Adaptive Maintenance
What it is: Changes made to keep the site working as conditions around it change. You did not cause the change, and you cannot prevent it. You can only respond.
Common examples:
- Fixing layouts after a browser update changes how something renders
- Supporting a new phone screen size
- Updating cookie and privacy notices after a rule change
- Reconnecting an integration after a third party changes its API
- Meeting a new accessibility standard
- Adjusting to changes in how search engines read pages
How often: A few times a year, driven by outside events rather than a schedule.
Typical cost: Varies widely. A cookie banner update is an hour. Rebuilding an integration after an API change can be several days.
Who handles it: A developer, usually with notice. Someone needs to be watching for these changes, which is the part most teams miss. The work itself is not hard. Knowing it is needed is.
What happens if you skip it: The site keeps working until it suddenly does not. An integration silently stops syncing after an API version is retired. A privacy notice falls out of compliance. These arrive without warning if nobody is watching for them.
4. Perfective Maintenance
What it is: Improving a site that already works. Nothing is broken. You are making it faster, clearer, or better at converting.
Common examples:
- Cutting page load time
- Rewriting calls to action that underperform
- Improving mobile layouts based on real behavior
- Refreshing older blog posts that have lost rankings
- Adding sections that answer questions buyers keep asking
- Tidying the CMS so the team can publish faster
- Testing two versions of a page against each other
How often: Ongoing, at whatever pace your budget allows. This type has no natural end point.
Typical cost: Usually the largest share of an agency retainer, because it is the work that produces returns rather than protecting against loss.
Who handles it: A mix. Designers, developers, and someone who understands conversion. This is where an agency retainer pays for itself, since the skills rarely sit in one person.
What happens if you skip it: Your site stays exactly as good as it was on launch day while competitors keep improving theirs. Nothing on your site got worse. You still lose ground.
Why this is the type worth buying: Corrective, preventive, adaptive, and emergency maintenance all protect what you have. Perfective is the only type that grows it. If your maintenance plan has no perfective work in it, you are paying to stand still.
5. Emergency Maintenance
What it is: Urgent response to a serious failure. The site is down, has been hacked, or has lost data. Work happens immediately, often out of hours.
Common examples:
- Site down or unreachable
- Security breach or defaced pages
- Expired SSL certificate blocking all traffic
- Expired domain taking the site offline
- Accidental deletion of pages or CMS content
- Payment or checkout failure on an e-commerce site
How often: Rare on a maintained site. Common on a neglected one.
Typical cost: The most expensive per hour by a wide margin. Emergency and out-of-hours rates are often double standard rates, and the real cost includes lost revenue during downtime.
Who handles it: Whoever can respond fastest and already knows your build. This is the situation where a retainer with an agreed response time justifies its price, and where a freelancer who is unreachable on a Saturday costs you dearly.
What happens if you skip it: You cannot skip it. Emergency work is the type that happens to you. The only choice you have is how often, and preventive work is what decides that.
The 5 Types At Glance
Read the cost column as a pair with the timing column. Preventive work is cheap because it is planned. Emergency work is expensive because it is not.
The Practical Categories of Maintenance Work
The five types tell you why work happens. These categories tell you where. Every maintenance plan should touch all seven.
Website maintenance and security
Website maintenance and security overlap so heavily that many people treat them as the same thing. They are not. Security is one work area inside maintenance, and it spans several of the five types.
Security covers spam filtering, access control, SSL validity, login monitoring, and reviewing third-party scripts. On self-hosted sites it also covers patching software.
Mapped to the types: routine scanning and access reviews are preventive. Closing a discovered gap is corrective. Meeting a new standard is adaptive. Responding to a breach is an emergency.
This is a good example of why one work area is not one type. Security work shows up in four of the five.
Read More: Webflow hosting and security guide and how to stop Webflow form spam.
Website Maintenance and Updates
Website maintenance and updates is the category people picture first, and it is the one that has changed most in recent years.
On a self-hosted site, updates mean core software, plugins, themes, and server versions. The work is constant and carries risk, since updates that fix one thing regularly break another.
On a hosted platform, most of that disappears. The platform updates itself. What remains is updating your own content, your own custom code, and your own integrations.
Mapped to the types: scheduled updates are preventive. Fixing what an update broke is corrective. Updating to match a new browser or API is adaptive.
Performance
Speed and Core Web Vitals. Image sizes, script loading, page weight, and how the site behaves on a mid range phone rather than an office laptop.
Mapped to the types: monitoring is preventive. Fixing a page that has become unusably slow is corrective. Making a fast page faster is perfective.
See More: Core Web Vitals for Webflow and how to increase website page speed
Content
Keeping published information true. Prices, team members, case studies, statistics, dates, and product details.
Mapped to the types: scheduled reviews are preventive. Correcting something wrong is corrective. Rewriting a page to perform better is perfective.
SEO
Meta titles and descriptions, heading structure, internal links, alt text, sitemap health, and redirects.
Mapped to the types: monitoring rankings is preventive. Fixing a missing redirect is corrective. Adjusting to a search engine change is adaptive. Improving a page to outrank a competitor is perfective.
Design and user experience
Layout checks across browsers and devices, animation behavior, font loading, and accessibility.
Mapped to the types: browser checks are preventive. Fixing a broken layout is corrective. Supporting a new device size is adaptive. Redesigning a section to convert better is perfective.
Read More: Webflow accessibility guide.
Functionality
Forms, bookings, CRM connections, payments, and any custom code.
Mapped to the types: weekly form testing is preventive. Repairing a broken submission is corrective. Reconnecting after an API change is adaptive. A checkout failing on a live store is an emergency.
Functionality is the highest-stakes category, because it is where silent failure is most likely and most costly.
How the Two Systems Fit Together
Here is the same work seen both ways. Read down for work areas and across for types.
Emergency sits outside this table on purpose. It is not a planned activity in any work area. It is what happens when the other four are not being done.
Use this as a gap check. If a whole column is empty in your current plan, you have a structural problem, not a task list problem. An empty preventive column means you will keep paying for corrective work. An empty perfective column means you are paying to stand still.
Website Maintenance Responsibilities: Who Handles Each Type
Website maintenance responsibilities are usually the reason maintenance fails. Not budget, not tools. Nobody owns it, so it does not happen.
Here is a realistic split for a business with a small marketing team and an outside agency.
Three rules make this work.
Every row has a name, not a team. "Marketing" does not test forms. A person does. Tasks assigned to a group get done by nobody.
Renewals belong with whoever controls the payment. Expired domains are one of the most common causes of full site outages, and they happen because the renewal notice went to a mailbox nobody reads any more.
Emergency response needs a named contact on both sides. Knowing who to call at 9pm on a Saturday is the whole value of the arrangement.
How to Split Your Maintenance Budget Across Types
Most businesses spend their maintenance budget in roughly this shape:
- Corrective: 60 percent
- Emergency: 25 percent
- Preventive: 10 percent
- Adaptive: 5 percent
- Perfective: 0 percent
That is the most expensive possible arrangement. Almost all of it is reactive, and the reactive types are the expensive ones.
A healthier split looks closer to this:
- Preventive: 25 percent
- Perfective: 40 percent
- Corrective: 20 percent
- Adaptive: 10 percent
- Emergency: 5 percent
The total does not need to go up. The mix changes. Spending more on preventive work shrinks the corrective and emergency spend, which frees budget for preventive work. That is the shift that turns maintenance from a cost into something that returns money.
A simple way to judge your own split: look at the last six months of website invoices. If most of the lines describe something being fixed, you are in the first pattern.
Which Types Change on a Hosted Platform
Almost every guide on this topic assumes a self-hosted site with plugins. If your site runs on a hosted platform like Webflow, the balance between the types shifts.
Corrective work drops. Most faults on self-hosted sites come from update conflicts between plugins, themes, and core software. None of that exists on a hosted platform, so a large share of corrective work simply never appears.
Preventive work simplifies. No patching, no version management, and no compatibility testing after updates. What remains is testing your own forms, backups, links, and speed.
Adaptive work drops. The platform handles browser changes and infrastructure updates. What remains is your own integrations and any rule changes affecting your content.
Emergency work becomes rarer. Most emergencies on self-hosted sites start with a security hole in outdated software. Remove that and the frequency falls sharply.
Perfective work becomes the main activity. With less to defend, the budget moves to improving the site. Speed, content, conversion, and design.
This is the practical case for a hosted platform, and it is rarely made this way. It is not that maintenance disappears. It is that the mix shifts from the types that cost you money to the type that makes you money.
If you are comparing platforms on this basis, see Webflow vs WordPress.
How to Tell Which Type You Are Actually Buying
Maintenance plans rarely state which types they cover, so read them this way.
If the plan lists monitoring, backups, and updates only, you are buying preventive maintenance. Something breaking is billed separately.
If the plan is hourly with no schedule, you are buying corrective maintenance. Nobody is watching the site between the calls you make.
If the plan includes a fixed number of hours a month, ask what happens when nothing is broken. If the answer is "the hours lapse," you are paying for corrective cover. If the answer is improvements, you are buying perfective work too.
If the plan has no stated response time, it does not cover emergency maintenance, whatever the sales page says.
Three questions cut through most of this. What is your response time when the site goes down? What happens to unused hours? Who is watching the site when I have not reported a problem?
For how these differences show up in pricing, see Webflow maintenance costs and what is included.
Knowing the Type Tells You What Maintenance Will Cost
The five types are not academic. They explain why two businesses with similar websites can pay very different amounts for maintenance.
The one paying more is almost always buying corrective and emergency work, because nothing preventive is happening. The one paying less has a schedule and spends the difference on improvements instead of repairs.
If you want to change what your website costs you, start by working out which types you are currently paying for. The invoices will tell you.
theCSS Agency is a Webflow Premium Partner, trusted by 150+ companies across 15+ countries. Our Webflow maintenance service is built around preventive and perfective work rather than repairs.
Want to know which types your site needs most? Book a Call and we will walk through where the gaps are, or see our work to view the sites we look after.
FAQs
1. What are the main types of website maintenance?
There are five. Corrective fixes faults. Preventive stops them from forming. Adaptive keeps up with browsers and rules. Perfective improves speed and conversion. Emergency handles downtime and breaches.
2. What is corrective website maintenance?
Corrective maintenance is fixing something that is already broken, like a failed form, a broken link, or a layout that has collapsed on mobile.
3. What is preventive website maintenance?
Preventive maintenance is scheduled checks that stop faults from forming. It covers form testing, backup checks, link scans, speed monitoring, and access reviews.
4. What is the difference between corrective and preventive maintenance?
Corrective work happens after a fault. Preventive work happens before one. Preventive costs less per hour and reduces how much corrective work you need.
5. What is adaptive website maintenance?
Adaptive maintenance updates a site to match changes outside your control, such as new browsers, new device sizes, new privacy rules, or a third party changing its API.
6. What is perfective website maintenance?
Perfective maintenance improves a site that already works. It covers speed gains, better calls to action, refreshed content, and conversion improvements.
7. Which type of website maintenance is most important?
Preventive, because it is the only type that reduces the size of the others. Every hour spent preventing faults removes several hours of corrective and emergency work later.
8. How do website maintenance and security relate?
Security is a work area, not a type. Security work appears across four types: preventive scanning, corrective fixes, adaptive standard changes, and emergency breach response.
9. What do website maintenance and updates include?
On self-hosted sites, core software, plugins, themes, and server versions. On hosted platforms, mostly your own content, custom code, and integrations, since the platform updates itself.
10. Who is responsible for website maintenance?
Ownership should be split by task. Content accuracy usually sits with marketing. Security, speed, and code sit with an agency or developer. Renewals sit with whoever controls payment. Every task needs a named person.
