High Kite logo

Insights

What should WordPress website maintenance include?

Understand what WordPress care should cover, how often checks are needed and what to ask before paying for a maintenance plan.

Website care checklist covering backups, updates, testing and support beside a laptop.

WordPress website maintenance should cover software updates, reliable backups, security checks and testing that important features still work. It should also make clear who responds when something goes wrong, how recovery is handled and which work costs extra.

For a business website, the result matters: people should be able to enquire, book or buy, and you should have a workable way to recover if the site fails.

The right level of care depends on what your website does. A brochure site and a busy online shop have different risks, even if both run on WordPress. Here is what we would look for when reviewing a maintenance arrangement.

Hosting, maintenance and improvement are different jobs

Some providers bundle these together. Ask what each part of your agreement covers:

ResponsibilityWhat you should clarify
HostingWho runs the server, manages its software and resources, and provides certificates and hosting backups?
Website maintenanceWho manages WordPress, plugin and theme updates, checks the result, monitors problems and handles recovery?
Support and improvementsWho handles content edits, new pages, design changes, additional features and integrations, and how are these charged?

A managed host may include some website updates. That does not automatically mean someone tests your forms or booking process afterwards. Equally, fixing an update conflict may be included in one care plan and charged separately in another. Get the responsibilities in writing.

Backups you can actually restore

A usable WordPress backup needs the files and database. The database contains changing information such as posts, settings and orders; copying the images alone is not enough. WordPress’s backup guidance explains why both parts matter.

Ask where recovery copies are stored, how long they are kept, who can access them if the hosting account is unavailable, and who carries out a restore. Agree when a recovery test will be carried out on a separate staging copy.

Backup frequency should reflect the information you can afford to lose. A shop or booking site collecting records throughout the day may need more frequent protection than a daily snapshot.

Recovery also needs care. Restoring yesterday’s whole database could overwrite orders or bookings received since then. The person handling it should plan how to protect newer records before restoring anything.

Updates without unwelcome surprises

WordPress, themes and plugins need ongoing attention, including security fixes. Automatic updates can be useful; someone still needs to check failures and act on alerts.

A sensible update routine is to:

  1. Review the release notes and identify anything urgent or likely to affect key features.
  2. Confirm a recent, usable backup and a recovery route.
  3. Test significant changes on staging, especially those affecting a page builder, payments, bookings or the server’s PHP version.
  4. Apply the changes and check the live website afterwards.

Security fixes need prompt assessment. They should not sit untouched until the next routine appointment simply because that is the normal schedule. A small-looking release can be important if it fixes a vulnerability.

For online shops, WooCommerce’s update guidance covers backups, staging and the checks needed after changes. An old staging database should not simply replace the live shop when testing finishes.

Check the journeys that matter

A website can look fine while an important function has stopped working. For a service business, we would start with the enquiry route. For a booking site, we would follow a booking through to its confirmation. The checks should reflect how the business uses the website.

Agree a short list of journeys to check, including:

  • Enquiries: submit a clearly labelled test message, check the visitor’s confirmation and confirm receipt in the agreed inbox or CRM.
  • Bookings and payments: test the relevant journey on staging using the payment provider’s test environment, including confirmations. Keep customer-facing payments in their normal live configuration.
  • Search, filters and accounts: check the features visitors rely on to find information or access services.
  • Mobile use: check representative pages, menus and forms on a real phone.

When testing on a copy, route test notifications to agreed recipients so customers do not receive them. The live site also needs appropriate checks after deployment; passing a staging test does not prove the live configuration works.

Basic uptime monitoring tells you whether a page responds. More advanced monitoring can test journeys too, but someone must own the alerts and follow them up.

Our guide to websites that get visitors but no enquiries covers the enquiry journey in more detail.

Four stages of WordPress maintenance: back up, update, test key journeys and record the result.
Good website care should leave a record of what changed, what was checked and what needs attention next.

Security, access and licences

Maintenance should include a review of the less visible dependencies:

  • Supported software, security alerts and monitoring appropriate to the website.
  • Individual logins with appropriate permissions, strong passwords and two-factor authentication where supported.
  • Unused plugins, themes and accounts that can be removed once their purpose has been checked.
  • Premium licences, including who pays for them, who owns them and what happens if you change provider.
  • Domain and SSL renewals, plus the contact details used for renewal warnings.

