A business website can look finished while still needing regular attention behind the scenes. Forms can stop delivering, software can become outdated, integrations can fail, business information can drift out of date, and renewals can be missed. Website maintenance is the controlled process of checking those moving parts before they become avoidable problems.

Quick answer

A practical website maintenance checklist should cover updates, backups and recovery, security and account access, forms and customer journeys, performance, content accuracy, analytics, domains, hosting, licences, and third-party integrations. The exact routine depends on the platform and the website. WordPress and WooCommerce normally require more direct software maintenance, while hosted platforms such as Shopify and Wix manage more of the underlying infrastructure. The business still needs to check the parts that affect visitors, enquiries, bookings, orders, and day-to-day operations.

What does website maintenance actually mean?

Website maintenance is the recurring work needed to keep a live website accurate, functional, recoverable, and suitable for the way the business currently operates. It is broader than installing updates. A technically current website can still fail commercially if an enquiry form no longer delivers, a booking route sends people to the wrong calendar, a product is sold with outdated delivery information, or an old team member still has administrator access.

A useful maintenance routine therefore checks three things together:

Technical operation: software, integrations, hosting, errors, backups, performance, and security-related controls.
Customer journeys: navigation, forms, bookings, checkout, payments, account emails, and other actions visitors need to complete.
Business accuracy: services, products, prices, contact details, policies, opening information, staff access, and the systems connected to the website.

The objective is not to change the website constantly. It is to know what needs checking, who is responsible, what evidence confirms that it works, and when a problem has become large enough to require separate development or redesign work.

What should be checked daily, weekly, monthly, and quarterly?

The right frequency depends on how heavily the website is used and how quickly its content or integrations change. A brochure-style site with one enquiry form has fewer moving parts than an ecommerce store processing orders every day. High-volume bookings, memberships, subscriptions, feeds, or integrations may justify more frequent monitoring.

The schedule below groups routine website checks by frequency, with examples of the work involved and why each check matters.

Frequency	Useful checks	Why it matters
Daily or automated	Uptime alerts, critical error notifications, failed orders or bookings, security alerts, and backup completion where applicable	Problems affecting live transactions or availability should be visible quickly
Weekly	Forms, booking routes, checkout, software or app notices, obvious broken pages, and important content changes	Customer-facing failures and routine updates should not remain unnoticed for long
Monthly	Backups and restoration readiness, performance, key integrations, analytics, Search Console, user access, redirects, and recurring licences	A monthly review catches gradual technical and operational drift
Quarterly	Full customer journeys, stale content, policy pages, permissions, third-party tools, mobile layouts, browser checks, and unused software or apps	Broader reviews identify accumulated issues that individual updates may not reveal
Annually or at renewal	Domain, hosting, premium software, certificates where relevant, supplier access, service agreements, and recovery arrangements	Critical services should not depend on an unnoticed renewal or an account nobody controls

A checklist is most useful when each item has a named responsibility and a record of the last check. “The website is maintained” is too vague if nobody can say who checks the contact form, who can restore a backup, or who receives renewal notices.

What should happen before and after website software or platform changes?

Updates should be controlled rather than treated as a button that can always be pressed without consequence. On WordPress and WooCommerce, core software, themes, plugins, extensions, hosting software, and PHP can interact with one another. WordPress recommends keeping software current and having a usable backup available before updates. Hosted platforms such as Shopify and Wix manage more of the underlying platform updates automatically, but themes, apps, integrations, custom code, and store settings can still change how the website behaves.

Before an update or significant change

Confirm that a recent backup or rollback route exists where the platform supports it.
Read important compatibility or release notes when the change affects core functionality.
Identify the customer journeys most likely to be affected.
Use staging, a duplicate theme, preview mode, or another safe testing route where appropriate.
Avoid stacking several unrelated changes together if that would make a failure difficult to diagnose.

After the change

Open the homepage and the most important landing pages.
Test navigation, mobile layouts, and interactive components.
Submit a real test enquiry through important forms.
For booking websites, complete the booking route far enough to verify availability, confirmation, and any payment or deposit logic.
For ecommerce, test product selection, basket, checkout, payment messaging, order confirmation, and customer emails as far as the environment safely allows.
Check the website for visible errors, unexpected layout changes, or failed integrations.

