What a Small Business Website Maintenance Plan Should Cover

Create an inventory of the domain, hosting platform, website code or theme, connected apps, email services and analytics accounts. Record who owns each account and how the provider is allowed to access it. Keep passwords and recovery information outside ordinary project notes.

This inventory helps distinguish maintenance from third-party billing or account administration. If a subscription expires, the developer may not control the renewal. The plan should identify who receives those notices and who is authorised to approve the cost.

Choose a short list of representative customer tasks. A service business may need its enquiry form, phone link and confirmation flow checked. An online store may also need product selection, cart changes and checkout reviewed.

Record what success looks like for each task. “Form working” is too vague if the information never reaches the team. A better check identifies the successful save, the admin view and any separately configured notification. Review the journey after changes to its dependencies.

Agree which edits can be made through the content interface and which need a development review. Theme code, integrations and application updates may require a preview or test environment. The process should match the platform rather than assume every website has the same deployment tools.

Specify who approves publication and what evidence they receive. A small content correction may need a quick preview, while an altered payment or account journey needs more deliberate verification. Keep a short change log so the team can connect a later problem with the relevant release.

Ask what can be restored, what is backed up and who can perform a recovery. A source code copy is not the same as a database backup, and neither automatically guarantees that every uploaded file or external app configuration can be recovered.

Set the recovery scope with the person responsible for the platform. Review the procedure using the tools the site actually has. If the plan includes backup checks, clarify whether those checks confirm a file exists or demonstrate that the business can use it to restore the required information.

External services can change even when nobody edits the visible website. Include relevant integrations in the inventory and decide how failures will be noticed. An expired connection or changed field can interrupt a workflow without altering the homepage.

Account access should also be reviewed when team members or providers change. Keep business accounts in the organisation’s ownership and grant the access required for the agreed work. Maintenance should make the site easier to operate, not make the business dependent on one person’s private login.

A useful maintenance report separates work completed, checks performed, open issues and decisions needed from the business. It should identify affected pages or systems and explain any limitation in the checks. A list of software version numbers alone rarely tells the owner what to do next.

Before agreeing a plan, confirm:

• Which platform, pages and connected services are included?
• Which changes are covered, and which require a new scope?
• What are the agreed contact hours and response expectations?
• What recovery capabilities are actually available?
• Who owns renewals, approvals and unresolved issues?

If maintenance includes a hosting move, use the platform’s migration guidance and review the new site carefully. Google provides separate guidance for infrastructure changes without URL changes, reinforcing the need to define what kind of move is being made.