Type at least 2 characters to search.

Website Maintenance Checklist: What to Do Weekly, Monthly and Yearly

Website Maintenance Checklist: What to Do Weekly, Monthly and Yearly

A website is not "done" once it launches. Plugins release security fixes, certificates expire, a payment gateway changes its API, and the contact form that worked in January quietly stops sending emails in June. None of this is dramatic. That is exactly why it gets missed.

Most website problems don't come from one big mistake. They come from neglect: an update that was never applied, a backup that was never tested, a certificate nobody was watching. This checklist sets out what to check every week, every month and every year, whether you do it yourself or hand it to someone else.

It is written with WordPress and WooCommerce sites in mind, because they are the most common, but almost every item applies to Shopify, Magento and custom-built sites too.

Why website maintenance matters

Skipping maintenance rarely causes a problem the next day. It causes problems that build up until one of them hurts. Three are especially common:

  • An outdated plugin becomes the way in. When a security fix is released, the details of the vulnerability usually become public too. Sites that never apply the fix stay exposed to a problem that already has a solution.
  • A backup that doesn't restore. Many site owners find out their backups were incomplete, corrupted or stored on the same server that failed only when they need them.
  • Something breaks quietly. A checkout step, an enquiry form or a booking widget stops working, and the site still looks fine. Nobody notices until the leads or orders stop arriving.

Regular maintenance is how you find these problems while they are still small.

Weekly website maintenance checklist

These tasks take little time, but they are the ones that most often get pushed to "later".

  • Apply core, theme and plugin updates. Read the changelog first, especially for major versions. Where you can, apply updates on a staging copy of the site before the live site, so a bad update doesn't reach your customers.
  • Check uptime and downtime alerts. Look at whether the site went down during the week and for how long. If you have no uptime monitoring at all, set it up: you should hear about downtime from an alert, not from a customer.
  • Review security scan results. If you use a security plugin or a malware scanner, actually read its reports. Warnings about changed files, new admin users or blocked login attempts are worth a look.
  • Confirm backups are being created. Don't assume the backup job is running. Check that the latest backup exists and is a sensible size. A backup that suddenly shrinks is a warning sign.
  • Glance at the site itself. Open the home page and a couple of key pages on your phone. Broken layouts after an update are often obvious within seconds.

Monthly website maintenance checklist

The monthly list goes deeper. Most of these checks catch problems that don't show up in an alert.

  • Test a restore. Restore a recent backup to a staging or test environment and check that the site actually works. This is the only way to know your backups are real backups.
  • Check SSL certificate and domain expiry dates. An expired certificate shows visitors a security warning; an expired domain takes the whole site, and often your email, offline. Both are easy to check and a very common cause of "the site suddenly broke".
  • Test your forms, checkout and booking flows. Submit the contact form, place a test order, make a test booking. Confirm the emails arrive and the data reaches wherever it should (your inbox, CRM or order system).
  • Find broken links and error pages. Look for 404 errors, especially on pages that used to get traffic or that other sites link to.
  • Check page speed on key pages. Measure the home page, your main service or product pages, and checkout. A page that has slowed down since last month usually has a cause you can find: a new plugin, a large image or a growing database.
  • Review admin users and access. Remove accounts for people who no longer need them, and check that nobody has more permissions than their work requires.

Quarterly and yearly checklist

Some tasks don't need doing often, but they matter a lot when they are skipped for years.

  • Check for end-of-life software. Older PHP versions, CMS versions and frameworks stop receiving security fixes. Once a version is end-of-life, updating plugins is no longer enough. Plan an upgrade before it becomes urgent. Our security updates service covers this for the whole server stack.
  • Remove unused plugins and themes. Deactivated plugins can still contain vulnerable code. If you don't use it, delete it.
  • Review your hosting. Check whether your hosting plan still fits your traffic, storage and performance needs, and when it renews.
  • Review your content. Update outdated pages, prices and contact details, and redirect or remove pages that no longer serve a purpose.
  • Change important passwords. Hosting, domain registrar, CMS admin and database passwords should be strong, unique and changed when people leave. Turn on two-factor login wherever it is available.
  • Review deeper performance. If the site has grown, a yearly look at the database, caching and server setup can find slowdowns that monthly checks miss. See performance optimization for ongoing work of this kind.

