WordPress backup checklist: Verifying restorability
Published:
Published by: Hedou Bibi
A WordPress backup checklist verifies files and database, then tests restore in isolation.

A WordPress backup checklist answers one question: can the backup package be restored into a working site? Files and the database must both be included. Posts, pages, users and settings live in the database, while core files, themes, plugins and uploaded media live in the filesystem. Keeping only one part cannot restore a complete site. A WordPress export XML contains only partial content data and excludes plugins, themes, uploads and full configuration, so it cannot replace a complete backup, but it can be used for content-level verification.
First, inspect the package structure: do site files cover core, themes, plugins and the uploads directory; does the database cover all tables and settings; are the WordPress core, database and key plugin versions recorded at backup time retained? Versions and dependency artifacts need separate confirmation, including vendor-specific external dependencies such as external APIs, queue services, object storage, payment gateway configuration or remote resources used by custom plugins. The configuration for these dependencies may be included in the files/database package, but the external service itself, its availability or separately stored credentials may not be in the package. Document them according to the actual configuration and compare item by item after restore.
Validation should run in an isolated test environment, never against production. Before restoring, disable email sending, scheduled callbacks, payments and external notifications so the test does not trigger real business actions. After restore, check in order: can the site be read and can you log in; do the homepage and key pages render; are media files accessible; does a test form submission verify storage, admin records or simulated notification results according to the actual configuration. Record each result as restorability evidence, including restore logs, page read results and form verification records. This rehearsal only represents the verification result of this backup snapshot in the corresponding environment.
Scroll horizontally or use the arrow keys to view the full table.
| Check | Focus | Evidence |
|---|---|---|
| File completeness | Core, themes, plugins, uploads | Directory comparison |
| Database completeness | All tables and settings | Table list, import result |
| Versions and artifacts | Core, database, plugin versions | Version record |
| Vendor dependencies | API, storage, payment configs | Dependency list |
| Isolated restore | Email, callbacks, payments off | Restore log |
| Functional reads | Pages, media, form read/write | Test records |
Acceptance rests on evidence: files and database restored, versions and dependencies accounted for, and read/write checks passed in isolation. The XML export can be used for content-level verification but does not constitute acceptance of a complete backup. These steps are for checking and rehearsal only, not real operations on production; rehearsal results only represent the state of this snapshot in the corresponding environment.
