What a Claude Code maintenance retainer covers, and what to ask before you sign

A Claude Code maintenance retainer should cover two kinds of upkeep. The first is the website itself: updates, fixes, broken links, redirects, forms, structured data and small changes, made with Claude Code but reviewed by a person before they ship. The second is the Claude Code setup around your site: the CLAUDE.md rules, permission settings, hooks and connections that keep the tool safe and useful, which need care because both your site and Claude Code keep changing.

It is easy for a maintenance offer to describe the first kind well and forget the second. That is a gap, because Anthropic ships Claude Code updates frequently and your site's rules drift as pages, platforms and people change. A setup that was right at handover can be out of date months later.

This guide lists what a good retainer includes, a monthly checklist you can hold any provider to, what to confirm is excluded, and the questions to ask before you sign.

Part one: site care

This is the work most people picture when they hear "maintenance." Claude Code can do much of the legwork, but each item still ends with a person checking the result.

Backups and the ability to roll back come first. Anthropic's docs say actions on remote systems, such as databases, APIs and deployments, can't be checkpointed, so git history and real backups are the safety net. For WordPress sites, our guide to WordPress backups covers the basics, and our guide to finding and fixing broken links with Claude Code shows one of these tasks step by step.

Part two: keeping the Claude Code setup current

This is the part that is easy to skip. A retainer should name it explicitly.

Project rules

Your CLAUDE.md file tells Claude Code how to build and test the site and what never to change. Anthropic's memory documentation recommends keeping each file under 200 lines and reviewing rules periodically to remove outdated or conflicting instructions. It also describes /doctor prompt-audit, which looks for problems such as references to files or commands that no longer exist and gives a report with proposed edits. Ask your provider to review the rules when your site changes and record what they changed.

Permission settings

Shared rules live in .claude/settings.json, committed to the repository. Deny rules, such as one blocking reads of .env files, should be checked whenever new secret files or folders appear. Anything a team member approved permanently for themselves lands in their personal .claude/settings.local.json, which stays out of git, so it's worth checking that the shared file still reflects the team's actual rules.

Hooks and checks

Hooks run commands automatically at set points, for example a link check after edits. When the build or tooling changes, a hook can fail silently or stop being useful. Our guide to hooks for website projects explains what to look for. If you run Claude Code checks in GitHub Actions, those workflows need the same care; see our guide to GitHub Actions website QA.

MCP connections and plugins

MCP (Model Context Protocol) servers connect Claude Code to tools such as your CMS or analytics. Anthropic's security documentation says it "does not security-audit or manage any MCP server," and its plugin docs say Anthropic doesn't review third-party marketplaces. A retainer should include a regular review of what is connected, what access each connection has, and whether it is still needed.

The Claude Code version

According to Anthropic's setup documentation, native installations update automatically in the background, while Homebrew, WinGet and Linux package-manager installs need manual updates by default. Teams can choose a stable release channel, which is typically about one week old and skips releases with major regressions. The docs also note that a newly launched model can require a newer version than the stable channel serves. Your provider should know which channel your team uses and why.

Seats and access

People join and leave. A maintenance routine should check that only current team members and current vendors have Claude seats, repository access and tool access, and that departed people's access has been removed.

A monthly maintenance checklist

Not every item needs work every month, and a small plan may cover only some of them. The point is that you know which ones your retainer includes.

Review rules still apply

Small changes are where shortcuts creep in. A two-line fix pushed straight to the live site without a branch or a check is exactly how a site-wide problem starts. On our own site, a publishing step once regenerated every post from source files and deleted edits that had been made only in the built copy; the lesson was to make edits in the source of truth. Our list of common Claude Code website mistakes has more examples. Under a retainer, ask for the same rules as a project: branches, reviewed diffs, a check that can fail, and a named approver for anything that goes live.

What to confirm is outside the retainer

Ask which of these are excluded, so there are no surprises:

• Large projects such as a redesign, a migration or a new application, which are often scoped separately.
• Writing new content, unless the plan says so.
• Claude plan or API costs, which Anthropic bills to whoever holds the account.
• Hosting, domain and third-party license fees.
• Guaranteed outcomes. No provider can honestly promise zero downtime, bug-free code or rankings.

If a request turns into a large job, it is reasonable to scope it as a separate project. Our comparison of fixed-price vs retainer Claude Code work explains when to switch.

Questions to ask before you sign

1. Which of the checklist items above does the plan include?
2. How are hours counted, and do review and reporting count toward them?
3. How will I see what was done each month?
4. Who decides priorities, and how do I request urgent work?
5. What happens to unused hours, and how is extra work approved and priced?
6. Whose Claude account and repository does the work use?
7. What is the notice period, and can I change plan levels?

How eSEOspace's maintenance plans are priced

As one published example, eSEOspace's website maintenance plans are each a fixed monthly price that includes up to a set number of hours of dedicated support: Starter at $250 per month (up to 1 hour), Essential at $750 (up to 5), Growth at $1,200 (up to 10), Advanced at $2,500 (up to 20) and Concierge at $4,000 (up to 30), as of October 2026. The pricing page describes maintenance as keeping "your site fast, secure, and online" and says clients can move up or down between tiers. eSEOspace does not publish an hourly rate. Claude plans and API usage are billed by Anthropic, separately. Ask us the questions above, as you would any provider.

Conclusion

A Claude Code maintenance retainer should keep both your site and your Claude Code setup in good order: updates, links, redirects, forms and fixes on one side; rules, permission settings, hooks, connections, versions and access on the other. Every change still goes through a branch, a review and a named approver. If you'd like ongoing care on those terms, see our website maintenance plans. More guides are in our Claude Code Guide.

Frequently asked questions