Pages and navigation
A page's title, URL, navigation position, and access settings answer different questions. Give the page a useful label, place it in the correct collection tree, and then decide whether visitors should find it through navigation or only by a direct link.
Start with page creation and metadata. Next, arrange the tree, test internal links, and review availability. Navigation uses the stored root structure together with page metadata; a URL that looks nested does not create a navigation relationship by itself.
The current standard page settings offer Public, Direct link only, Password protected, and Disabled. Saved editor drafts and a private website are separate concepts. Hiding a link is not access protection.
Use Page anatomy and the managed editor for content inside a page. Collection-specific ordering and item routes are covered in Collections and content trees. Before a large move, rename, or deletion, review Saving, recovery, and troubleshooting and keep a list of addresses and links that need checking.