Launching a website does not mean it needs work every week. It also does not mean it can be forgotten forever.
The maintenance it needs depends on how it is built, how often the content changes and which services are connected to it. A simple Astro website usually needs less attention than a WordPress installation with several plugins, but both still need someone to own the domain, hosting, forms and main accounts.
I would therefore not start by asking whether you need a monthly retainer. I would start with a more useful question: what could stop working, who would notice and who would be responsible for fixing it?
This article expands one of the decisions in my service business website guide. If you are still defining the whole project, the guide to professional website costs explains how maintenance also affects the initial proposal.
What website maintenance actually means
Maintenance, support and content changes are often grouped together. They are different kinds of work.
| Work | Example |
|---|---|
| Fixing a delivery bug | The agreed contact form does not send messages |
| Maintaining the existing system | Updating a dependency and checking the website afterwards |
| Providing support | Investigating an incident or recovering access |
| Updating content | Replacing copy, images, prices or team details |
| Expanding the website | Adding a page, language or integration |
The distinction matters because each type of work may have different terms. A delivery bug should not be treated in the same way as a new section requested several months later.
When a proposal only says “maintenance included”, it is missing useful information. You need to know which tasks it covers, for how long, how often they are performed and which work will be priced separately.
The minimum every website still needs
Even when the technical setup is small, several responsibilities remain after launch:
- Renewing the domain and hosting. If the domain expires, the website and related email may become unavailable.
- Keeping access details. The business should know who controls the domain, hosting, analytics and connected services.
- Testing contact routes. A page can load correctly while its form has stopped delivering messages.
- Keeping information accurate. Services, prices, opening hours, team details and legal copy can become outdated without a technical error.
- Receiving important notices. Deployment failures, billing issues and Search Console alerts need to reach somebody.
You do not need to open every dashboard each morning. You do need to avoid critical accounts depending on an unknown address or somebody who no longer works on the project.
Google describes Search Console as a way to understand how Google crawls and indexes a website and to receive notices about issues. Checking it after meaningful changes is useful; reacting to every daily fluctuation is not.
Different websites need different maintenance
Technology changes the tasks involved, but so do the size of the website and the features it uses.
A static Astro website
A static website does not have a content database or WordPress dashboard running on every visit. Removing those parts reduces the number of things that can fail and usually makes maintenance simpler.
The project still uses Astro, TypeScript, packages and integrations that continue to evolve. The official Astro documentation recommends reviewing changes and following the relevant upgrade guide for major versions.
You do not have to install each release as soon as it appears. A sensible process is to review updates, test the build and check important pages before deploying. External services still need attention too. Forms, analytics, video providers and APIs can fail while the HTML continues to load.
A WordPress website
WordPress provides a dashboard for editing and an ecosystem of plugins for common business features. That convenience adds more parts that need to work together: WordPress itself, its theme, plugins, database, users and backups.
The official WordPress update guide recommends creating a backup, checking plugin and theme compatibility and reviewing the website after updating.
Automatic updates can help, but they do not replace the review afterwards. If something fails, somebody still needs to receive the notice and restore a working version.
The decision is not that Astro is good and WordPress is bad. It is about who will edit the site and who will take ownership of its technical work. My Astro versus WordPress comparison explores that decision in more depth.
Astro connected to a CMS
An external CMS can keep a custom frontend while giving other people a dashboard for editing. It also introduces new responsibilities: users, permissions, content schemas, queries, webhooks and deployments.
A dashboard may say that content is published while the public site still shows the previous version because a deployment failed. The complete publishing journey therefore needs testing and a clear owner. My Keystatic versus Sanity guide explains how that operation changes depending on where the content is stored.
What I would review after launch
The website launch checklist covers the initial delivery. I would not repeat the entire checklist every week. Instead, I would organise reviews around three moments.
During the first few days
- Open the main pages through the final domain.
- Send a real submission through every form.
- Confirm analytics and Search Console are receiving data.
- Review routes, redirects and deployment errors.
- Separate delivery problems from new requests.
When a change is made
- Test the build or update before publishing.
- Review the changed page on mobile and desktop.
- Test any affected forms, links or integrations.
- Check metadata and redirects if a URL changes.
On a suitable recurring schedule
- Review renewals, users and recovery methods.
- Test contact routes.
- Find outdated information and broken links.
- Review meaningful hosting and Search Console notices.
- Remove services or dependencies that are no longer used.
The schedule should follow the real risk. A stable landing page may need few interventions. A shop, booking website or WordPress installation with many plugins needs closer attention. Charging for a monthly review does not make it necessary by definition, but leaving everything without an owner does not make maintenance unnecessary either.
How I maintain this website
This portfolio is built with Astro, TypeScript and MDX content. When I publish something, I check the Spanish and English routes, metadata, sitemap, social images and links. If I update dependencies or change configuration, I also run the project’s build and tests before deployment.
I do not perform every check every day. I adapt the review to the change. Correcting one sentence does not carry the same risk as changing routes, upgrading Astro or adding an analytics service.
That experience has also shown me that maintainability starts before launch. Reusable components, organised content and a clear deployment process prevent the same fix from being repeated across many pages. My guide to organising a multi-page website covers that part in more detail.
What should be agreed from the start
Before a project begins, I would put clear answers to these questions in writing:
- Who controls the domain, hosting and external accounts?
- Which delivery bugs are covered, and for how long?
- Which maintenance tasks are included?
- Who can change copy, images and pages?
- How are updates and backups handled when needed?
- How is an incident reported?
- How are new changes and features priced?
- Which access details and documentation does the client receive at handover?
Not every project needs an ongoing maintenance contract. Some work well with individual interventions. Others need recurring reviews because the website changes often or depends on more systems.
The important part is making that decision consciously. If nobody knows who renews the domain, tests the form or handles an update, the problem is not the lack of a monthly fee. It is the lack of an owner.
My web design and development service for professionals and businesses defines the scope, launch and approach to future changes before development begins.