Automatic updates can be useful, but they do not remove the need for monitoring. If an update happens automatically, somebody still needs a way to know whether it failed or changed an important part of the site.

How often should forms, bookings, and ecommerce journeys be tested?

Anything that directly generates an enquiry, booking, or sale deserves more attention than a low-traffic informational page. A form can look normal on screen while email delivery fails. A booking tool can remain embedded while its availability rules are wrong. A checkout can load while a payment method, delivery rule, discount, or confirmation email is misconfigured.

For service and lead-generation websites

Submit each important form using a real email address.
Confirm the enquiry reaches the correct inbox or CRM.
Check autoresponders and confirmation messages.
Verify required fields, consent wording, attachments, spam controls, and mobile usability.
Test telephone, email, map, and booking links where they are important to conversion.

For appointment and booking websites

Check appointment types, staff, locations, and availability.
Verify deposits, full payments, cancellation rules, and rescheduling.
Test reminder and confirmation messages.
Check what happens when no slot is available.
Confirm calendar or CRM integrations still exchange the correct data.

For ecommerce websites

Test product variants, stock behaviour, basket, and checkout.
Check payment methods and failed-payment messaging.
Verify shipping rules, delivery thresholds, taxes, discounts, and returns information.
Check order confirmation and fulfilment emails.
Review important apps, feeds, subscriptions, reviews, or marketplace connections.

These tests should reflect the real customer journey rather than stopping at “the page loads”.

What should a website backup and recovery check include?

A backup is useful only if it contains what would be needed to recover the website and can be restored within an acceptable timeframe. The backup arrangement varies by platform and hosting provider, so the business should understand what is actually being protected.

What is backed up: files, database, media, orders, settings, or other data?
How often are backups created?
How long are they retained?
Where are they stored?
Can an older version be restored rather than only the latest copy?
Who has permission to start a restore?
Has the recovery process ever been tested?

For a website that changes frequently, an occasional backup may not be enough. An ecommerce store, membership site, or active booking system can create new data throughout the day. Recovery planning should take account of what could be lost between backup points, not only whether a backup button exists.

Hosted platforms may provide version history, platform-level resilience, or other recovery tools, but that does not automatically mean every app, integration, externally stored file, or business process can be restored in the same way.

What security and account-access checks belong in website maintenance?

Routine maintenance cannot guarantee that a website will never experience a security problem. It can reduce avoidable risk by keeping access controlled, software current where the business is responsible for it, and suspicious changes visible.

Remove accounts that no longer need access.
Use individual accounts instead of sharing one administrator login where the platform allows it.
Use strong passwords and multi-factor authentication on important accounts.
Review administrator, developer, staff, collaborator, and agency permissions.
Check that the recovery email and telephone details belong to people who can still act.
Keep plugins, themes, extensions, and custom components supported and current where applicable.
Review unexpected new users, changed settings, redirects, or unfamiliar integrations.
Confirm that third-party suppliers have only the access they still require.

The same principle applies outside the website itself. Domain registrars, hosting, DNS, email, payment providers, analytics, advertising, CRM systems, and ecommerce platforms can all affect the site. Losing control of one of those accounts can create a website problem even when the website code has not changed.

What performance and technical checks should be included?

Performance should be reviewed over time rather than only on launch day. New scripts, apps, images, tracking tools, fonts, product widgets, and third-party embeds can gradually make a website heavier. Hosting or platform changes can also affect behaviour.

Useful recurring checks include:

Page loading on representative mobile and desktop devices.
Large images or videos added since the last review.
Console, server, application, or platform errors where access is available.
Broken links and unexpected 404 pages.
Redirects after old URLs are removed or changed.
Forms, menus, accordions, filters, sliders, and other interactive elements.
Third-party scripts that are no longer required.
Core Web Vitals and other performance evidence where it is relevant to the website.

A performance score should not become the only maintenance target. The more important question is whether the website remains fast enough, stable, accessible, and functional for the people using it.

What content and business information should be reviewed?

Maintenance includes keeping the public website aligned with the real business. Outdated content can create commercial and operational problems even when the site is technically healthy.

Services, products, prices, packages, and availability.
Contact details, locations, opening information, and service areas.
Team information and named contacts.
Delivery, returns, cancellation, booking, or membership information.
Accreditations, certifications, awards, and time-sensitive claims.
Case studies, testimonials, and proof that still reflects the current offer.
Privacy, cookie, and other legal information where the website or data processing has changed.
Copyright years and other recurring details where appropriate.

