Skip to content
Web development4 min readOctober 16, 2026

Website maintenance: what do you pay for?

Robert MirovUpdated Oct 16, 2026

Website maintenance: what do you pay for?

Website maintenance keeps agreed functions operational and makes changes predictable. The word support is not a scope of work. An owner needs to know who detects a broken enquiry form, how data is restored and where to request a price update.

01Separate different cost categories

Hosting, domain registration, technical support and development are separate items. Paying for a server does not mean someone tests enquiries. Advertising and SEO are not automatically included either. A fictional repair business has a working homepage but stops receiving requests after an outside service changes. A homepage uptime check will miss that failure. Define the business actions that must remain operational.

02Specify work and boundaries

Agree on tasks and frequency rather than a promise to monitor everything.
TaskVerifiable outcome
FormA test enquiry reaches its recipient
BackupDate, scope and restore procedure exist
UpdateImportant functions checked afterwards
ContentIncluded editing allowance is clear
IncidentContact channel and owner assigned
New integrations and sections may need separate estimates. If support uses an hours allowance, agree how tasks and time are approved.

03Backups must be restorable

A backup preserves data for recovery. Establish whether it includes databases, files, configuration and content, where it is stored and who can access it. Its age determines how much recent work might be lost. Test restoration in a separate environment at an agreed frequency. A completed-backup notification alone is insufficient. Keep business control of hosting and domains, using the website ownership checklist.

04Response and resolution are different

Response time means when a request is taken up, not when full recovery is guaranteed. The cause may belong to a payment provider, hosting service or another dependency. Prioritise loss of all enquiries differently from a photograph replacement. Agree working hours, emergency contact and temporary workarounds. Do not assume round-the-clock coverage unless it is explicitly provided.

05Ask for an outcome-based report

A useful report lists changes, checks, findings and open tasks. A quiet month can still document planned tests. A long technical list without outcomes does not explain value to an owner. Start by testing the current form, any payments and account access. Build the support scope around actual dependencies. Search-related work is discussed separately in the SEO audit guide.

06Frequently asked questions

Is a monthly contract mandatory? There is no universal requirement. Choose by functionality, downtime impact and update frequency, while assigning responsibility. Does hosting include all maintenance? Usually it covers agreed infrastructure. Forms, integrations and content need separate clarification. Should every change be included? Only the agreed scope. New features, large sections and migrations may need separate estimates. How do I assess a backup? Check its contents, date, access and a test restore. The existence of an archive does not prove completeness.

Summary

To discuss website support with UZNEO, send your address, functions, update frequency and current issue. We can establish access, dependencies and a defined scope. A search audit can be a separate task.

Define your website support scope

Send your website or example and required tasks. UZNEO can define functions, editing and acceptance checks.