Web maintenance: what to include and how to prioritize it

Your website may continue to be published and, even so, leave problems unmet: a form that no longer reaches the correct recipient, an outdated notice, accesses that no one controls or accumulated technical changes without criteria. The question is not to add tasks by routine, but to decide what should be reviewed so that the website continues to fulfil its function.

The Web Maintenance must cover the review and care of the elements that allow your site to remain operational, safe to manage and consistent with your business. By finishing this guide you will be able to distinguish what tasks you need, which are going first and what requests should be treated as an improvement or a new development.

The elements to be included in web maintenance

The useful scope depends on how your website is built, the tools connected and who manages it. However, these elements help to convert a generic request to "keep the website" into concrete decisions.

Critical Function Review Start with what is interrupted by an important action: contact forms, budget requests, reservations, purchases, private areas or integrations with other tools.

It is not enough to check that a page loads. It defines which route is reviewed and what result it should produce. For example: a person sends a query, sees a confirmation and the computer receives the message in the agreed channel.

Technical updates with subsequent verification A website may depend on its management system, extensions, templates, libraries or third party services. Maintaining them requires evaluating the updates available and checking after that relevant functions continue to respond as expected.

The important decision is not to treat an update as an isolated action. If a modification affects the design, form or integration, a risk proportional verification should be included.

Secure & Recovery Possibility A copy is only useful if it is known what it contains, where it is kept, how often it is generated and who can access it. Maintenance should leave these conditions clear.

It is also important to define what would be done if it were necessary to recover the website: who makes the decision, which version would be used and what recent information might require revision. Actual recovery depends on the specific configuration, so it should be validated in each case.

Access and Account Management Check who has access to the web administrator, hosting, domain, forms, analytics tools, and connected services. When a person stops collaborating with the business or changes functions, their permissions must be reviewed.

The aim is not to accumulate credentials in the hands of a supplier, but to keep the account holders and the persons authorized to operate with them identified.

Reducing narrowed incidences Maintenance can include research and correction of point failures: links leading to a non-existent page, a broken visual element, a wrong notice or a form that does not complete your journey.

Here it is important to agree what is considered an incidence and what is considered an improvement. Changing the colour of a button can be a minor adjustment; redesigning the service pages or adding a new booking logic already changes the functional scope.

Update needed contents Timetables, contact details, services, legal texts provided by your managers, images or documents may require changes. Include them when they are part of the maintenance, but specify who delivers the material and who approves the publication.

Technical maintenance does not replace the commercial, legal or brand validation of a content. You must confirm that the information published is correct and authorized.

Registration of changes and pending decisions Note what has been changed prevents an incidence from recurring without context. A simple record can pick up the date, the change made, the reason, the person who approved it and any effects that need to be monitored.

This practice also allows for the separation of resolved adjustments from improvements that need definition, budget or own planning.

How to prioritize web maintenance

Not all tasks are of the same urgency. To decide the order, it classifies each matter according to its impact and dependence.

-Immediate priority: affects an essential action or prevents a relevant part of the website from working.For example, a contact path that does not receive requests or a purchase area that does not allow the process to be completed. -High priority: does not block the entire website, but introduces a clear risk of operation, management or access. Here you can enter permissions that have not been reviewed or a technical unit that needs checking. -Planned priority: improves clarity, content or experience without impeding current activity. It should be programmed so that it does not compete with a critical incidence. -Input: incorporates pages, functions, integrations, redesigns or process changes. Although desirable, it requires defining goal, scope and solution before including it in maintenance.

Before accepting a task, answer four questions:

1. What action of customers or equipment protects or improves?
2. What happens if it is postponed?
3. What access, content or external provider do you need?
4. How will you prove that it's settled?

If you can't answer them, you don't have a well-defined maintenance task yet. You have a request that needs clarification.

Example applied to a service SME

Imagine, as a hypothetical example, a company that receives requests from its website and updates its services several times a year. Its maintenance could be organized as follows:

-Immediate: check that the form delivers the queries to the correct address and that the confirmation message is displayed when you send it. -Alto: review the accesses of the people who manage the website and keep identified accounts needed to operate it. -Planned: Update texts, documents and service pages when the company delivers approved content. -Out of ordinary maintenance: Create a private area for customers, connect a management tool, or rethink the entire navigation structure.

The difference matters because the first three tasks preserve or correct what already exists. The last category changes what the website should do. Mixing both things into an ambiguous scope often makes planning and subsequent checks difficult.

What should be left out of maintenance scope

Defining exclusions avoids waiting for a comprehensive solution under a name that is too generic. Unless expressly agreed, these needs often require an independent scope:

• creation of new user sections, functionalities or paths;
• complete redesign of the visual identity or architecture of the web;
• migration of content, domains, data or platforms;
• new integrations with external tools;
• writing, photography, translation or expert advice;
• advertising campaigns, commercial strategy or continuous positioning;
• legal, fiscal or compliance decisions to be validated by a competent professional.

Leaving a task out does not mean it is not necessary. It means that you need a different conversation: what goal you pursue, what information affects, who will use it, and how the result will be checked.

The next step: turning a diffuse need into a clear scope

Good web maintenance does not mean applying an identical list to all sites. You must protect what your business already needs to attend, report or manage actions from the web; and you must separate that care from the improvements that alter the system.

If you are not clear what tasks your site needs to maintain and what are required for evolution, you can explain your web development project to AVSISTEC to assess the technical scope that would make sense to define.