This runbook defines how site elements are cleaned up, decommissioned, or archived in a controlled, documented manner.
Cleanup and decommissioning are deliberate operations—not reactive deletions. They are performed to preserve structure, usability, and long‑term integrity as the site evolves.
Checklist Objective
Remove or archive site elements intentionally while preventing broken URLs, orphaned assets, configuration drift, or unintended SEO side effects.
Scope Boundary
This runbook covers:
- Content removal and archival decisions
- Plugin and feature decommissioning
- Media library cleanup
- URL handling for removed content
This runbook does not cover:
- Server or OS‑level cleanup
- Database‑level purges outside WordPress
- Emergency rollbacks (handled by backups)
Preconditions
- Operations 05 — Content & Structural Audits is completed and approved
- Backup and recovery readiness is confirmed
- No active troubleshooting is in progress
Important Terminology — What “Archiving” Means
In this system, archiving has a specific, narrow meaning. Because the term is overloaded in WordPress and IT contexts, the following definitions apply.
Archiving (as used in this runbook)
- The content continues to exist
- The URL is preserved
- The item is removed from active navigation and workflows
- The item is no longer updated or maintained
- The item may be set to NoIndex if appropriate
Archiving is used when content may have future reference value but should not remain part of the active site surface.
Archiving does NOT mean
- Deleting the Page or Post
- Moving it under a parent Page or Post named “Archive”
- Relying on WordPress category or tag archive grids
- Hiding content via UI tricks without documentation
Important clarification
- WordPress “Archives” (category archives, date archives, search results) are not archival storage
- They are dynamic query results and must not be used to represent decommissioned content
Checklist Steps — Content Cleanup & Archival
1. Evaluate content for removal or archival
- Identify content that is outdated, duplicated, or unused
- Confirm the content is no longer required by any workflow
- Confirm the content is not referenced by active checklists
2. Decide: archive or delete
- Archive if:
- The content may be referenced historically
- The URL should be preserved
- Delete if:
- The content has no future value
- The content is a duplicate or mistake
3. Archive content (if applicable)
- Remove the content from active navigation
- Document the archival decision and reason
- Apply NoIndex where appropriate
- Confirm no active workflows rely on the content
4. Delete content (if applicable)
- Confirm the content has no future value
- Prepare URL handling before deletion
- Delete the content deliberately
Checklist Steps — URL & SEO Handling
5. Define URL behavior
- Determine whether redirects are required
- Use appropriate HTTP status codes
- Avoid redirect chains
6. Verify indexing state
- Confirm archived content is no longer indexed if intended
- Confirm deleted content is removed from sitemaps
- Confirm sitemap updates reflect changes
Checklist Steps — Plugin & Feature Decommissioning
7. Review plugins and features for removal
- Identify unused or redundant plugins
- Confirm no dependencies exist
8. Decommission plugins safely
- Deactivate plugins before deletion
- Remove related features deliberately
- Confirm no templates or components rely on them
Checklist Steps — Media Cleanup
9. Identify unused media
- Locate images not referenced by active content
- Confirm media is not used by templates or components
10. Remove or archive media
- Delete unused assets when safe
- Avoid breaking existing references
Required Output
- Content cleanup and archival decisions documented
- Plugins and features decommissioned safely
- Media library free of unused assets
- URLs and indexing handled correctly
Pause & Lock
Cleanup and decommissioning actions must result in a stable, documented site state before any further changes are made.
Completion of this runbook closes the Operations phase. Future work must loop back through the appropriate Operations runbook rather than bypassing established controls.