# Monthly maintenance: why a website is never finished

# Monthly maintenance: why a website is never finished

Carlos Eduardo de Souza · 2026-10-30

A site nobody looks after gets slower, less secure and harder to find. What monthly maintenance covers, and how we run it.

A website starts ageing the day it launches. Software gets updates, browsers change, content goes stale. Monthly maintenance is how a site stays fast, secure and useful.

### What goes wrong without it

- **Security:** outdated CMS versions and plugins are the most common way into a site.
- **Search:** slow pages, broken links and old content lose ground in search engines and in AI answers.
- **Experience:** forms stop sending, pages break in new browsers, prices and contacts go out of date.
- **Recovery:** without tested backups, one attack can mean rebuilding the site from scratch.

### What we check every month

- Core, plugin and extension updates for TYPO3, WordPress and headless stacks.
- Backups, tested, at a frequency that matches how often the content changes.
- Forms, links, payments and integrations.
- Speed, accessibility and search health.

### How the hours work

 You contract a monthly block of hours and use it where it matters most: fixes, new pages, design, front-end or back-end work, SEO and GEO. The team that knows your site does the work.

 See how it works in [Coopers Evolve](/services/evolve).

> A website is not a project that ends. It is a product that keeps working, or stops.

## More from the journal

- [Journal](/blog.md)

- [Machine speed, human signature: how we use AI without losing accountability](/blog/machine-speed-human-signature.md): AI drafts a lot in our pipeline. People still decide. Here is where AI sits in each stage, and where it does not.
- [TYPO3, WordPress or headless? Choosing a CMS for a multilingual site](/blog/typo3-wordpress-or-headless.md): Three questions decide it: who edits, how many languages, and what your IT allows.
- [GEO: writing for people and for AI answers](/blog/geo-writing-for-people-and-for-ai-answers.md): Search is no longer only a list of links. What changes in content and code when answers come from AI.
- [React Native in 2026: when one code base is enough](/blog/react-native-in-2026-when-one-code-base-is-enough.md): Where cross-platform wins, and the cases where we still write native modules.
- [Verification and validation: how we check every delivery](/blog/verification-and-validation-how-we-check-every-delivery.md): Done is defined at the start. At the end, we check against it, item by item.
- [Working from Curitiba with teams in Vienna and New York](/blog/working-from-curitiba-with-teams-in-vienna-and-new-york.md): Hours that overlap, rituals that travel, and what we learned about working across time zones.
- [Our origin: from code partner for agencies to AI-first engineering](/blog/our-origin.md): Coopers started in 2013 as the team agencies called when they needed code. What we kept from those years, and what changed.
- [How we build a website, step by step](/blog/how-we-build-a-website.md): Five steps from the first question to the first weeks after launch, and what you see and approve at each one.
- [Monthly maintenance: why a website is never finished](/blog/monthly-maintenance.md): A site nobody looks after gets slower, less secure and harder to find. What monthly maintenance covers, and how we run it.

---
HTML: https://coopers.digital/blog/monthly-maintenance