Collection ordering, summaries, and visibility
Documentation / Collections and content trees
Order, summary, and visibility answer different questions: where does an item appear, what short description represents it, and can visitors access or discover it? Changing one does not automatically change the others.
Set the intended order
For a sequential collection, arrange pages in its reorder tree. The root file owns sibling order and parent-child relationships. A listing can use that order or another supported sort. Dated listings default to newest publication date first. Popular (Rating) uses recorded ratings, not measured page views.
Check which summary is displayed
Write concise descriptive copy, but verify the field used by the selected renderer. The current native Summary control saves navSummary. Dated listings read pageSummary, with older-field fallbacks; the tree renderer reads description for its descriptive text.
These are not interchangeable fields in the current implementation. If editing Summary does not update a listing, ask an administrator to inspect and update the field that renderer actually consumes. Do not repeatedly rewrite the same control or assume it changed the SEO description.
Check availability separately
Page metadata owns availability. Listings exclude unavailable items; dated listings additionally exclude future dates. Tree listings also respect the unlisted flag. The In navigation setting does not provide privacy, even though its saved flag can also affect tree listings.
A direct-link page can remain accessible and indexable without appearing in public listings or menus. An indexing exclusion also does not restrict access.
Validate all three
Reload the listing after saving. Check order, visible description, and destination as a visitor. Inspect site navigation and search metadata separately.