Backups done right

A backup is only useful if it survives the problem you need it for, and if it can be restored. Three questions tell you whether your backups are real:

  1. Where are they stored? A backup kept on the same server as the website is lost with the server. Backups should be stored somewhere separate from your web server.
  2. How long are they kept? If a site was infected two weeks ago and you only keep the last three days of backups, every copy you have is infected. Keep enough history to go back to a clean point.
  3. Has a restore been tested? Until you have restored a backup and seen the site working, you are hoping, not knowing.

As an example, this is how backups work on our website maintenance plans: backups are stored separately from your web server and kept for 30 days, so a lost or compromised server doesn't take the backups with it. Every plan includes monthly backup verification, and plans from Standard up include weekly backups. Frequency is set by how often your content changes; sites that change daily can be backed up more often, and we periodically test restores to confirm backups actually work. For larger environments, see cloud backup & disaster recovery.

What to do if your site is hacked

If you see strange redirects, spam pages, unknown admin users or a warning from Google or your host, act quickly but don't panic:

  1. Contain it. Put the site in maintenance mode if you can, and change the passwords for hosting, the CMS admin, the database and FTP/SFTP.
  2. Don't simply restore and move on. Restoring a backup without finding how the attacker got in usually means they come back the same way.
  3. Find the cause. Look for outdated plugins or themes, weak passwords, and files changed around the time the problem started.
  4. Clean or restore from a clean point. Remove the malicious code, or restore a backup from before the infection, then apply every pending update.
  5. Harden and watch. Close the way in, remove unused plugins and accounts, and keep a close eye on the site and security scans for the next few weeks.

If your site has been hacked and isn't on a maintenance plan, we also offer emergency hack cleanup. Tell us what you are seeing and we will help you get it back.

Do it yourself, or use a maintenance plan?

Doing it yourself is reasonable when the site is small, changes rarely, and someone on your team is comfortable with updates, backups and the occasional problem. The checklist above is enough to stay on top of it, as long as someone actually owns it and does it every week.

A maintenance plan makes more sense when the site earns money (orders, bookings, leads), when nobody has time to do the checks, or when a few hours of downtime would cost more than the plan. It also means someone else is watching the site when you are not: on our plans, uptime is watched by 24/7 automated alerts, so downtime is noticed even outside office hours.

Plans start from ₹5,000/month. See our Maintenance & Support Plans to compare what each plan includes.

Frequently asked questions

How often should a website be updated?

Check for core, theme and plugin updates every week, and apply security fixes as soon as you reasonably can. Test larger updates on a staging copy first.

Can I skip updates if the site is working fine?

Not safely. A working site can still be running a plugin with a publicly known vulnerability. Skipping updates also makes the eventual upgrade bigger and riskier, because many versions pile up at once.

How long should website backups be kept?

Long enough to go back to a point before a problem started, since some infections and errors are noticed only weeks later. Thirty days is a sensible minimum for most business sites, with backups stored away from the web server.

How much does website maintenance cost?

It depends on the size of the site, the platform and how much support you need. Our plans start from ₹5,000/month; the plans page shows what each one includes.

What is the most commonly missed maintenance task?

Testing restores and testing forms. Both look fine from the outside until the day they are needed, which is why they belong on the monthly checklist.

Whether you work through this checklist yourself or hand it over, the goal is the same: find small problems before they become big ones. If you would rather someone else looked after it, see our website maintenance services, including care for WordPress and WooCommerce sites.

Have a project like this in mind?

Let's talk about how NIMU Technologies can help you build it.

Start a Project