WalkUp Digital
Guide

Website maintenance checklist: what to check, and how often

A schedule for keeping a website working, secure and accurate after launch: the tasks for each week, month, quarter and year, what differs on WordPress, and who should do each one.

What is website maintenance?

Website maintenance is the routine work that keeps a site working, secure, findable and accurate after launch. It has four parts: keeping the software current, keeping copies that can be restored, watching for failures, and testing what visitors actually do, such as sending an enquiry or paying for an order. Done well, it is invisible, which is why it is easy to skip.

This page is the schedule. What a maintenance agreement should contain is covered in what a website maintenance plan should include, and what makes the work larger or smaller in what changes the cost of maintaining a website.

Weekly: updates, backups and the checks that catch silent failures

Updates. Review what is available for the platform, the theme, the plugins and any libraries. Security fixes are applied within days. Other updates are tried first on a staging copy, a private duplicate of the site, and reach the live site only after passing the checks below. Note what changed, so that a fault appearing later can be traced.

Backups. A scheduled backup can stop for weeks unnoticed: a full disk, an expired key, a changed password. Check the date and size of the latest copy; one much smaller than the last means something is missing.

Forms and checkout. Send every important form and confirm that the message reaches an inbox someone reads. The thank-you message on screen is not proof: a form whose emails no longer arrive can still show it, and the fault goes unnoticed until someone wonders why enquiries have dropped. On an online shop, put a test order through checkout and check the confirmation email and the order record.

Monitoring. Uptime monitoring runs all the time and alerts a person. Each week, read what happened, including short outages that recovered by themselves: when they repeat, there is usually a cause worth finding.

Search Console. Google Search Console sends email alerts when Google identifies issues, but read the reports anyway: Page indexing, for pages that should be indexed and are not; Core Web Vitals, which is based on data from real visitors; and Security issues and Manual actions, which should both be empty. If important pages are missing from results, see why a website is not showing on Google.

Broken links. Crawl the site for links that end in an error. Google recommends fixing only the 404 errors you link to yourself or list in your sitemap, and redirecting pages that have moved; a 404 for a page removed without a replacement is not necessarily a problem.

Speed on a phone. Open the main pages on an ordinary phone over mobile data. Large new images, an extra tracking script or a new plugin are the usual reasons a fast site slows down.

Security and access. Remove the administrator accounts of people who no longer work with you, check the log for repeated failed sign-ins and unexpected file changes, and make two-step verification compulsory for every administrator. Close the month with a short written report: what was updated, tested, broken and fixed.

Quarterly: a restore test, a content review and accessibility checks

Restore a backup. Restore a recent backup to a separate address and confirm the copy works: pages open, sign-in works, forms submit, orders and files are there. A backup that has never been restored is only an assumption. Where personal data is involved, Article 32 of the GDPR lists, among the security measures to be taken as appropriate, the ability to restore the availability of and access to personal data in a timely manner after a physical or technical incident, and a process for regularly testing how well those measures work.

Content. Read the site as a customer would. Prices, opening hours, people, services and contact details age faster than design. Update or remove pages about things you no longer offer, redirecting those that had visitors or links. Do not change pages just to look recent: Google's guidance on helpful content lists changing a page's date to make it seem fresh, without substantial changes, as a warning sign.

Accessibility. Run W3C's Easy Checks on the main page templates: alternative text, page titles, headings, colour contrast, visible keyboard focus, zoom and form labels. W3C is clear that they are a first review, not proof of accessibility; the full standard is WCAG, now at version 2.2. For online shops, the European Accessibility Act (Directive (EU) 2019/882) lists e-commerce among the services it covers, so confirm whether it applies to your business.

Renewals. Keep one list of every renewal, its date and the account that pays: domain, hosting, certificate, email, paid plugins and any outside service for forms, maps or payments. Turn on automatic renewal for the domain and check the card on file. When a domain lapses, the website and its email addresses stop together. Where SSL certificates renew automatically, confirm the automation still runs; a failed renewal shows only when browsers start warning visitors.

Legal pages and cookies. Compare the privacy notice and the cookie banner with what the site actually runs today. Under Article 5(3) of the EU ePrivacy Directive, and in Greece Article 4(5) of Law 3471/2006, storing or reading information on a visitor's device, non-essential cookies included, requires consent given after clear and comprehensive information. The exceptions are storage used only to transmit a communication and what is strictly necessary to provide a service the visitor has explicitly requested. Under Article 13 of the GDPR, the information given when data is collected, usually set out in the privacy notice, must state among other things the purposes, the recipients or categories of recipients, and how long the data will be kept or the criteria used to decide.

