A secure WordPress site depends on more than a strong password or a free SSL certificate. This reusable WordPress hosting security checklist shows what to configure before launch, what to verify on shared or managed hosting, and what to review after updates, plugin changes, migrations, or security incidents.
Overview
WordPress security is a shared responsibility. Your hosting provider controls parts of the server, network, account, backup, and monitoring environment; you control the WordPress installation, administrator accounts, themes, plugins, content, and configuration. A secure WordPress hosting plan should support good operational habits, but no hosting feature replaces routine maintenance.
Start by identifying what could be affected if the site is compromised. A brochure site may primarily need protection for its content and visitor data. A store, membership site, or business website may also need to protect customer information, orders, forms, email accounts, and integrations. This risk assessment helps determine whether shared hosting is sufficient or whether managed WordPress, VPS hosting, or cloud hosting offers the isolation and control you need.
Before choosing a provider, ask for specific details rather than relying on labels such as “secure hosting” or “managed security.” Confirm which controls are included, whether they apply to your plan, how long backups are retained, and how you can restore or obtain assistance during an incident. A hosting comparison should evaluate recovery and account security alongside speed, storage, and price.
Hosting-feature comparison checklist
| Feature | What to verify | Why it matters |
|---|---|---|
| Automatic updates | Whether WordPress core, plugins, and themes can be updated automatically; whether exclusions, notifications, and rollback options exist | Reduces the time a known issue remains unaddressed, but updates should still be tested for compatibility |
| Malware scanning | What is scanned, how often scans run, how alerts are delivered, and whether cleanup is included or separate | Helps identify suspicious files or changes that may not be visible in the WordPress dashboard |
| Web application firewall | Whether a WAF is provided, where it operates, how rules are managed, and how false positives are handled | Can filter some hostile web requests before they reach WordPress |
| Backups | Backup frequency, retention period, storage location, included databases and files, and whether backups are independent of the live account | Provides a recovery path after accidental deletion, failed updates, or compromise |
| Restore testing | Whether you can restore files and databases separately, use a staging restore, and verify that backups are usable | A backup that has never been tested may not meet your recovery needs |
| Account isolation | How accounts, sites, users, and processes are separated on shared infrastructure | Limits the potential impact of a problem elsewhere on the server, although no isolation claim should be treated as absolute |
| Multi-factor authentication | Whether MFA is available or required for hosting, billing, email, SSH, and WordPress administrator accounts | Protects accounts even if a password is exposed |
| Staging | Whether the plan includes staging, protected access, database copying, and a dependable way to push tested changes live | Allows updates and configuration changes to be checked before production use |
| PHP-version support | Which supported PHP versions are available, how versions are changed, and whether old versions are retired | Keeping PHP and WordPress components within supported compatibility ranges improves security and reliability |
| Incident response | How to report a suspected compromise, what assistance is available, expected communication channels, and what evidence is preserved | Clear escalation procedures reduce confusion when the site is unavailable or infected |
Checklist by scenario
Before launching a new WordPress site
- ☐ Confirm the domain, hosting account, and WordPress administrator email are controlled by the business or site owner.
- ☐ Enable MFA on the hosting panel, registrar, billing account, email account, and every WordPress administrator account that supports it.
- ☐ Use unique, long passwords and store them in an approved password manager. Do not share a single administrator login.
- ☐ Remove unused themes, plugins, sample content, temporary users, and installation files.
- ☐ Use HTTPS and confirm that the site, login area, forms, and administrative redirects behave correctly.
- ☐ Set the least-privileged WordPress role appropriate for each person. Editors and contributors do not normally need administrator access.
- ☐ Confirm that the host supports a currently supported PHP version and that the selected theme and plugins are compatible with it.
- ☐ Configure scheduled backups and complete a test restore before accepting real traffic.
- ☐ Set up staging if the host provides it, and document how to copy the site and database safely.
- ☐ Record hosting support contacts, domain access, DNS access, backup locations, and the procedure for reporting an incident.
After installing a plugin, theme, or integration
- ☐ Check the developer, update history, required PHP version, permissions, and data access requested by the extension.
- ☐ Take or confirm a recent backup before activation or a major configuration change.
- ☐ Test the change in staging when possible, including login, forms, checkout, search, caching, and key integrations.
- ☐ Delete replaced or abandoned extensions rather than leaving them disabled but installed.
- ☐ Review new administrator accounts, API keys, webhooks, scheduled tasks, and external services created during setup.
- ☐ Check logs, malware alerts, uptime monitoring, and page performance after deployment.
During a quarterly security review
- ☐ Export a current list of plugins, themes, users, PHP version, WordPress version, and hosting security features.
- ☐ Review inactive accounts and remove access that is no longer required.
- ☐ Test a backup restore in a private or staging environment and record the result.
- ☐ Confirm backup retention still matches the site’s recovery requirements.
- ☐ Review WAF, malware scanning, login protection, rate limiting, and alert settings.
- ☐ Check that domain, DNS, hosting, and email accounts still use MFA and current recovery details.
- ☐ Review uptime and error monitoring for repeated failures, unexpected redirects, or traffic anomalies.
- ☐ Apply updates through staging or a documented maintenance process, then verify important user journeys.
After a suspected compromise
- ☐ Record symptoms, timestamps, suspicious URLs, affected users, alerts, and recent changes before deleting evidence.
- ☐ Contact the host through its incident or abuse channel and ask what account, server, and backup evidence is available.
- ☐ Change passwords and revoke sessions, API keys, application passwords, and access tokens from a clean device.
- ☐ Preserve a copy of relevant logs and avoid restoring an unverified backup over the live site.
- ☐ Identify the entry point, remove unauthorized code or accounts, patch the cause, and scan the restored site.
- ☐ Check DNS, redirects, search visibility, forms, payment connections, and email for unauthorized changes.
- ☐ Document the incident and add preventive controls to the next review.
What to double-check
Backups are not the same as recovery. A provider may advertise daily backups, but you still need to know whether the database is included, how many versions are retained, where they are stored, and how quickly a restore can begin. Test both a complete restore and, where practical, a database-only or file-only recovery. For a detailed migration and recovery workflow, see the website migration checklist and hosting comparison.
Automatic updates need boundaries. Automatic WordPress core updates may reduce maintenance effort, while automatic plugin or theme updates can introduce compatibility problems. Use staging for important sites, enable update notifications, and define which components are approved for unattended updates. Keep a rollback path rather than assuming an update can always be reversed.
Security features may be plan-specific. Malware scanning, WAF rules, staging, account isolation, incident assistance, and backup retention can differ between shared, managed WordPress, VPS, and cloud plans. Ask the provider to identify exactly what is included in your plan. The WordPress hosting guide can help frame broader hosting questions, but provider documentation should decide the final configuration.
Performance is part of resilience. A site that times out during updates or receives traffic spikes is harder to operate safely. Monitor uptime, PHP errors, database errors, storage limits, and resource usage. Use the website uptime monitoring guide to establish checks that alert someone who can act.
Common mistakes
- Relying on a security plugin alone: A plugin can add useful controls, but it cannot secure a compromised hosting account, outdated PHP runtime, stolen domain credentials, or weak backup process.
- Keeping inactive plugins installed: Deactivation is not the same as removal. Retain only extensions with a clear purpose and maintenance path.
- Using one administrator account for everyone: Individual accounts improve accountability and make it possible to remove one person’s access without disrupting the team.
- Ignoring the registrar and email account: An attacker who controls the domain or mailbox may be able to reset hosting and WordPress access. Protect these accounts as carefully as the site itself.
- Assuming a backup is clean: A backup created after an intrusion may preserve the compromise. Establish restore points and verify their contents before relying on them.
- Changing PHP or caching settings directly on production: Test changes in staging and keep a documented rollback plan.
- Choosing on introductory price alone: Compare renewal costs, security controls, support boundaries, and recovery options. The web hosting renewal costs guide provides a useful framework for evaluating long-term value.
When to revisit
Use this checklist before launch, after a major WordPress release, whenever a plugin or theme changes, and after a hosting migration or DNS change. Schedule a formal review at least quarterly for an actively maintained site, with more frequent checks for ecommerce, membership, publishing, or business-critical websites.
Refresh the checklist whenever your host changes its backup retention, supported PHP versions, MFA options, WAF controls, staging workflow, or incident-response process. Recheck the provider’s documentation after changing plans, moving from shared hosting to VPS or cloud hosting, or adding a second site to the account. A hosting comparison should be repeated when traffic, data sensitivity, integrations, or recovery expectations change.
To make the next review practical, save the completed checklist with the date, WordPress and PHP versions, installed extensions, backup test result, and outstanding actions. Assign an owner to every unresolved item and set a deadline. Then perform one small verification immediately: log in with MFA, inspect the latest backup, or restore a copy to staging. Repeating these concrete checks is more valuable than treating security as a one-time launch task.