Most WordPress problems appear after launch, not before. Slow performance, security incidents, SEO indexing issues — all because basic hosting checks were skipped.
This checklist is designed to be used before any WordPress site goes live, regardless of hosting provider.
Table of Contents
-
Hosting & Server Checks
-
PHP & Environment
-
Security Hardening
-
Performance & Caching
-
SEO & Indexing
-
Backup & Recovery
1. Hosting & Server Checks
Before launch, verify:
-
Hosting account is isolated (CloudLinux / containerized)
-
Correct domain assigned to the account
-
No addon domains sharing the same document root
-
Temporary URLs disabled
Quick test:
-
Upload a random file
-
Confirm it is not accessible from other domains
Why this matters:
Shared roots are a common cause of cross-site contamination.
2. PHP & Environment
Checklist:
-
PHP version: 8.1+
-
PHP handler: FPM / LSAPI
-
Error display: OFF
-
Error logging: ON
Required values:
Verification:
-
phpinfo()
-
WordPress Site Health must show “Good”
3. Security Hardening (Before Traffic Exists)
Do this before indexing:
-
Change default admin username
-
Enable 2FA (WordPress + cPanel)
-
Disable XML-RPC if unused
-
Remove unused themes and plugins
File permissions:
Never launch with default credentials.
4. Performance & Caching
Mandatory before launch:
-
Page cache enabled
-
Browser cache enabled
-
GZIP or Brotli active
Optional but recommended:
-
Object cache (Redis/Memcached)
-
Image lazy loading
Rule:
If caching is added after launch, performance metrics are already polluted.
5. SEO & Indexing
Checklist:
-
Search engine visibility unchecked
-
HTTPS enforced
-
Canonical URLs verified
-
Sitemap generated and accessible
Before launch:
-
Block indexing on staging
-
Enable indexing only on production
Common mistake:
Launching staging URLs indexed by Google.
6. Backup & Recovery
Minimum requirements:
-
Daily backups
-
Offsite storage
-
Manual restore tested at least once
Test:
-
Restore a single file
-
Restore database snapshot
If restore was never tested, backups do not exist.
Why This Checklist Gets Shared
This checklist:
-
Works on any hosting
-
Prevents real production issues
-
Is vendor-neutral
-
Saves agencies time and reputation
That makes it link-worthy, not promotional.
Key Takeaways
-
Most hosting issues are predictable
-
Pre-launch checks prevent 90% of incidents
-
A checklist is cheaper than fixing production failures
Leave a Reply