The platform. Check the server software. Each version of PHP, the language WordPress runs on, is supported for four years, the last two with security fixes only; PHP 8.2, for example, receives them only until 31 December 2026. Replace plugins that their developers no longer maintain. Then ask whether the site still fits the business. If a redesign is due, a redesign without losing SEO starts with a map of the current addresses.

How often should a website be updated?

Update means two things. Software is updated once the new version has been checked: security fixes within days, the rest on the weekly or monthly cycle. Content changes when the business does: a new service, price, opening hours or member of staff. A site that sells what it sold last year does not need new pages just to look active.

Regular publishing helps when you have something useful to say about what your customers search for. That is a content decision with its own calendar, not a maintenance task.

Who should do each task: the owner or the provider?

A useful division: the provider is responsible for the site working, and the business for the site being true.

The provider: updates tested on staging, backups and restore tests, monitoring, security, speed, Search Console errors, broken links, accessibility fixes and the monthly report.

The business: prices, services, opening hours and every other fact on the site; decisions on the privacy notice and cookies, as the data controller; reading the report; and telling the provider when enquiries seem low, which is often the first sign of a form fault. The business should also own the accounts: domain, hosting, analytics and Search Console, which allows several owners and added users. A provider who leaves should not take the site with them.

Shared: the provider tests forms and the business confirms that messages arrive; the provider watches renewal dates and the business keeps payment details current. When a provider processes personal data on the business's behalf, for example by receiving form submissions, Article 28 of the GDPR requires that processing to be governed by a contract or other legal act. Our own product Kalimenu follows the same split: venues change their dishes and prices themselves, and we keep the platform running (how we built Kalimenu).

How long does website maintenance take?

Two questions hide here. The first is how much work a site needs each month. The checklist is the same for every site; what varies is how often each task comes up and how long its test takes. The more separate pieces of software a site runs on, the more updates arrive. The more visitors can do, such as send an enquiry, book or pay, the more has to be checked after each update. And the more often content changes or orders come in, the more often backups are needed. The number of pages matters less than any of these.

The second is how long the site is down during maintenance. With staging, hardly at all: the live site changes only once updates have passed their test. A maintenance page left up for hours suggests that updates are being tried on the live site.

WordPress maintenance: what is different

Three points are specific to WordPress. Since version 5.6, new installations update both minor and major core releases automatically by default, and since version 5.5 each plugin can be switched to automatic updates from the Plugins screen. Security fixes arrive quickly, but a major change can also reach the live site untested, so decide which updates run automatically and which wait for a test.

Each plugin is software from a different developer, with its own release schedule and its own risk of being abandoned; fewer plugins mean fewer updates and fewer conflicts. And before any update, take a backup you know how to restore, as WordPress's own documentation advises. If you are still choosing a platform, see WordPress, Wix or a custom website.

Does every website need maintenance?

For a while, nothing happens. Then, usually without warning, something does. The certificate or the domain expires, and visitors see a warning or no site at all. A form stops delivering. Someone uses a weakness in an old plugin to break in; if Google detects it, the Security issues report in Search Console lists it, and affected pages can carry a warning label in search results or a warning page in the browser. Or the server software reaches the end of its support, and the upgrade breaks code nobody kept current.

Each of these is usually harder and more expensive to put right afterwards than to prevent. That is why Website Care begins at the launch of every site we build and runs for at least twelve months. Sites we did not build join after a technical audit. Every arrangement is quoted in writing after a conversation; tell us about your site.

Questions

Frequently asked.

How often should a website be backed up?

It depends on how much you would lose between two copies: less often for a site that rarely changes, more often for one that takes orders or bookings every day. Always take one before an update, and restore one to a separate copy at least once a quarter.

Can I maintain my own website?

Partly. Content, prices and checking that enquiries arrive belong with the business itself. Updates, restore tests and security need a staging copy, server access and time to fix what breaks, so they are usually handed to a provider while the business keeps every account in its own name.

Should WordPress plugins update automatically?

Automatic updates bring security fixes quickly, which matters. The risk is an untested change reaching forms or a checkout the business depends on. A reasonable rule is that security releases apply quickly and other updates are tried on a staging copy first.

What is a staging site?

A private copy of the live website on a separate address, closed to visitors and search engines. Updates and changes are tried and checked there first, and only what passes is applied to the live site.

Does website maintenance improve Google rankings?

It removes technical problems that can stop pages being crawled, indexed or used comfortably on a phone, and that supports visibility. It does not guarantee positions, and nobody can honestly promise them.

What if an update breaks the site?

With staging, the fault appears on the copy and the live site is untouched; the update waits until the cause is found or the component is replaced. If a fault does reach the live site, the quickest way back is the backup taken just before the update. WordPress's own documentation notes that without a full backup of the site and its database made before an upgrade, rolling back successfully is close to impossible.

Start a project.

Contact the studio