Website maintenance: what happens after your website goes live

Launch day feels like the finish line. In practice it is the start of the website’s working life. A site that nobody looks after slowly gets slower, falls out of date, misses security fixes and, one day, stops working at the worst possible time.

This guide explains what actually needs to happen after a website goes live, why each job matters, and how to decide whether you, your developer or a care plan should handle it. It applies whoever built your site.

Hosting: where the website lives

Your website runs on a server somewhere, rented from a hosting company. Hosting is a recurring cost, usually paid monthly or yearly, and the quality varies a lot.

What to know:

• Who holds the hosting account. Ideally the business owns it, or has the login details, even if a developer manages it.
• When it renews. Expired hosting takes the site offline.
• What it includes. Cheap shared hosting rarely includes monitoring, tested backups or anyone who will fix the site when something breaks.
• Whether it can cope. A site that has grown, or added online booking or a shop, may need more than the starter package it launched on.

Domain and SSL: your address and padlock

Your domain name (such as yourbusiness.co.ug or yourbusiness.com) is renewed every year or few years. If it expires, your website and often your email stop working, and in the worst case someone else can register it.

SSL is what puts the padlock and “https” in the browser bar. Browsers warn visitors away from sites without it, and forms should never send personal details without it. Many SSL certificates renew automatically, but only if the setup is right; a certificate that silently fails to renew shows visitors a frightening warning page.

Check that the domain is registered in the business’s name, that renewal reminders go to an email someone reads, and that SSL renewal is automatic and monitored.

Backups: the job you only notice when it is missing

A backup is a copy of your website’s files and database stored somewhere else, so the site can be restored after a mistake, a failed update or a hack.

Good backups are:

• Regular, ideally daily for sites that take bookings, orders or enquiries.
• Off-site, stored away from the server they are copying, so one failure does not take both.
• Kept for a while, so you can go back to before a problem started.
• Tested. A backup nobody has tried to restore is a hope, not a plan.

Ask your developer or host where your backups are, how often they run and when a restore was last tested.

Updates: software ages quickly

Every website runs on software: a content management system such as WordPress, plugins and themes, a framework, a programming language and a server. All of these get updates, many of them security fixes.

Skipping updates is how most small-business websites get hacked. But updating carelessly can also break things, especially on WordPress sites with many plugins. The safe routine is: back up first, update, then check the important pages and forms still work.

Security: more than a strong password

Beyond updates, basic website security includes:

• Strong, unique passwords and two-factor sign-in where available, for the website admin, hosting, domain and email.
• Removing old accounts for staff and developers who have left.
• Fewer plugins. Each one is code you depend on; remove what you do not use.
• Protected forms, with spam protection and limits on repeated submissions.
• Keeping personal data to a minimum, and knowing where enquiries and customer details are stored.

Content: keeping the site true

An out-of-date website quietly costs you customers. An old phone number, last year’s prices, a staff member who has left or a “latest news” post from three years ago makes visitors wonder whether you are still trading.

Set a simple routine:

• Monthly: check contact details, prices, opening hours and offers.
• Quarterly: review service pages, photos and team details.
• When something changes: update the website on the same day you update your Google Business Profile and social pages.

If you cannot easily make text and photo changes yourself, agree who will and how quickly.

Monitoring: knowing before your customers do

Uptime monitoring checks your website every few minutes and sends an alert if it goes down. Without it, you often find out when a customer calls to say the site is not loading, or not at all.

Beyond uptime, it is worth checking now and then that:

• Forms still deliver. Send yourself a test enquiry each month. Forms break silently when email settings or passwords change.
• Google can see the site. Google Search Console reports indexing problems and security issues.
• The site is still fast on mobile. New photos uploaded at full size are a common cause of slowdowns.

Who should do all this?

You have three realistic options:

1. Do it yourself. Possible for content and basic checks if you are comfortable, but updates, backups and security take time and some technical skill.
2. Pay your developer per job. Fine for occasional changes, but routine work such as updates and monitoring tends to be forgotten until something breaks.
3. A care plan. A monthly arrangement where one team handles hosting, SSL, backups, updates, monitoring and agreed content changes. You know who to call, and the routine work happens without reminders.

Whichever you choose, write down who is responsible for each job above. The most common problem we see is not bad maintenance, but nobody being sure whose job it was.

Signs your website needs attention now

• The padlock is missing, or visitors see a security warning.
• You do not know who holds the domain or hosting logins.
• The site has not been updated in over a year.
• Enquiry forms have gone quiet for no obvious reason.
• The site takes a long time to load on a phone.
• Your previous developer is hard to reach.

FAQ

How often should a website be maintained?

Monitoring and backups should run continuously or daily. Software updates usually need attention at least monthly, and content checks monthly or quarterly.

Is hosting the same as maintenance?

No. Hosting keeps the site online. Maintenance covers the work around it: updates, backups, security, monitoring and content changes. Some hosting packages include part of this; many include none.

Can you look after a website you did not build?

Often, yes. We review the site first and tell you what it needs to run reliably, or whether a rebuild would cost less over time.

What does a care plan cost?

Care plan prices are listed on our pricing page. Larger systems are quoted in writing based on what needs to be monitored and supported.

Next step

Not sure what state your website is in? We will check it for free, including speed, security basics, Google visibility and whether your enquiry forms work, and send you a short report.

Get a free website audit, or read about our website hosting and maintenance care plans, with managed hosting, SSL, nightly off-site backups, uptime monitoring and updates from a Kampala team.