A single Astro site is easy to keep current. Thirty are not, because each one drifts at its own pace. Here’s how to keep the job small.
Know where you stand
Start with an inventory: which version each site runs, which integrations it uses, and which Node version it builds on. You can’t plan around what you can’t see.
Sort sites by risk
Not every site needs the same attention:
- Server-rendered sites come first, because more of their code is exposed.
- Sites with forms, payments or logins come next.
- Static brochure sites can follow, but don’t let them slide too far.
Set a rhythm
Pick a monthly slot for routine updates. Regular small updates go faster than an annual catch-up, and big gaps are where upgrades get expensive.
Automate the easy part
Turn on Dependabot or Renovate so patch updates arrive as pull requests. With a build check in CI, most of those become a quick review.
Standardize where it helps
The more alike your sites are, the less each update costs. Agree on a package manager, a Node version and a CI workflow. Shared components can help too, although they bring their own version to manage.
Tell customers about it
Upkeep is invisible when it goes well, which makes it hard to charge for. A short monthly report shows what was done, and that’s what Em Care reports are for.