In addition to the existing page slug, allow additional paths, which do a permanent redirect (301) to the main page URL.
Here I'll refer to those secondary paths as Redirects since that's their function.
Often, a given page needs to be referable by several different slug/paths;
KEY IMPLEMENTATION SUGGESTIONS
The redirect slug is full-path. e.g. /foo/bar/page. This allows redirects to function regardless of how the site hierarchy changes. It also supports "shortcuts" for print & TV marketing, e.g. /mowers -> /category/mowers
Whenever a slug is changed on a Page, Folder, CMS collection, or CMS item, automatically create a redirect for the old slug, to the new path.
For Folders and CMS collections that are moved via a slug change, this could be a wildcard redirect such as /oldslug/* -> /newslug/* Or, you can simply create the redirect one each of the child pages (for a folder) or existing CMS items (for a collection)
Redirects show beneath the Slug, and can be added, edited, or deleted at any time.
If you attempt to create an new Page, Folder, CMS collection or CMS item, whose path conflicts with an existing redirect path, alert the user to confirm. Notify them that the redirect exists, and will be deleted if they approve. This maximizes the flexibility of the site, and minimizes 404's, without impeding change and new content creation.
WHY THE CURRENT "HOSTING PLAN" REDIRECTS FAIL