Skip to content

Slugs, paths, and moving a page

A slug is derived from the title once, at creation; a moved page’s old URL redirects to the new one, and URL Override gives a page its own address.

A page’s URL is the chain of slugs from the site root down to it: a page slugged pricing inside a section slugged platform is served at /platform/pricing. Kywi stores that chain on the page itself, and rewrites it only when the page or a section above it is moved or re-slugged.

What renaming a page does

Editing a title changes the label in the tree, the menu and the breadcrumb, and leaves the URL alone. The slug follows the title only at creation, and through a transform that deletes punctuation rather than replacing it — so the spaces around a dropped character survive as hyphens.

text
Title   Pricing, plans & FAQ
Slug    pricing-plans--faq     ← the comma and the & are deleted, their spaces are not
Path    /platform/pricing-plans--faq/

Creation is therefore the moment to set the slug you want: the Slug field keeps what you type (trimmed), and only fills itself in from the title when you leave it empty.

Changing a slug moves everything under it

Saving a new slug rewrites this page’s URL and the URL of every page beneath it, in the same save. Re-slug a section from guides to handbook and its forty children are served from /handbook/… at once, with nothing to republish.

Moving a page

Move to… in the Site Tree’s row menu gives a page a new parent and rewrites its path and every path beneath it, the way a slug change does. Dragging a row is a different action: it sets the order siblings appear in and never touches a URL.

Giving a page its own address with URL Override

The Navigation tab has a URL Override field. Type a path such as /team and that becomes the page’s public address, whatever its place in the tree: the page is served there, its tree URL permanently redirects to it, and menus, navigation, breadcrumbs, the sitemap, the llms files, feeds, search results and the canonical tag all use the override. Pages beneath it keep their own tree URLs. While the page is unpublished, outside its Unpublish At or restricted, both addresses are a 404.

An override may use only lowercase letters, digits, hyphens and underscores in each segment — no dots, so no .html or other file extension — and is saved lowercased with a trailing slash. It can’t be /, can’t begin with a reserved name (admin, api, ax, kywi, media and the framework’s own routes), a language code or a site-mount prefix, and the home page and site mounts can’t take one. Only page-like content can have one. Overriding a page with its own tree URL just clears the field.

Each override is unique within its site and language, against every other page’s tree URL and override; a deleted page frees its address. The check runs both ways: a save that would collide is refused with the reason, and so is a create, slug change, move, copy or trash restore that would land a tree URL on another page’s override. Change or clear the override and the old address redirects. A copy or a translation starts without one.

Two pages, one URL