Website Maintenance and Support: What Matters After Launch

After launch a website often looks finished. The domain is connected, the pages are reachable, the legal notice is in place. What is missing is ongoing responsibility: who notices if the site is down, who changes opening hours, who restores a backup if something goes wrong?

Website maintenance is more than hosting. Hosting ensures that the website remains accessible. Maintenance, content care and support describe what actually happens afterwards.

Website maintenance is more than keeping the site online

Availability initially means only that the website can be accessed. It says nothing about whether a form still works, a certificate is renewed on time or recently changed prices are still correct.

The work differs sharply by technology. A lean, code-based setup needs different checks than a system with many plugins, themes and automatic updates. That is why the blanket claim “every website needs weekly updates” is useless.

Almost every website needs clear responsibilities: who notices outages, who updates content and who is responsible for restoring the site?

Maintenance, content care and support: three terms that get mixed up

In everyday use these words are often treated as the same thing. Each one refers to a different part of the work after launch.

Maintenance keeps the website technically usable. That includes dependency updates, security fixes, publishing new versions and keeping the site reachable.

Content care keeps the information on the website current: opening hours, prices, images, text and contact details.

Support means one party handles both within the agreed scope. Hosting only provides storage and reachability. It does not settle who updates the content, who fixes technical problems and who restores the website if something fails.

Technical operations: availability, SSL and deployment

In practice it matters that the site stays reachable, that the connection is encrypted and that a change can go live in a traceable way.

SSL is not an optional extra. Without a valid certificate, visitors see warnings, forms appear insecure and trust in the website suffers.

Deployment means having a defined process for publishing a checked version of the website. For code-based websites, this also includes traceable version control. Anyone who only edits on the live system later finds it hard to say what changed when.

Security and dependencies follow the website stack

A CMS with plugins creates different maintenance work than a leaner custom or static setup. Every extra dependency is a possible update, compatibility or security task.

That is not a reason to dismiss one system across the board. It is a reason to keep the stack deliberately small when the website allows it. The existing article Maintenance and security: lean websites cost less explains this relationship in more detail.

Describing a website as unhackable is not a credible claim. A well-maintained system reduces risks. It does not eliminate them entirely.

Backups and restore are not the same thing

A backup that cannot be restored when needed is ultimately just a file. NIST and the BSI therefore distinguish between backup and recovery: it must be clear what is backed up, how often backups are created, where the copy is stored and how it can be restored when needed.

On code-based websites, versions and deployments can help as well. They do not replace backups of content, uploads or configuration that live outside the code.

Velvionix describes only the scope of its own offer here: operation and agreed backups for websites created by Velvionix, not a general backup product for arbitrary third-party systems.

Small content changes are their own part of ongoing support

After launch, opening hours, phone numbers, prices, text and images change. Small layout corrections often belong there too.

That is not a new website. It is ordinary work. If nobody takes those changes, the page ages in public even though hosting keeps running.

The boundary is clear: new pages, new features and substantial copy or design work are a separate project. They do not fall under “small maintenance”.

Monitoring and quality control

It must be detected when the website is no longer accessible or when a deployment causes visible errors. That does not need a 24/7 security operations centre or an invented SLA paragraph.

For small business websites, a regular and clearly defined review is often sufficient: availability, obvious errors after changes and verification that the published version still matches the most recently approved version.

Velvionix does not promise monitoring beyond the agreed care scope. What is included is on the service page.

What maintenance costs depends on the system and the scope

A system with many moving parts requires more attention than a lean system. Frequent content changes cost more than a page that is updated three times a year.

For websites Velvionix built, care and hosting start at 39 EUR net per month, with a 12-month minimum term and annual billing in advance. This is not a separately bookable webspace service or a general maintenance service for third-party systems.

Details on scope, term and limits are on care and hosting and website pricing.

Which support fits which case?

A small business website with infrequent changes primarily needs stable operation, reliable backups and occasional content updates.

A website with frequent changes also needs a clearly defined process for text updates, images and small corrections.

An existing third-party CMS is not a general maintenance job at Velvionix. If the foundation is no longer viable, a new website build is often cleaner than endless repair of the old system.

With a newly planned Velvionix website, operation and agreed small changes can be considered from the outset instead of being left as an afterthought after launch.

Frequently asked questions