Deleting pages and checking affected links
Documentation / Pages and navigation
Deletion removes content; it is not a substitute for hiding a navigation item. If the page only needs to leave the menu, review its listing or availability settings first. If visitors should reach a replacement destination, consider a redirect before deleting the original.
Review dependencies first
Record the page address and identity, then inspect the places that may depend on it:
- Main navigation and collection branches.
- Text links and Buttons on related pages.
- Collection listings and manually selected page lists.
- Section Embed or Block Embed references.
- Shared topline, prefooter, or footer settings.
- Translations and external links to the old address.
A stable page reference avoids some rename problems, but it does not make a deleted target available. Do not assume the delete confirmation includes a complete incoming-link report.
Delete the intended page
Open the page metadata, locate Danger Zone, and choose Delete page. Read the confirmation carefully, including the displayed path. The current confirmation warns that the deletion cannot be undone. Do not rely on ordinary visual-editor backups as a guaranteed undelete facility.
If a branch or shared page is involved, have the administrator review the effect before confirming. A page used as shared chrome should not be treated as an isolated article.
Check the website afterward
Reload the content list and inspect the relevant navigation branch. Open known incoming links, replacement routes, and any pages containing references to the deleted content. Repair stale references explicitly. Also check the visitor-facing error or redirect behavior at the previous address.
For recovery options that actually exist in your installation, see Saving, recovery, and troubleshooting.