To delete a WordPress user while retaining their posts, review the deletion screen's content reassignment choice before confirming. First inventory what the account owns and choose an approved replacement. Removing login access and changing historical authorship are separate decisions.
Decide whether deletion is necessary
For offboarding, start with the contractor access removal guide. You may need to revoke access immediately while retaining the account's attribution or investigating integrations. Do not leave an unsafe account active merely because content planning is unfinished; coordinate containment with the authorized owner.
For routine cleanup, confirm that another independently controlled administrator can manage the site and backups. Never test deletion on the only usable administrator account.
Inventory ownership before opening the confirmation screen
List the user's posts, pages, attachments and custom content types. Record important public URLs and their current author displays. Also identify plugin records that reference the account, such as memberships, editorial assignments or integration credentials.
Core's user deletion reference documents reassignment and deletion behavior, but plugins can attach their own hooks and store relationships separately. A promise to keep core posts is not a guarantee that every plugin-owned record will be preserved.
| Record |
Pre-deletion question |
| Published article |
Who should own and be credited for it? |
| Media attachment |
Does any workflow depend on its owner? |
| Custom content |
Does its plugin support reassignment? |
| Integration credential |
Has its consumer been replaced or retired? |
Ownership inventory: Posts and plugin records listed. Replacement account: Identity and purpose verified. Public articles: Content and bylines checked. Old access: Revoked as intended. Explanatory checklist, not a customer test result.
Review the reassignment deliberately
The Users screen documentation describes attributing content to another user during deletion. Select the approved destination carefully. Similar display names are not enough; verify the actual account.
Public authorship needs an editorial decision. Reassigning ownership to an administrator can also change the displayed byline or author archive. Preserve truthful credits using the site's supported editorial mechanism rather than implying the new administrator wrote someone else's work.
On Multisite, distinguish removing membership from one site from deleting the network account. The scope and consequences differ. Have the network operator review the intended action instead of copying a single-site command.
Rehearse and verify before closing the task
Use a private staging copy and a recoverable backup when plugin relationships are unclear. Compare the ownership inventory before and after the rehearsal. Do not experiment with SQL deletions or bulk user-removal commands on production.
After the authorized production action, verify representative article URLs, images, bylines and author archives. Confirm the expected records still exist under the replacement owner. Check that revoked access stays revoked and the replacement integrations still run.
If content disappeared, stop further cleanup and preserve the current database before attempting recovery. Restoring an old full database can overwrite newer orders and submissions. Ask HandL WP to plan a targeted recovery or reassignment using the inventory and backup timestamps, not a public database export.
References reviewed October 5, 2026. Examples are explanatory, not customer test results.