For a wider view of what the site itself should contain, see What Should a Small Business Website Include?. Maintenance should keep those essential elements accurate after launch rather than allowing them to drift.

Should analytics and Google Search Console be part of website maintenance?

They should at least be checked often enough to reveal obvious problems. Analytics and Search Console are not substitutes for maintenance, but they can expose changes that deserve investigation.

Confirm that analytics is still recording the important events or conversions.
Check that consent settings have not stopped required measurement unexpectedly.
Review sudden drops in traffic or conversion data.
Check Search Console for indexation, sitemap, crawl, or page-experience issues that are relevant to the site.
Confirm that major new pages are crawlable and important removed URLs redirect correctly.
Investigate unexpected spikes in 404s or excluded pages after migrations and content changes.

This does not turn routine maintenance into an ongoing SEO campaign. Search growth, content strategy, competitive analysis, keyword research, authority building, and sustained optimisation belong under SEO where those are the primary objectives.

Which domains, hosting, licences, and renewals should be tracked?

Some of the most disruptive website failures happen because a recurring service expires or an account is tied to a person who is no longer involved. Keep a simple register of important services and who controls them.

Domain registration and DNS
Hosting or platform subscription
Business email connected to forms or notifications
Premium themes, plugins, apps, and extensions
Booking, membership, CRM, email, or automation tools
Payment-provider and ecommerce subscriptions
Cookie, accessibility, analytics, security, or monitoring tools
Stock-image, font, or other digital licences where continued use depends on them

Record the supplier, renewal date, renewal amount where useful, payment method, account holder, recovery contact, and whether automatic renewal is enabled. The recurring cost of these services should also be considered alongside the original build price. Our guide to business website costs in the UK explains how maintenance, hosting, software, and other ongoing costs fit into the wider website budget.

Does website maintenance differ between WordPress, Shopify, and Wix?

Yes. The objective is similar, but responsibility for the underlying technology changes by platform.

WordPress and WooCommerce

WordPress gives the site more direct responsibility for its hosting environment, WordPress core, themes, plugins, extensions, backups, and compatibility. WooCommerce adds ecommerce-specific dependencies such as payment gateways, shipping extensions, checkout customisation, product data, and transactional emails. Updates should be backed by an appropriate rollback route and followed by testing of the affected customer journeys.

Shopify

Shopify includes hosting and applies its core platform updates automatically. That removes much of the server and core-software administration, but the store still needs oversight of themes, apps, custom code, domains, staff permissions, product and collection content, payments, shipping, integrations, customer emails, and checkout-related settings.

Wix

Wix also hosts the site and handles the underlying platform software and infrastructure. The business still needs to maintain its content, forms, bookings or ecommerce settings, connected apps, domain, account access, analytics, customer journeys, and any custom code or integrations used on the site.

If you are comparing ecommerce platforms partly on the level of maintenance and operational responsibility, see our Shopify vs WooCommerce guide.

Other platforms follow the same principle: first identify what the platform manages, then document what remains the responsibility of the business or its support provider. Our Website Maintenance & Support service is therefore platform-neutral and agreed after the existing website, access, integrations, and support requirements have been reviewed.

When does website work stop being routine maintenance?

Maintenance should not become an unlimited label for every website request. A support arrangement works better when routine tasks are separated from larger changes that need their own planning, testing, budget, and approval.

For a fuller comparison of recurring care and defined WordPress technical work, read Website Maintenance vs WordPress Development.

It may be a development project when:

A new feature, template, form system, integration, or technical workflow is being built.
Several technical changes need to be coordinated together.
Custom code or a significant plugin, app, or integration change is required.
A WordPress site has a defined list of technical work that is better handled as a WordPress Development project.

It may be a redesign when:

The navigation or information architecture needs restructuring.
The design system no longer works across the site.
Mobile usability or the customer journey needs broad changes.
Several pages need to be reconsidered together rather than edited individually.

In those situations, Website Redesign is normally a clearer route than trying to fit a strategic rebuild into routine support.

It may be SEO when:

The main objective is to improve organic visibility, build or refine search-led pages, develop content, analyse competitors, strengthen internal linking at scale, or measure sustained search performance. Maintenance can protect technical operation, but it does not replace an ongoing SEO programme.

