There is a fairly widespread idea that a website project ends when it is published.

The design is prepared, the features are developed, the content is added, everything is reviewed and, finally, the publish button is pressed. From that point onwards, it can seem as though the website is finished and should continue working in exactly the same way for the next few years.

But a website is not a printed brochure.

From the moment it goes live, it has to coexist with servers, browsers, content management systems, plugins, integrations, external services, devices and users that are constantly changing.

The project does not end when it is published. In reality, that is when a different stage begins.

A website keeps changing even when nobody touches it

One of the most difficult things to explain is that a website can change even when the company has not modified anything.

The text may still be the same, the design may appear unchanged and nobody may have added any new features. However, everything surrounding the website continues to evolve.

The server is updated. The PHP version changes. A new version of WordPress is released. Plugins receive fixes. Browsers change their behaviour. An external API updates its terms. A provider stops maintaining a tool. Google changes the way it interprets certain types of content.

The website may appear to be standing still, but the environment in which it operates never is.

That is why a form that had been working for years may suddenly stop sending emails. An integration that seemed stable may begin returning errors. A server update may make part of the code obsolete. A plugin may disappear or stop being compatible with the rest of the system.

It does not always happen overnight. Quite often, small issues build up until someone discovers that something important has not been working for weeks.

Maintenance is not just pressing “update”

When website maintenance is mentioned, some companies imagine someone logging into WordPress once a month and pressing a few update buttons.

For some projects, it may be that simple.

For others, updating without reviewing things beforehand can create incompatibilities, errors or even take part of the website offline.

An update may change a feature used by the project, conflict with another component or affect a custom development. It may also fix a security vulnerability that should not be left unresolved.

The work involves knowing what needs to be updated, when it should be done and which checks need to be carried out before and afterwards.

That is why staging environments, backups, error monitoring and recovery systems exist.

Updating is part of maintenance, but maintenance includes much more than that.

It also means testing forms, reviewing backups, checking available storage, monitoring errors, analysing performance, finding broken links, removing components that are no longer used and making sure that integrations are still communicating correctly.

A website can be online and still be accumulating problems.

Invisible work that is difficult to explain

From our experience, this problem often appears in projects that have been approached mainly from a design perspective.

Many agencies do excellent work in identity, communication, visual experience and brand presentation. However, not all of them have a technical team ready to support the project once it has been published.

Maintenance is then left out of the initial plan.

Not necessarily because it is considered unnecessary, but because it is work that is difficult to see, difficult to demonstrate and even more difficult to explain to the client.

A new design is visible. A new feature can be demonstrated. An update that prevents a future problem, a verified backup or a security review does not produce an obvious visual change.

When everything works, it can look as though nothing has been done.

That is precisely one of the problems with maintenance: much of its value lies in preventing situations that never end up happening.

The technical time it requires is also commonly underestimated. From the outside, updating a website may look like pressing a button. But someone has to check what is being updated, review possible incompatibilities, verify that the project still works and know what to do if something goes wrong.

When an agency does not have that technical capability, the project may be left without a clear person responsible once the initial design and development stage is complete.

The website is published, but nobody is really looking after it.

Artificial intelligence has also changed security

Artificial intelligence is helping professionals review code, detect unusual behaviour, identify vulnerabilities and respond more quickly to certain incidents.

The problem is that the same capabilities can also be used to locate exposed systems, analyse vulnerable code and automate certain types of attack.

This reduces the time between the discovery of a problem and its possible exploitation.

It does not mean that every website will inevitably suffer an attack.

It means that leaving a known vulnerability unresolved for months is becoming increasingly risky.

The tools that help us identify problems can also help others find them from the other side.

That is why maintenance should not depend on remembering the website only when something goes wrong.

Maintenance costs less than recovery

Many companies begin to appreciate maintenance after they have already experienced a problem.

A form stops working and sales enquiries are lost. A website becomes infected and starts redirecting users to fraudulent pages. A pending update becomes incompatible with the server. The project stops loading correctly and nobody knows where the latest backup is.

At that point, we are no longer talking about maintenance. We are talking about urgent recovery.

An emergency always means working with less information, less time and greater pressure.

You have to determine what happened, when it started, which parts have been affected and whether there is a clean backup to restore. In some cases, it is also necessary to check whether information has been exposed or whether users have been affected.

Preventive maintenance does not guarantee that nothing will ever happen. Absolute security does not exist, and no serious professional should promise it.

Its purpose is to reduce risks, detect problems sooner and have a recovery route prepared.

It is similar to maintaining a vehicle. Nobody waits for the engine to break down completely before checking the oil. Not because they expect an immediate failure, but because they understand that use, time and wear are part of the machine’s normal operation.

A website should be treated in much the same way.

A website also needs to evolve with the company

Maintenance should not be limited to preventing technical problems.

A company changes. New services appear, teams change, sales processes are modified and new needs arise.

A website that represented a company accurately three years ago may now be describing a reality that no longer exists.

The design may still work and the technology may be up to date, but the messaging may have become outdated. There may be new types of customers, the contact process may have changed or an important part of the business may not even appear on the website.

Maintenance also means reviewing whether the project is still fulfilling its purpose.

Sometimes a page will need to be changed, performance improved or a form adapted. At other times, it may make sense to develop a new feature, connect an internal tool or rethink an entire section.

All of this is part of the natural order of things.

When a company opens an office, a shop or any other workspace, it does not expect it to remain exactly the same for ten years. Repairs are carried out, furniture is replaced, spaces are expanded and the premises are adapted to new needs.

The initial investment gets the project started. Later investments allow it to remain useful.

The problem with leaving a project without anyone responsible

Over the years, we have received many enquiries from companies that have a website but do not really know who is looking after it.

The person who developed it is no longer available. The agency completed the project and maintenance was never agreed. The provider updates a few components, but nobody reviews the system as a whole. The hosting belongs to one company, the domain to another and the login details are spread across former employees.

Everything works until it does not.

Then the search begins for passwords, providers, backups, licences and documentation that was never prepared.

A large part of maintenance is about avoiding that situation.

Someone should know the project, have access to the systems, understand how it was built and be able to step in when necessary.

The website does not need to be changed constantly. What matters is knowing that there is a team looking after it.

The project continues after delivery

Publishing a website is an important moment, but it should not be seen as the end point.

It is the moment when the project begins receiving real visitors, collecting data, facing new situations and showing whether the decisions made are working as expected.

From that point onwards, another stage begins: observing, correcting, updating and improving.

Artificial intelligence is accelerating many processes, including the way vulnerabilities are identified. This shortens response times and makes it increasingly difficult to justify leaving older systems without supervision.

But security is only one part of the work.

A maintained website can remain compatible, continue representing the company accurately and adapt when new needs arise.

An abandoned website remains still while everything around it continues moving forward.

When was the website last properly reviewed?

I do not mean simply checking that the homepage is still online.

I mean reviewing pending updates, backups, forms, performance, integrations, access credentials and the overall condition of the project.

At Levenant, we work with websites and platforms that need continuity, technical support and the ability to keep evolving.

We can review the current state of your project, identify which areas need attention and propose a maintenance plan adapted to how it actually works.