Troubleshooting missing pages and navigation items
Documentation / Saving, recovery, and troubleshooting
A missing menu item and a missing page are different problems. A page may exist and open directly while being absent from navigation. Conversely, a root entry can point to content that no longer exists. Identify the failure before creating a replacement or changing visibility.
Check the content target
Confirm the website and exact route, including its language prefix. In Content > Pages, look for the stable page ID rather than relying only on the title. Review its path, availability, root, template, and redirects. A renamed title does not necessarily mean a new URL.
For collection items, the public route combines the collection base path with the stored relative slug and language configuration. Do not assume that the stored item slug is the complete public URL.
Check navigation membership
The main root defines the menu's order and hierarchy. Page metadata supplies labels and availability. Moving a page URL beneath another URL does not create a navigation child automatically.
Check that the intended page ID appears in the correct root and that its availability permits public navigation. If a parent is restricted, inspect the resulting branch as well. A direct-link page can intentionally be outside normal navigation.
An assistant can use list_roots for a complete inventory, including pages outside navigation, translations, stale references, and unknown-root content. Ask for read-only diagnosis before approving a tree rewrite.
Test as the right visitor
A private website or page can appear available to an administrator but not to a visitor. Test without admin or private-preview access. Check redirects and translated fallbacks before concluding content was deleted.
If content really is gone, inspect page history or ask an administrator about snapshots. Do not fill the gap with a duplicate page until identity and inbound-link consequences are understood. See pages and navigation, collections, and languages.