Website Maintenance Checklist 2026: 10 Proven Checks

Website maintenance checklist 2026: a wrench and ten checked boxes beside a browser window (TechBella Solutions)

A website is not finished when it launches. PHP versions expire, plugins develop flaws, certificates shorten, platforms change their requirements and backups quietly stop working. The last few weeks have shown how fast this can happen, from critical PHP security fixes to new WooCommerce releases and new Google Play rules.

This website maintenance checklist for 2026 pulls those lessons together into ten checks you can run every quarter. Each check links to a detailed guide with the official sources behind it. Use it as a conversation with your host, agency or in-house team, and assign an owner and a date to every line.

AreaQuarterly question
Server and platformAre PHP, WordPress, WooCommerce and plugins supported and patched?
RecoveryDo we have an off-site backup, and have we tested a restore?
Trust and speedDo certificates renew automatically, and is INP at 200 ms or less?
People and vendorsWho has access, and what do vendors do with our data?
A summary of the ten checks in this guide. Each links to a detailed article with sources.

Why a website maintenance checklist beats good intentions

Maintenance fails when nobody owns it. A website maintenance checklist turns vague worry into small tasks with names and dates. It also gives you something to compare against when an agency says the site is “taken care of”. If they cannot show you these ten items, you cannot be sure.

The ten checks

Check 1: PHP version and security fixes

Confirm which PHP version actually serves your site, and that it is supported and patched, using the dates on the php.net supported versions page. The October 2026 PHP flaws affected all web-serving installations, and PHP 8.1 and older received no regular upstream fix. WordPress recommends PHP 8.3 or greater. Read our PHP vulnerability guide and our PHP 8.5 features guide for the support dates.

Check 2: WordPress, WooCommerce and plugin updates

Keep the core, WooCommerce and plugins current, with staging tests before production. WooCommerce 11 has already shipped several security updates, as we explain in our WooCommerce 11 guide.

Check 3: Plugin risk review

Remove unused plugins and review the rest. Patchstack reported that 91% of new WordPress vulnerabilities in 2025 were in plugins, and 46% had no patch when disclosed. Our plugin security guide lists the steps.

Check 4: Backups and a restore test

Back up the database and files, keep an off-site copy that your site login cannot delete and test a restore. Follow our backup strategy guide.

Check 5: SSL certificate renewal

Public certificate lifetimes are shrinking, with a 200-day maximum since March 2026, 100 days from March 2027 and 47 days from March 2029. Make sure renewal is automatic and monitored. See our SSL certificate validity guide.

Check 6: Speed and responsiveness

Check your Core Web Vitals, including Interaction to Next Paint, where 200 milliseconds or less is good according to web.dev. Our INP guide and WooCommerce speed guide show how.

Check 7: Runtime and framework versions

If your site or app uses Node.js, TypeScript or Next.js, check each version against its support dates. Our guides cover Node.js LTS versions, TypeScript 7 and Next.js 16.

Check 8: Orders, payments and compliance

Test a live checkout and refund, check your payment plugins after every WooCommerce update and review tax settings. For the UAE, see our guides to WooCommerce VAT, UAE e-invoicing and BNPL options. If you use HPOS, confirm extension support, as in our HPOS guide.

Check 9: Accessibility and usability

Test with a keyboard and on a phone. The W3C’s WCAG 2.2 added criteria on focus visibility, target size, dragging and authentication, which we explain in our WCAG 2.2 guide.

Check 10: Access, vendors and mobile apps

Review who has admin, hosting and repository access, remove people who have left and check your vendors’ data handling, as we describe in our IT outsourcing checklist. If you have an Android app, check the Google Play target level in our Google Play guide.

What to put in a maintenance report

A report on your website maintenance checklist should be short enough that someone reads it and specific enough that it proves work was done. A useful format has six lines: the date, versions of PHP, WordPress and WooCommerce, the updates applied, the result of the latest backup and restore test, the certificate expiry date and a list of issues found with owners and dates.

Add a short note on anything unusual, such as a spike in failed logins, a plugin that became abandoned or a page that slowed down. A report that only says “everything is fine” tells you little. One that shows evidence builds trust and gives you a record when someone asks, months later, what was done and when.

A quarterly website maintenance checklist rhythm

  • Week 1: versions, updates and plugins on staging.
  • Week 2: backups, certificate, access and security review.
  • Week 3: speed, accessibility and checkout testing.
  • Week 4: fix list, report and plan for the next quarter.

