WEBSITE CARE
Website Maintenance Checklist for Small Businesses
Use this website maintenance checklist to keep business information, enquiries and essential features working after launch. Assign an owner to each task so small problems do not become permanent ones.
What should you check during a regular website review?
Begin with the actions customers rely on: finding accurate information, opening useful pages and completing an enquiry or order. A maintenance review should follow those journeys from start to finish, including the confirmation a visitor receives.
For a service business, open the homepage, a service page and the contact route on a phone. Check the displayed offer, working hours if published, phone and email links, downloads and any recent changes. Submit a clearly identified test enquiry through a channel you control and verify whether it arrives; seeing a success message alone does not establish delivery.
Keep a short issue log with the affected URL, expected result, actual result and person responsible. This makes a support request much easier to act on than “the website is not working.”
How often should different maintenance tasks happen?
The right schedule depends on how often the site changes and how much the business relies on it. Use the following cadence as a starting plan, then adjust it for your platform, traffic and support agreement.
| When | What to review | What to record |
|---|---|---|
| After a change | Affected pages, navigation and enquiry or checkout flow | Change made, checks completed and rollback route |
| Regularly | Current offers, broken links, received enquiries and reported errors | Issues, owner and next action |
| Before renewals or major updates | Domain, hosting, paid tools, backups and access | Renewal date, account owner and recovery plan |
How should you handle updates and backups?
Identify what powers your website before deciding which updates apply. A static website, a CMS and a store have different maintenance needs, so the plan should name the components your project actually uses.
For WordPress sites, the official updating guide recommends backing up before an upgrade so the site can be restored if something goes wrong. Decide who maintains the backup, what it contains and how restoration is checked; having a file labelled “backup” is less useful than knowing it can be used.
For any platform, document who controls the domain, hosting, code and connected services. Give technical partners the access needed for their role, and review that access when responsibilities change.
What belongs in a website maintenance agreement?
A useful agreement states which tasks are covered, who handles them and how requests are prioritised. It should also separate recurring care from new features, redesign work and third-party charges.
Ask about the supported platform, content changes, deployment responsibilities, backup arrangements and the process for urgent problems. Any response targets should be written into the actual agreement rather than assumed from the phrase “ongoing support.”
FoxRanger manages website development, maintenance and technical work for Brosip and BuzzClub. Those are the kinds of continuing responsibilities covered by our website maintenance services; a new project’s scope is assessed individually.
What should you send when asking for maintenance help?
Share the website URL, platform if known, the task you need help with and a description of the problem. Add a screenshot or exact error message when it helps explain what happened, without including passwords or private customer records.
If the issue is part of a larger rebuild, read our website redesign SEO checklist. You can also prepare a technical-support brief to organise your requirements before sharing them.