Know who can change the site

Review administrator and editor accounts, remove access that is no longer needed and confirm that each person has an individual account. Use strong authentication for privileged access and store recovery methods where the organisation can retrieve them.

Check hosting, domain and DNS accounts as well as WordPress itself. A secure dashboard does not help if a former contractor or unused mailbox still controls the hosting account or password reset path.

Review updates and extensions

Keep WordPress core, themes and plugins on supported versions. Remove extensions that are inactive or no longer required, and identify who receives update notices and applies changes. Test significant updates in a staging environment when the site’s integrations or custom code make that prudent.

Before adding a plugin, check who maintains it, whether it is still supported and whether its features overlap with something already installed. Fewer well-maintained components are easier to review than an unowned collection of extensions.

Check backups and recovery

Confirm what is backed up, how often, where copies are stored and who can restore them. A backup that has never been restored is an assumption, not a recovery plan. Perform a controlled restore check and document the steps and access needed.

Keep at least one backup separate from the production account so a compromised hosting login cannot automatically erase every recovery copy. Set retention around the business’s needs and legal obligations.

Include the hosting layer

Review the PHP version and support status, file and database access, TLS configuration, administrative access and any security controls supplied by the host. Confirm who handles infrastructure patches and how incidents are reported.

Treat this as a maintenance routine, not a one-time certificate. Record the owner and review date for each task so security work remains part of operating the site.