Website maintenance means checking and sustaining the functions your business relies on: accessible pages, forms, integrations and content administration. A useful agreement specifies included activities and support boundaries. «Complete maintenance» without detail is difficult to evaluate.

Separate technical upkeep from content changes

Updating a platform, checking backups and resolving an error are different from writing a new page or redesigning a section. Ask for a list showing what is included and what requires a separate estimate.

Hosted platforms handle some infrastructure, but forms, external services and content still need attention. A WordPress scope may also include core, theme and plugin updates. Match the plan to the technology in use.

Check commercially important functions

A website can be technically available while losing enquiries. Test a form through to message delivery, rather than checking that the button appears. For bookings or payments, verify representative journeys and notifications.

Maintain an inventory of critical pages and actions. A service website might prioritise contact and quote forms. A store needs checks for its basket, payment and inventory updates.

Pair backups with a restoration process

Define what is backed up, how often and how long copies are retained. File backups without a database may be insufficient on some platforms. Periodically verify restoration in a safe environment.

For an active store, define acceptable data loss and how to handle orders created after the latest backup. Do not promise instant recovery unless the infrastructure and team can support it.

Apply updates with verification

Test consequential changes before or immediately after deployment, depending on urgency and architecture. Keep a change log and a recovery method. The WordPress updating documentation is a useful reference for that platform.

Review access when a collaborator leaves and use individual accounts. An inventory of services and subscription owners reduces reliance on a single person.

Define incident response

Response time is not resolution time. Specify support hours, reporting channels and priority levels. A broken enquiry form and a request to change wording do not carry the same urgency.

Maintenance reports should show what was checked, what changed and which issues remain. A record of completed work is more useful than a generic statement that everything is fine.

Frequently asked questions

How often should a site be checked?

That depends on how frequently it changes and the impact of a failure. An active store needs different controls from a rarely updated brochure site. Set the cadence around risk and volume.

Does maintenance include SEO?

It may include technical checks. Research, writing and editorial strategy are separate activities unless explicitly included.

For structural issues, read the website redesign guide. Contact Nightstar to discuss your current setup.