Should a business maintain its own website or use a support provider?

Either can work. The deciding factor is whether the business has the access, confidence, time, and process to carry out the checks reliably.

Internal maintenance may suit a simple hosted website where one person can safely manage content, forms, subscriptions, and account access. External support becomes more useful when the site has several integrations, WordPress or WooCommerce dependencies, frequent changes, ecommerce operations, or nobody internally who can diagnose problems when a routine task goes wrong.

Before agreeing ongoing support, define:

Which tasks are included.
Which platform and third-party systems are covered.
Who controls the domain, hosting, licences, and key accounts.
How requests are submitted and prioritised.
What response expectations apply.
What is excluded or separately quoted.
What happens when a task becomes development, redesign, SEO, or third-party work.

The result should be a clear operating arrangement rather than a vague promise to “look after the website”.

Common questions about website maintenance

What should I do if my website hasn’t been maintained for several months?

Start by checking that you can access your website and the accounts used to manage it. Before making several updates, confirm that a suitable backup is available and identify any security warnings, broken features, or other urgent problems. Test the main ways customers contact, book, or buy from you, then prioritise any necessary repairs and software updates. If you suspect the website has been compromised or cannot establish whether it is safe to update, seek appropriate technical assistance before making further changes.

Can automated monitoring and updates replace regular website maintenance checks?

No. Automated checks can alert you to website downtime, failed backups, and certain software problems, but they won’t necessarily tell you whether an enquiry reaches the correct inbox, a booking system shows the right availability, or checkout calculates delivery charges correctly. Automated monitoring is useful, but it should be supported by regular tests of the parts of your website that customers rely on. The frequency of those tests depends on the website and the impact of something going wrong.

How can I tell whether my website maintenance is being carried out properly?

Ask for a clear record of the checks included in your maintenance agreement and when they were completed. Useful information might include software updates, backup checks, form or checkout testing, problems identified, and work carried out to resolve them. You should also know which issues still need attention and whether any additional work requires approval. The amount of reporting should reflect the website and the service agreed, rather than simply producing a long report every month.

Can restoring a website backup remove recent orders, bookings, or customer information?

Yes. Restoring an older backup can replace information added since that backup was taken, including orders, bookings, customer accounts, or enquiries stored on the website. Before restoring a busy website, check what information has changed, whether it can be preserved, and how it will be checked afterwards. Some connected services store information separately, so the recovery process depends on the systems involved. A backup is important, but you also need a plan for restoring the website without unnecessarily losing business information.

What happens if my domain or a paid website app expires?

An expired domain can interrupt access to your website and connected email services. A paid app, plugin, or other subscription that expires may stop receiving updates, lose certain features, or become unsupported, depending on the provider. If something has expired, check the account and renewal options with the relevant supplier, then test any affected website functions. Some services cannot be restored immediately, so it’s better to keep renewal dates, payment details, and account access up to date.

Does website maintenance include fixing every problem found during a check?

Only repairs covered by your maintenance agreement are included in the agreed fee. Routine troubleshooting and smaller fixes may be included, but substantial recovery work, replacing unsupported software, and developing new functionality often require a separate quote. Before agreeing to a maintenance service, check which repairs are covered, what counts as additional work, and how any extra charges will be approved.

What affects the cost of website maintenance?

Website maintenance prices depend on the platform, technical condition, connected systems, and amount of recurring work required. A simple hosted website may need relatively few technical checks, while a WordPress or WooCommerce website can require regular software updates, backup management, and more extensive troubleshooting. Support availability, response times, and the frequency of checks can also affect the price. Hosting, premium software, major repairs, and additional development may be charged separately. When comparing quotes, check the included tasks, service limits, and how additional work is approved.

Need ongoing website care?

Keep routine website work under a clear support arrangement.

We can review the existing website, identify the maintenance responsibilities, and agree the updates, monitoring, troubleshooting, content changes, and smaller tasks that should sit under ongoing support.

View Website Maintenance & Support

Platform responsibilities were checked against current official WordPress maintenance guidance, Shopify hosting documentation, and Wix hosting documentation. Exact platform features, plans, recovery tools, and third-party responsibilities can change, so the live setup should always be reviewed before maintenance is agreed.