Summarize this page with AI
Opens your chosen AI service with this public page’s link. Sign-in may be required; summaries can contain errors.
A monthly WordPress maintenance checklist should show what was checked, what changed and what still needs attention. A list of installed updates cannot establish whether an enquiry reaches its destination or whether a backup can be used. For a business website, organise the review around important journeys and the people who can authorise work.
Use the maintenance evidence log below for an existing website. It is an original planning aid for a recurring review, rather than a release acceptance worksheet for a redesign. The monthly meeting does not replace urgent action: agree separately how security notices, outages and other time-sensitive issues reach the responsible operator.
1. Establish the review boundary
Record the site, environment, review period and person responsible for decisions. List the important templates and connected systems: a service enquiry, a download, an account area or a checkout where applicable. Identify what the team can test and which services another supplier controls. A report should say when a route was excluded because access or test arrangements were unavailable.
Keep an asset and dependency record with the CMS, active theme, plugins, hosting responsibilities and relevant renewal owners. Record versions and material changes against the previous review. Do not place passwords, recovery codes or customer data in a shared maintenance report; link to the authorised access process instead.
2. Treat an update as a controlled change
WordPress’s official updating guidance recommends a backup before upgrading and checking plugin and theme compatibility. It explains that there is no single update order for every site. Ask the technical operator to review the relevant release notes and dependencies, rather than assuming an update button supplies a complete change plan.
For each proposed change, record the component, current and proposed version, reason, approval owner, test environment and recovery reference. Agree the checks before the change. Afterwards, retain the observed result and any follow-up issue. A screenshot of an updated version number supports the version record; it does not prove that a form, payment or integration still works.
3. Keep backup evidence separate from recovery evidence
The WordPress backup handbook distinguishes the database from the website files. Ask which parts of the environment the backup covers and who can recover them. A successful backup job and a tested recovery are separate observations; record both with their dates and scope.
Plan a restore check in an appropriate isolated environment with an authorised operator. Record the backup reference, environment, observed content and functionality, reviewer and unresolved limitations. Define how any later business records would be reconciled before considering a production recovery. This worksheet is not an instruction to overwrite a live database.
4. Review access and representative journeys
Ask the responsible account owner to review active users, roles and access that no longer matches the work. Record each required decision and who may approve it. Do not silently remove an account because a name is unfamiliar; establish its ownership and dependencies first. Include access to hosting and connected services where that falls within the agreed scope.
Read a representative page on a phone and desktop, then follow the important paths using approved test arrangements. Check navigation, downloads, visible form instructions and confirmation behaviour. Any live submission needs permission and a designated test destination. Record where a visual review stops short of end-to-end delivery verification.
W3C’s Easy Checks offers an initial review of issues such as headings, text resizing, keyboard use and form labels. Passing those checks is not a comprehensive accessibility evaluation. Use the findings to identify work for a deeper assessment rather than labelling the entire site accessible.
5. Use a seven-field maintenance evidence log
Create one record for each meaningful check or change. Keep seven fields together: review date and environment; item and responsible owner; expected condition; observation or proposed change; evidence reference; decision and approver; next action and due date. The evidence reference should lead to something another authorised reviewer can inspect, without exposing credentials or personal data.
A fictional example might read: monthly staging review; contact-form route owned by the website manager; a permitted test should reach the designated test inbox; confirmation displayed but receipt unverified; dated capture saved; held by the business reviewer; confirm the delivery route with the operator before closing. The open receipt check is a useful finding, not a failed lead count or a fabricated customer result.
A second fictional record might cover a backup: review date and isolated restore environment; recovery owned by the hosting operator; agreed content and journey checks should pass; selected backup restored but one download unavailable; restore reference and issue saved; held; investigate the missing file and repeat the agreed check. Keep this distinct from the backup job’s success message.
6. Close the review with decisions
Summarise four things: updates reviewed, recovery evidence, journey observations and open responsibilities. Separate completed changes from proposed work and unresolved checks. Agree who receives urgent issues and which work needs a new scope or approval. Carry each open item into the next review with its original reference, rather than deleting it when the reporting month changes.
Compare consistent measures over time where they exist, such as incidents or confirmed test failures. Keep traffic separate from qualified enquiries, and avoid attributing a short-term search movement to a particular update without evidence. The maintenance log should make decisions easier; it cannot promise uninterrupted availability, security or search growth.
Discuss the maintenance scope
Menteso’s website maintenance service describes software care, functional checks, backup responsibilities and reporting. For changes to the underlying site, see WordPress development. Bring the current site, key journeys, known issues and ownership gaps to a scoped discussion; confirm coverage, access and decision responsibilities in the proposal.
Bring these to your scoping conversation
- The business question and the decision you need to make
- Your existing information, priorities and constraints
- The scope and specialist support you want to discuss
A starting brief helps the right specialist understand your needs. Confirm the scope and professional review required for your project.
Put this guide to work.
Explore the wider business context. Bring your questions and project requirements to a focused discussion with our team.
Discuss your project → Explore services

