A website is not finished on launch day. This guide lists the tasks that maintenance covers, how often each one needs doing, and why one plan costs more than another.
Website maintenance is the routine work that keeps a site secure, working and current after launch. It usually covers software updates, backups, security checks, uptime and renewal monitoring, form and link testing, speed checks and small content fixes. The cost depends on the platform, the number of plugins and integrations, how often content changes, how fast problems must be fixed, and who supplies the hosting.
What website maintenance means
Website maintenance is the recurring work that keeps a live site secure, working and accurate after launch. The build is finished on launch day, but the software it runs on, the hosting underneath it and the business it describes all keep changing. Maintenance is how the site keeps up with them.
It is separate from adding features or changing the design. Maintenance keeps the site you have in good order. A new layout, a booking system or a rewrite is a project, and the guide to website maintenance versus redesign explains where the line falls. The website launch checklist covers the day a site goes live. Maintenance covers every month after it.
What website maintenance includes
Plans use different wording, but the work falls into the same groups. Use this list to check that a quote, or your own routine, leaves nothing out.
Software updates
A site on a content management system such as WordPress runs on several layers of software: the core system, the theme, the plugins and the version of PHP on the server. Each layer gets security and bug-fix releases. Weaknesses in old versions are published, so out-of-date software is an easy way into a site. Updating is not a button to click on a busy shop, because an update can break a plugin or a layout. On a site that takes orders, updates are best tried on a copy first and followed by a test order.
Backups
A backup is a full copy of the files and the database, stored somewhere other than the hosting account it protects. The step people skip is the restore. A backup that has never been restored is an assumption, so a good routine includes an occasional test restore on a spare copy.
Security
This covers malware scans, protection on the login page, removing admin accounts that nobody uses, strong passwords with a second login step where the platform offers one, and a valid SSL certificate so browsers do not warn visitors. Most of it is routine. The work that matters starts when something is found, so ask who cleans up and how quickly they respond.
Monitoring and renewals
An uptime monitor checks the site every few minutes and sends an alert if it stops responding. Renewals cause the dullest and most avoidable outages. The domain name, the hosting plan, the SSL certificate and any paid plugin licences all expire on dates that somebody has to track. A lapsed domain is the most serious, because it can take the site and any email on that domain offline with it.
Testing forms, links and key journeys
Contact forms, enquiry buttons, checkout, booking and the WhatsApp link are the parts that turn visits into business, and they fail quietly. Nobody sees an error. Enquiries simply stop arriving. Maintenance includes sending a test through each form and following each important path from the homepage to the end. A link checker finds broken pages and links that point to pages you have removed.
Speed and mobile checks
Sites get slower over time as images, plugins and scripts are added. A regular test on a phone shows when that is happening. The guide to checking and improving website speed explains the tests and the usual fixes.
Search health
Google Search Console reports pages that cannot be indexed, crawl errors and mobile problems. A monthly look catches a leftover noindex setting or a page that now returns an error. If the reports show a pattern you cannot explain, the signs listed in when a website needs a technical SEO audit are worth reading.
Content updates and small fixes
Opening hours, team members, offers, expired events, the year in the footer and the phone number in the header all go out of date. Some plans include a set amount of content editing. Others treat every edit as a separate request. Clarify this early.
Reporting
A short note each month saying what was updated, what was found and what needs a decision gives you a record. It also tells you whether the plan is worth keeping.
How often each task needs doing
There is no universal schedule. A shop that takes orders every hour needs more care than a five-page brochure site. The rhythm below is a reasonable starting point. Adjust it to how often your site changes and how much a day of downtime would cost you.
| Task | Sensible rhythm | Reason |
|---|---|---|
| Uptime monitoring | Continuous and automatic | You hear about an outage from an alert, not from a customer |
| Backups | Daily for shops and booking sites. Weekly, or after each change, for brochure sites | A backup should never be much older than your last order or edit |
| Software updates | Checked weekly, with security fixes applied sooner | Old versions have known weaknesses |
| Form, checkout and link tests | Monthly, and after any update | Quiet failures cost enquiries |
| Search Console and speed review | Monthly | Trends show up before they become problems |
| User accounts and permissions | Every quarter | Former staff and old agencies should not keep access |
| Test restore from a backup | Once or twice a year | Proves the backup works |
| Domain, hosting and SSL renewals | Yearly, with a reminder a month ahead | Prevents a lapse |
| Content review | Every quarter, and whenever the business changes | Keeps prices, hours and offers true |
To answer the common question directly: page content should change whenever your business changes. The software underneath needs a look every week or two, whether or not you touch the pages.
What affects the cost of website maintenance
Maintenance cost is set by how much work the site creates and how quickly someone must act when something goes wrong. These are the factors that move it. None of them is a fixed price, so a fair quote names which ones apply to your site.
- The platform. A small static site has few parts to update. A site on a content management system with many plugins has more parts, and each one can break after an update.
- Integrations and custom code. Payment gateways, booking tools, CRM links and WhatsApp connections need testing after changes, and someone has to understand how they work.
- The type of site. A shop or booking site loses money when it is down, so it needs closer monitoring, more frequent backups and a checkout test after every change. A brochure site can run on a lighter routine.
- How often content changes. Regular edits take hours. Some plans fold them in and others charge for them separately.
- Response expectations. Fixing a problem within hours takes planning and availability. Fixing it within a few working days takes less.
- The state of the site on day one. A site that has not been updated for a long time needs catch-up work before routine care can start, and updating many skipped versions at once can break things.
- Who built it and how well it is documented. A developer who did not build the site has to learn it first. Clean code and clear handover notes keep that short.
- Hosting. Managed hosting often includes backups, security scans and server updates. On basic hosting those jobs fall to whoever maintains the site.
- Third-party costs. Hosting, domain renewals and premium plugin or theme licences are paid to other companies and are usually separate from the maintainer's own fee. Check whether a quote includes them.
Plans are usually priced as a monthly retainer, a block of hours or a payment per task. A retainer gives a predictable cost and routine checks. A block of hours suits a site that needs occasional changes. Pay per task suits a very small site that rarely changes, but nobody looks at the site unless you ask, so problems are found late.
What to ask before you agree to a plan
Two plans with the same name can cover very different amounts of work. Put the same questions to each provider.
- Which tasks are included, and which are excluded or charged separately?
- Who holds the admin logins for the domain, the hosting and the site? You should hold them, or at least have a copy.
- Where are backups stored, how often are they taken and when was a restore last tested?
- How do I report an urgent problem, and what response is agreed in writing?
- Are updates tried on a copy of the site before they go live?
- How many content changes are included each month?
- What report will I receive, and how often?
- How do I end the plan, and do I keep everything?
If you want a developer's view of what your site needs, the website development page explains what Liftup builds and how to start a conversation.
What you can do yourself
Many owners look after part of their site, and that is reasonable. What suits you depends on the platform. On a hosted website builder, the provider handles the server and software updates, so your tasks are content, renewals and form tests. A WordPress site on its own hosting needs more.
Tasks that most owners can do safely include editing text and photos, checking that forms deliver, removing old user accounts, putting renewal dates in a calendar, confirming that backups exist and running a speed test on a phone. Tasks better left to a developer include updating a live shop, changing the PHP version, restoring from a backup, cleaning a hacked site and anything that touches payment code. The reason is not secrecy. A mistake in these areas can take the site down, and recovery is harder than prevention.
What happens if you skip website maintenance
Nothing happens at first, which is why maintenance gets skipped. The problems build slowly and then arrive together.
- An old plugin is used to break into the site, and visitors or Google see spam pages or a warning.
- The host changes the server version, a plugin stops working and nobody is watching.
- The contact form stops sending mail, and enquiries disappear without an error.
- The SSL certificate expires and browsers put a security warning in front of the site.
- The domain lapses and the site goes offline, along with any email on that domain.
- The site breaks or is hacked and the last good backup is months old, or does not exist.
- Pages slow down, and prices, hours and offers drift out of date. Visitors notice before you do.
Catching up later costs more than steady care, because updating many versions at once breaks more than updating one at a time. Use the list to rank the work. Renewals, backups, updates and form tests come first.
Does a small brochure site need maintenance?
Yes, in a lighter form. A five-page site has fewer parts that can go wrong, but the domain still expires, the certificate still renews, forms still break and the business details still change. A basic routine is a calendar reminder for each renewal, one backup you know how to restore, a monthly form test and a content check twice a year. If the site runs on a platform with plugins, add a weekly update check.
Keep one maintenance record that you own
Whoever looks after the site, keep a single document in your own hands. Write down the domain registrar and expiry date, the hosting provider, plan and renewal date, who has admin access, the platform and its version, the list of plugins and paid licences, where backups are stored and the date of the last restore test, where each form sends its messages, and the date of the last speed and Search Console check.
The record costs nothing to keep. It is the first thing a new developer asks for, and it protects you if the person who built the site leaves or becomes hard to reach.
Questions and answers
What does website maintenance include?
It includes software updates for the platform, theme and plugins, backups, security scans, uptime and renewal monitoring, testing of forms and links, speed and mobile checks, Search Console review, and small content fixes. Plans differ in which of these they cover, so ask for the list in writing.
How often should a business website be updated?
Update the content whenever your business changes, such as new prices, hours or services. Check the software underneath every week or two and apply security fixes sooner. Test forms and links monthly, and review the whole site for accuracy every quarter.
What affects the cost of website maintenance?
The main factors are the platform, the number of plugins and integrations, whether the site takes orders or bookings, how often the content changes, how fast problems must be fixed, the condition of the site on day one and the hosting setup. Third-party costs such as hosting and plugin licences are usually separate. Ask a provider which of these apply to your site.
Can I maintain my website myself?
Partly, yes. Most owners can edit content, check forms, remove old accounts, track renewals and run speed tests. Updating a live shop, changing server settings, restoring backups and cleaning a hacked site are better left to a developer, because mistakes there can take the site down.
What happens if I skip website maintenance?
Nothing at first, then problems arrive together. Old software becomes a way in for attackers, forms stop sending enquiries without any error, and certificates or domains lapse. Catching up after a long gap is harder than steady care, because updating many versions at once breaks more.
Does a small brochure site need maintenance?
Yes, but a lighter routine is enough. Keep track of the domain, hosting and SSL renewals, keep one backup you know how to restore, test the contact form monthly and check the content twice a year. Add an update check if the site uses a platform with plugins.