A monthly website review is useful because it gives someone responsibility for checking that the site still does its job. It is not a reason to wait a month before dealing with an urgent security issue, a failed enquiry form or a broken checkout.
For a business owner, the most useful checklist combines technical care with practical checks. You do not need to become a WordPress developer. You do need to know who handles maintenance, what they check and how your team reports a problem.
Divide the work before starting
Some tasks belong to your maintenance provider. Others require someone who understands the business.
A developer can check software and technical behaviour. They may not know that a service has closed, an enquiry is reaching a former employee or a downloadable brochure contains last year’s details.
| Area | Technical responsibility | Business responsibility |
|---|---|---|
| Backups | Confirm agreed backups and recovery arrangements | Explain which recent data the business cannot afford to lose |
| Updates | Assess and apply changes using an appropriate process | Identify important journeys to test |
| Enquiries | Check the form and agreed delivery route | Confirm the receiving team can find and act on submissions |
| Content | Maintain the agreed technical structure | Approve accurate services, people, dates and documents |
| Issues | Investigate and document technical changes | Report symptoms with useful examples |
The exact split depends on your agreement. Do not assume hosting includes development support, or that a care plan includes unlimited content changes.
1. Confirm the backup and recovery arrangement
Ask what is backed up, how often, where copies are held and who can restore them. A dashboard saying “backup completed” is not the same as a documented recovery process.
Check whether both the website files and database are covered. Also identify information outside WordPress, such as a CRM or external booking system, that needs its own arrangements.
The appropriate frequency depends on how the site changes. A relatively static brochure site and a store receiving orders throughout the day have different exposure to lost data.
Agree how recovery is tested safely, and how long restoration may take in your setup. Avoid treating a backup as a guarantee that every recent transaction can be recovered.
2. Review updates and unresolved technical issues
Your provider should have a process for assessing WordPress, theme and plugin updates. Ask how important changes are tested and what happens if something fails.
For stores, WooCommerce’s update guidance recommends backups, testing on staging and checking store behaviour. The right process for your website should reflect its actual features and risk.
A monthly review can confirm that maintenance is being carried out and unresolved issues have owners. It should not become a rule that known urgent problems are ignored until the next scheduled date.
Also review warnings about expired licences or unsupported components with your provider. Do not purchase replacement plugins just because a warning appears; first confirm what the component does and which account owns it.
3. Complete a real enquiry test
Open the site as a visitor and complete an important enquiry route using clearly labelled dummy information.
Check the on-screen confirmation, the saved entry where applicable and the agreed recipient’s ability to find the enquiry. If there is a CRM connection, check that part too.
A confirmation message alone does not prove the receiving team got the information. Conversely, a missing email does not necessarily mean the original submission was lost.
Tell the recipient a test is coming. Keep a short record of the date, route, result and any follow-up action. Do not add real customer information to a general maintenance checklist.
4. Check the pages people actually use
Choose a small set of important journeys instead of browsing every page without a purpose.
For an enquiry-led business, that might be the homepage, a key service, a project example and the contact route. For a store, include a representative product and the purchase journey using an agreed safe test method.
Check them on your phone as well as a larger screen. Look for missing images, obstructed buttons, outdated notices and links that lead to the wrong place.
Compare like with like when checking speed. One isolated score is not a diagnosis, and a fast homepage does not tell you how every dynamic page behaves.
5. Review content that can quietly become wrong
Ask your team about changes to staff, services, locations, opening hours and contact destinations.
Check important downloads separately from page copy. Updating a service description does not update a brochure linked from it.
Also review temporary content: event notices, seasonal messages, special offers and project announcements. Give each item an owner and a removal or review date when it is added.
This is a practical accuracy check, not a demand to rewrite every page each month.
6. Review access and recent changes
Confirm that people who need access have appropriate accounts, and ask the authorised administrator to review access when staff or suppliers change.
Keep a simple record of significant website changes: what changed, who approved it and whether the relevant journey was checked afterwards.
Do not assume an activity log records everything. Its coverage depends on the tools and configuration, and some changes happen outside WordPress.
Likewise, do not perform database cleanup as a routine business-owner experiment. Have the technical provider assess a specific need and protect recoverable data before making destructive changes.
Keep a short monthly record
A useful review log can be as simple as:
| Check | Result | Follow-up owner | Due date |
|---|---|---|---|
| Backup and recovery arrangement reviewed | Confirmed or action needed | Named person | Agreed date |
| Main enquiry route tested | Passed or issue found | Named person | Agreed date |
| Important pages and downloads checked | Current or correction needed | Named person | Agreed date |
| Open technical issues reviewed | Closed or next action agreed | Named person | Agreed date |
The log is valuable when it leads to action. A long checklist that nobody follows up is less useful than four meaningful checks.
If maintenance responsibilities are unclear, review our website care plans and talk to us about your current setup. The first step is agreeing what needs ongoing care and who owns it—not assuming every site needs the same package.
