Originally published: January 12, 2021 · Last updated: August 17, 2026
Accidentally deleting a WordPress page does not always mean the content is gone. WordPress normally moves deleted posts and pages to Trash first, and revisions or backups can provide additional recovery paths when the current item is damaged or permanently removed.
The right recovery method depends on what actually happened, so start with the least destructive option.
1. Check Trash first
For a standard WordPress installation, moving a post or page to Trash does not immediately erase it. WordPress keeps trashed content for a period before permanent deletion, with 30 days as the default.
Open Posts or Pages in the dashboard, switch to the Trash view and look for the missing item. If it is there, restore it instead of recreating the page manually.
2. Use revisions when the page still exists but the content is wrong
Sometimes the page was not deleted. Its content was overwritten, heavily edited or partially removed. In that case, revisions are more appropriate than Trash.
WordPress stores previous saved versions of posts and pages. The revision screen lets you compare versions and restore an earlier state. WordPress 7.0 includes an updated revision interface with clearer change markers.
3. Check your backup system after permanent deletion
If the item has been permanently deleted or Trash has already been emptied, a backup is the next reliable recovery path.
Do not automatically restore an entire production site just to recover one page. First determine whether your backup tool or host can restore the database to a temporary location or staging site. You can then copy the missing content back without overwriting newer production changes.
4. Look for exports or staging copies
A WordPress XML export, staging site, local development copy or recent migration package may contain the missing page. These are useful secondary sources when a normal backup is unavailable.
They may not reproduce every piece of plugin metadata, but they can save the text, slug, featured-image reference and other information needed to rebuild the page accurately.
5. Treat database recovery as a last resort
Direct database work is not the first recovery method for a normal site owner. WordPress content and metadata can be spread across several records, and manual edits can create new problems.
If a page is permanently gone and the only remaining copy is inside a database backup, restore that backup safely to a separate environment and extract the content there rather than experimenting directly on the live database.
What happens to the old URL?
If a deleted page was public and had traffic or inbound links, restoring the same page at the same URL is usually the cleanest outcome when the content still belongs on the site.
If the page should remain deleted, decide whether an equivalent replacement exists. Redirect the old URL only when there is a genuinely relevant destination. Otherwise, a normal not-found response can be correct.
Prevent the next recovery emergency
- keep automated backups outside the WordPress server;
- test that backups can actually be restored;
- use staging for major edits;
- review revisions before overwriting complex pages;
- limit destructive permissions to people who need them.
The practical rule
Recover in this order: Trash, revisions, backups, secondary copies, then specialist recovery. Each step is safer than immediately manipulating the database or restoring an entire site.
Official references: WordPress page and post settings and WordPress revisions documentation.