A website maintenance checklist helps you catch small problems before they become part of a customer's day. A site can stay online while its form stops reaching you or its opening hours become wrong. Checking only the homepage is not enough.
Start with a short routine you can keep. The schedule below is a starting point, not a rule for every business. Check more often when your site changes often or a failed task would cause serious trouble.
The short answer
- Agree who owns content, platform care, account access and recovery.
- Check the full enquiry route after important edits and on a regular schedule.
- A backup file must cover the data you need and be restorable.
How this guide was made
This routine draws on NCSC backup and device advice plus Google Search Console guidance. The schedule and restore worksheet are original planning aids. No restore test was run, and a host's duties depend on its service terms.
Sources checked .
Name who owns each job
Get the split of work in writing and add an urgent contact route plus a backup person. Keep passwords out of the sheet and share account access through a secure method.
The business owner
Confirm facts, offers, prices and hours. Name who reads enquiries, approves content and pays renewals. These jobs still need an owner when a supplier handles the site.
The platform or host
Ask which software, uptime checks and backups the plan covers. Ask what is excluded, what it can restore and how you request help. The word managed is not a list of duties.
The technical maintainer
Agree who checks custom code, outside tools and problems after an update. The maintainer should know the recovery steps and say which issue needs another provider.
Check the contact path often
Use this schedule as a starting routine. Adjust it to the value of the task and how often your site changes. A busy booking service may need more frequent checks than a simple information page.
Send a labeled test inquiry using details you control. Confirm the result on the page, the saved record if there is one and the place where staff read it. Check that someone can reply to the test address.
Look at your key business facts while you are there. Are services, prices and hours still right? Can visitors tell where you work? Update an old offer when it ends rather than waiting for a monthly review.
| When | Suggested check | Evidence to keep |
|---|---|---|
| After a material edit | Repeat the affected task | Changed page and result |
| Each week | Send a marked enquiry | Visitor result and staff record |
| Each month | Review key pages and search messages | Issue list with owners |
| Before renewal | Confirm cost, date and account contact | Private renewal record |
| When a core task fails | Contact its owner and start an incident log | Failure time and recovery evidence |
Review important pages each month
Open your homepage, main service pages and contact page on a phone. Read the headings and tap the main links. Look for missing images, old staff details and pages that no longer match the business.
Google's Search Console introduction explains how the service reports search and indexing information. Review messages and useful reports after changes and as part of your regular care. A page that is online is not automatically indexed.
Use what you find to choose a small set of actions. You do not have to redesign the site every month. Fix the broken link, clarify the confusing sentence or update the changed service. Keep each task specific.
Source for this section: [3] Google introduction to Search Console
Look after software and account access
Keep the site and the devices used to manage it within their support period. Agree which updates your host handles and which need a separate maintainer.
Supported software
The NCSC device guide covers updates for computers and phones, including devices used to administer a site. It is not a complete server security checklist. Ask how website security updates are handled and check the main tasks after changes.
Source for this section: [1] NCSC guidance on protecting devices
Access when people leave
When staff or suppliers leave, review their account access through your normal process. Transfer needed ownership before removing access so the business is not locked out.
Recovery details
Check that the recovery email and phone still belong to the right person or business. Name who can help when the main owner is away. Keep recovery codes out of public task sheets.
Know what a backup can restore
A backup is a protected copy you can use to recover important data. Ask what is included, how recent copies are and who can restore them. A copy of page text may not include customer inquiries, images or settings.
The National Cyber Security Centre recommends protecting backups and checking the data you need is included. Its guidance also stresses knowing how to restore data. Your website provider's exact coverage still needs a separate check.
A file named backup is not proof that recovery works. Arrange a safe restore check with the person who manages the site. Use a separate test area where possible so you do not replace the live site while learning the process.
Source for this section: [2] NCSC guidance on backing up data
Plan one safe restore drill
This worksheet is for a fictional consultant. Results remain Pending until the drill is performed. Use a separate safe area so the exercise does not replace the live site.
Ask how many hours of new enquiries the business could afford to lose. The answer helps choose a backup routine that fits your needs.
Have the technical owner prevent the test copy from sending live emails, taking payments or triggering customer actions before restoring data into it. Use only the access and records needed for the drill.
| Item to agree | Planning entry |
|---|---|
| Backup date | Record exact date and time |
| Content coverage | Confirm pages, images and settings |
| Business records | Confirm whether enquiries are included or saved elsewhere |
| Restore area | Separate test site with proper access controls |
| Operator | Named technical provider |
| Acceptable data loss | Business owner to decide |
| Completion evidence | Pending, inspect restored pages and agreed records |
Use a maintenance log
This fictional solo consultant has planned four checks. They are marked Pending because the example does not claim anyone completed them. Replace the roles with real names and add the date and evidence after each check.
- Record the date and page or account checked.
- Describe the issue in plain words.
- Give the next action to one person.
- Add the result when the fix has been checked.
| Task | Owner | Evidence to save | Status |
|---|---|---|---|
| Test a new inquiry | Business owner | Where the test request arrived | Pending |
| Check the service price | Service owner | Page and confirmed current price | Pending |
| Review domain renewal | Account owner | Renewal date and valid contact | Pending |
| Confirm restore process | Technical provider | Coverage and safe test plan | Pending |
Watch renewals and urgent problems
Check domain renewals, hosting billing and key account contacts before they are due. Know who owns certificate care if your host does not handle it. Put reminders where the responsible person will see them.
Do not wait for the next review when the site is down, inquiries are missing or account activity looks suspicious. Contact the responsible provider and keep a record of what changed. Use the recovery plan you agreed on.
This checklist is a care routine, not a full security audit. Its value comes from clear ownership and real checks. Keep it short enough to use, and add tasks when your site's needs change.
Keep an incident note
When a core task fails, record what you know before making several changes. Preserve useful logs and keep customer details out of public notes.
- Time first noticed and person who reported it.
- Exact page and task that failed.
- Last known working result and recent changes.
- Person assigned to investigate and contact route.
- Recovery action, evidence of success and time checked.
Sources and further reading
Numbered links beside each section point to the source used there. Our examples and checklists are guidance from SnapRebuild. They are not claims of test results. Product details can change.
SnapRebuild sells a website building service. These guides are published under our editorial team name and use AI for research and writing. This is not a claim of independent expert review. Read how we make and update our content. Found an error? Tell us.
Ready for a fresh start?
Bring your website or your business idea. Explore a SnapRebuild preview and decide what comes next.
Try your free preview