WordPress & Support4 min read

WordPress Maintenance Checklist for Agencies

A practical weekly, monthly and quarterly maintenance checklist for agencies responsible for client WordPress websites.

A practical weekly, monthly and quarterly maintenance checklist for agencies responsible for client WordPress websites.

Start with an inventory and ownership record

A maintenance checklist only works when the team knows what it covers. Keep a current list of client sites, hosting, domain renewal dates, critical plugins, forms, integrations, backup location, responsible owner and agreed maintenance window. Record which sites are business-critical and which require special approval before changes.

The inventory should not become a document that nobody updates. Connect it to the work process where possible and review it when a site changes hands, launches a new feature or adds an integration. Store access details securely rather than placing passwords in the checklist.

  • Site owner and business contact
  • Hosting and domain renewal details
  • WordPress, PHP, theme and plugin versions
  • Backup and restore instructions
  • Critical journeys and integration dependencies

Weekly checks

Weekly checks focus on signs that something has broken or is becoming risky. Review uptime alerts, security warnings, failed backups, form submissions, checkout issues and any update that needs attention. The exact frequency should reflect site traffic and business impact.

For a store or lead-generation site, test the journey that creates revenue or enquiries. A homepage loading successfully does not prove that the contact form, payment flow or email notification works. Keep the check short enough to repeat and record any failure with a clear owner.

  • Review availability and monitoring alerts.
  • Check failed backups and unresolved incidents.
  • Test the main enquiry, login or checkout flow.
  • Review updates waiting for approval or testing.

Monthly maintenance

Monthly work can include applying tested updates, reviewing administrator accounts, checking storage and database growth, reviewing security scans and verifying that backups can be restored. Updates should be staged for higher-risk sites and followed by checks that confirm the site still works.

Do not treat the update button as the maintenance plan. Review compatibility notes, remove unused plugins where safe, check the current PHP support position and record any exception. If a site cannot be updated, document the risk and the plan rather than silently leaving it behind.

  • Update WordPress core, plugins and themes after appropriate checks.
  • Review administrator access and remove accounts no longer needed.
  • Check backup retention and perform a restore test.
  • Review storage, database growth and error logs.
  • Record exceptions and the date they will be reviewed.

Quarterly reviews

Quarterly reviews look beyond routine updates. Check whether the site still meets business goals, whether key journeys are accessible and usable, whether performance has changed and whether the hosting or plugin stack needs a larger upgrade. Review the support agreement and contact list as well.

Use the review to prioritise risks rather than generate a long list with no owner. Each action should have a reason, a responsible person, a target date and an acceptance check. Share a client-friendly summary that separates completed work from recommendations.

  • Review performance and Core Web Vitals data.
  • Check user roles, privacy needs and data retention.
  • Review major plugin and PHP lifecycle risks.
  • Test restore and incident response steps.
  • Agree the next quarter's improvements with the client.

Security and access basics

Keep privileged access limited, use multi-factor authentication where available and avoid shared administrator accounts. Make sure backups are protected separately from the production site and that the team knows how to respond to a suspected compromise. A backup is useful only if it is recent, accessible and restorable.

Security scanning can help find known issues, but it does not replace updates, configuration review or investigation after an incident. If malware is suspected, preserve useful evidence, contain the affected site and follow a documented recovery process. Avoid promising that one scanner can guarantee a site is secure.

  • Use individual accounts and least privilege.
  • Keep software supported and patched.
  • Protect backups from unauthorised changes.
  • Document incident escalation and recovery responsibilities.

Service levels and client reporting

Agencies should agree what routine maintenance includes, which issues count as urgent and how response times are measured. Response time is not the same as resolution time; a complex outage may need investigation, third-party input or a planned change. State the service boundaries clearly so clients know what to expect.

Reports should show work completed, important findings, unresolved risks and next actions. Avoid reporting only the number of updates performed. The client needs to know whether the site is healthy, what still needs attention and what decision is required from them.

  • Define included tasks and excluded work.
  • Set priority levels and response expectations.
  • Record incidents, actions and outstanding risks.
  • Use plain language in client reports.

Make the checklist repeatable

Store the checklist in a format the team can use for every client while allowing site-specific checks. Assign owners and dates, record evidence and track exceptions. If the agency manages many sites, automate routine reminders and status collection but keep approval gates for risky actions.

A well-run maintenance service is visible, predictable and honest about risk. It prevents avoidable failures where possible and gives the team a clear path when something does go wrong.

  • Use one standard checklist with site-specific additions.
  • Keep evidence and outcomes beside each task.
  • Review recurring failures to improve the process.
  • Connect maintenance work to a clear support plan.
Put the insight to work

Need a more reliable digital platform?

We can help review an existing product, improve production support or plan the next stage without turning the process into unnecessary complexity.