Before big sales, add the steps in our White Friday readiness guide.

Maintenance for small, medium and large sites

Every website maintenance checklist should match the site, because different sites need different levels of care:

  • A simple brochure site needs monthly updates, a reliable backup, certificate monitoring and a quarterly check of forms and contact details.
  • A content site or blog adds checks for broken links, comment spam and search performance.
  • An online store needs staging tests for every update, order and payment checks, stock and tax review and extra care before sales.
  • A custom application needs dependency updates, code review, automated tests and monitoring of servers and logs.

Be honest about which group you are in. Over-maintaining a small site wastes money, and under-maintaining a store risks lost sales. The website maintenance checklist scales: each check can take ten minutes or a full day, depending on what your site does.

Signs your maintenance is not working

  • Nobody can say which PHP version the site runs on.
  • Updates are applied directly on production with no staging copy.
  • Backups exist but nobody has restored one.
  • The certificate expiry is tracked in one person’s calendar.
  • Former staff or agencies still have admin access.
  • Payments and checkout are only tested when a customer complains.

Each of these is cheap to fix today and expensive to fix after an incident. Choose the one that worries you most and fix it this week.

Questions to ask your host or agency

If someone else maintains your site, ask a few direct questions:

  1. What exactly is included each month, and what is billed extra?
  2. How do you test updates before they reach the live site?
  3. Where are backups stored, and when was a restore last tested?
  4. Who is alerted if the site or checkout stops working, and how fast do they respond?
  5. How do you handle urgent security releases outside the normal schedule?
  6. What happens to our access, data and code if we end the contract?

Clear answers show a mature service. Evasive ones are a signal to look further. Whichever route you choose, keep ownership of your domain, hosting account and backups in your own name.

How to report on it

Keep a one-page record: each check, its owner, the date it was done, what was found and what is left. If your agency produces a monthly report, compare it to this list. Gaps show you where risk hides.

Running the website maintenance checklist yourself, or with help

Small sites can run this website maintenance checklist in a few hours a quarter. Stores with orders, payments and custom code usually benefit from a partner who tests on staging and watches security notices. Our website maintenance service covers these checks, and we are happy to explain what we do and what we do not do.

Budgeting for maintenance

A website maintenance checklist is easier to follow when maintenance has a place in the budget. Think of it like servicing a vehicle: a small, regular cost that prevents a large, unplanned one. Include time for updates and testing, monitoring tools, off-site backup storage, security scanning and a reserve for the occasional urgent fix, such as a critical PHP or plugin release.

We do not quote prices here because they depend on your site, but you can ask any provider to break their offer into these lines. Comparing like with like makes it clear what you are paying for, and it exposes plans that look cheap only because they leave important tasks out.

Starting small: your first hour

If the full list feels like too much, start with five tasks that take about an hour. Check your PHP version and its support end date. Confirm that a recent backup exists and note where it is stored. Look at your certificate’s expiry date. Remove one plugin you do not use. Check who has admin access and remove anyone who should not.

Write the results in a note with today’s date. That single page is the start of your website maintenance checklist record, and next quarter you can add the other checks one at a time.

Tools that make the checklist easier

You do not need many tools to run a website maintenance checklist. An uptime monitor that tests your checkout, a certificate expiry checker, a backup plugin that emails failures, a security scanner and a shared password manager cover most needs. Add Search Console for crawl and speed reports, and a staging environment from your host. Choose tools you will actually look at, and send their alerts to at least two people so nothing depends on a single inbox.

Want these ten checks handled for you?

Our website maintenance service covers updates on staging, backups and restore tests, security monitoring and a clear quarterly report.

See website maintenance

Frequently Asked Questions

How often should I run a website maintenance checklist?

Quarterly is a good rhythm for most business sites, with security updates and backups handled continuously or monthly. Add extra checks before major sales and after any big platform change.

What is the most important maintenance task?

Keeping a tested backup and keeping PHP, the platform and plugins patched. Everything else depends on being able to recover and on closing known holes.

Do I need a maintenance agency?

Not always. Small, simple sites can be managed in-house. Stores with payments, custom code and busy seasons usually benefit from someone who tests updates and monitors security.

Share This Article:

Start a project

Having a project idea in mind?

Tell us what you are building. A few lines about your goals are enough to start.

  • What you want to achieve
  • Your current website or setup
  • Deadlines and a rough budget