Interactive checklist
WordPress pre-launch checklist
A full-width interactive checklist for WordPress launch, onboarding, migration, and site handover checks. Your progress is saved in this browser.
Checklist
18 checks
| Done | Check | Guidance | Evidence to record |
|---|---|---|---|
| □ | Confirm domain registrar ownership | Make sure the client owns the domain account and recovery email, not an old developer or agency. | Registrar login confirmed, owner email documented |
| □ | Document hosting, DNS, CDN, and email providers | Record where DNS is managed, where the site is hosted, and which service handles transactional email. | Provider list and emergency contacts |
| □ | Create named admin accounts | Avoid shared admin logins. Give each trusted person their own account with the lowest role they need. | Admin users reviewed in WordPress |
| □ | Set up full-site backups | Back up the database and files. Store backups separately from the live hosting account where possible. | Backup schedule and storage location |
| □ | Test a restore process | A backup is only useful if it can be restored. Test the process on staging or a temporary environment. | Restore test date and result |
| □ | Enforce strong passwords and two-factor authentication | Apply this to WordPress admins, hosting, domain, DNS, analytics, and email tooling. | 2FA enabled for key accounts |
| □ | Remove unused plugins, themes, and users | Inactive code and abandoned accounts increase maintenance and security risk. | Plugin, theme, and user review completed |
| □ | Confirm SSL, redirects, and canonical host | Choose the preferred host, force HTTPS, and avoid duplicate HTTP, HTTPS, www, and non-www versions. | HTTP variants redirect to one canonical URL |
| □ | Install analytics and conversion tracking | Track meaningful actions such as forms, calls, checkout, bookings, newsletter signups, or account creation. | GA4, GTM, or analytics events tested |
| □ | Verify Google Search Console and submit sitemap | Use the correct property, submit the XML sitemap, and check that important pages are indexable. | GSC property verified and sitemap submitted |
| □ | Set up IndexNow submission | Add the IndexNow key file, confirm the public key URL is accessible, and make sure changed URLs can be submitted after deployment. | IndexNow key URL and submission route confirmed |
| □ | Validate schema.org structured data | Check key templates for appropriate structured data such as Organization, WebSite, BlogPosting, Service, FAQ, Product, or Breadcrumb markup where relevant. | Structured data validation completed for key templates |
| □ | Confirm scheduled tasks, cron jobs, and automations | Check scheduled posts, subscription renewals, email automations, CRM syncs, stock updates, or other background jobs the site relies on. | Scheduled tasks documented and tested |
| □ | Configure SMTP for WordPress email | Do not rely on default PHP mail for important contact forms, orders, password resets, or notifications. | SMTP test email received |
| □ | Test every form and notification path | Check required fields, spam protection, success messages, notification emails, and CRM integrations. | Test submissions received and recorded |
| □ | Record speed and Core Web Vitals baseline | Benchmark key templates before launch so future maintenance has something to compare against. | PageSpeed Insights or Lighthouse results |
| □ | Check titles, meta descriptions, headings, and alt text | Make sure important pages have clear search snippets, sensible headings, and useful image descriptions. | Metadata and image review completed |
| □ | Decide when maintenance mode is needed | Use maintenance mode for migrations, major redesigns, security cleanup, or disruptive update work, but avoid using it for normal minor maintenance. | Maintenance mode plan documented |