Domains, delivery and craft
What is Website maintenance?
The recurring work that keeps a site working after launch: applying updates, verifying backups restore, monitoring uptime and certificates, checking forms still deliver, and reviewing search errors. Most site failures are silent, which is why the routine matters more than the reaction.
Also called: site upkeep · maintenance retainer
A workable monthly routine
- Apply updates on staging, test the critical paths, then deploy
- Confirm the contact form email actually arrives, by sending one
- Check Search Console for new coverage errors and manual actions
- Review uptime, certificate expiry and Core Web Vitals movement
- Scan for broken internal and external links
- Log what was done, with the date
The failures nobody notices
A contact form that stopped delivering after a host change. A certificate ten days from expiry. A plugin update that broke checkout on mobile only. None of these announce themselves, and every one is found by routine rather than by luck.
Why static sites cost less to maintain
No database, no plugin ecosystem, no PHP version to keep current. The maintenance surface reduces to dependencies, content and monitoring — which is why the ongoing cost of a static site is usually a fraction of a comparable CMS build.
Where this is covered in depth
A definition can only go so far. Who actually owns your website — a checklist you can verify today covers this properly — 3 minutes, free, no email required.
Who wrote this
Anas Bin Masud builds e-commerce sites and does technical SEO for businesses in the UK, Canada and Pakistan. These definitions come from client work rather than from a content brief — where an entry describes a mistake, it is usually one found on a real site. More about how I work.