Homepage and navigation settings

Documentation / Site administration and domains

The homepage and the navigation are related but separate. A page's route determines where it opens; root files determine navigation order and hierarchy. A title or URL that looks nested does not automatically place that page beneath another item in the menu.

Check the homepage

In Content > Pages, identify the page that opens at / and inspect its settings. Review its page title, navigation label, availability, and template. Open the root address in a visitor session to confirm that it displays the expected content, including the correct language behavior.

Do not change several page paths to / while experimenting. Plan a homepage replacement so there is one intended destination, with existing links and any redirect requirements reviewed before saving.

Maintain the navigation tree

Use the page structure and reorder controls to place pages in the intended order and parent-child hierarchy. The main root is the source of the main navigation tree. Its entries reference page IDs; labels and availability come from the pages themselves.

A page can exist without appearing in navigation. When an item is missing, check both its membership in the root and its page-level availability. Public pages, or pages without a restrictive availability value, are eligible for normal navigation. A path hierarchy alone is not sufficient.

Review shared header controls

Under Settings > General > Settings, Show site header, Show search icon, and Show language switcher control shared header features. A custom shell can provide its own presentation while still using the root-derived navigation component.

After saving, inspect desktop menus, mobile disclosure, nested links, and translated labels. If an assistant changes the root, require a complete reviewed tree and current root version. Keep metadata on page settings, not navigation entries. See pages and navigation and languages and translations.