An SSL certificate protects the connection; it does not establish that the website is free from malware. WordPress’s security guidance explains the broader responsibilities around the application and hosting environment.

Agree who investigates an alert, what incident support includes and how to report a suspected problem. No provider can eliminate every risk.

How often does WordPress need maintenance?

Maintenance is an ongoing routine, with extra checks after changes or alerts. The following is a starting point to discuss with your provider, rather than a fixed schedule for every website or a statement of High Kite’s contract terms.

WhenWhat to plan
OngoingAutomated backup and availability checks, with someone responsible for failed jobs, outages and relevant security alerts. Match backup frequency to acceptable data loss.
After updates or configuration changesCheck the affected pages and important journeys, including enquiries, bookings or checkout.
At an agreed regular reviewReview available updates, performance changes, important links and recurring errors; record completed work and unresolved issues.
At planned intervals and after significant changesTest recovery on a separate copy and review account access, licences and support responsibilities.

A quiet website still needs security attention. Conversely, a busy shop may need much closer monitoring than a site with a handful of enquiries each month. Agree actual frequencies and response arrangements around that difference.

Routine care, urgent fixes and new work

Keep the scope clear:

  • Routine care: the agreed updates, backups, monitoring and checks.
  • Urgent fixes: an outage, suspected compromise or failure affecting a key business function.
  • New work: additional pages, design changes, features and integrations.

Ask how each is handled, what support hours apply and which costs are additional. An acknowledgement time and a resolution time are different commitments.

How much should WordPress maintenance cost?

There is no single price that fits every website. A useful quote should explain how cost relates to the site’s complexity, backup and recovery needs, monitoring, testing, support availability and included work.

Compare the total cost over a year. Check whether hosting, domain renewal, premium licences, VAT where applicable, emergency work and content changes are included or charged separately. A low monthly fee is difficult to assess without that detail.

High Kite’s care and support is scoped around the website and the work required. The hosting, care and support section explains the services available; we can then discuss what your site needs.

Can you maintain a WordPress website yourself?

You can handle routine care yourself if you have the access, time and confidence to update, test and recover the site. Allow for work outside the dashboard too, including hosting changes, email delivery and renewals.

If the website takes payments, manages bookings or relies on custom integrations, consider who could investigate a fault you cannot resolve. Paying for support can make sense when the impact of a failure outweighs the time or expertise available in-house.

Questions to ask when comparing website care

Use these questions to review an existing arrangement or compare proposals:

  1. What is included, how often is it done, and who handles urgent security fixes?
  2. Where are backups kept, what history is available, and when was recovery last tested?
  3. Which customer journeys are checked, and does a form check include receipt of the message?
  4. Who controls the hosting, domain and licence accounts, and what happens if we move provider?
  5. How do we report a fault, what support hours apply, and which work costs extra?
  6. What record will show the work completed, the checks made and anything needing a decision?

A short maintenance note can be more useful than a long list of software versions. For example:

Illustrative maintenance note — not a report from a client website

Work: Updated a contact-form plugin.
Check: Submitted a labelled test enquiry and confirmed the visitor’s confirmation and delivery to the agreed inbox.
Follow-up: One optional field would benefit from clearer wording; confirm whether that change is within scope.

That gives you something concrete to discuss: what happened, whether it worked and what comes next.

How High Kite looks after WordPress websites

High Kite provides managed SiteGround cloud hosting, website care and ongoing support. Depending on the agreed scope, services can include daily backups, SSL, WordPress software updates, security and performance checks, staging facilities and technical troubleshooting.

Content changes, new pages, features, integrations and reporting can also be arranged as ongoing support. These should be agreed clearly alongside routine maintenance.

High Kite is based in Hindhead, Surrey, and works directly with businesses and organisations to understand how their website supports them. The starting point is the site you have, how it is used and what support is already in place.

Let’s talk about your website support

If your current arrangement is unclear, or nobody is looking after the site, send us your website address and tell us what it does: enquiries, bookings, sales or something else.

We can talk through what is already covered and what needs attention.