# Slugs, paths, and moving a page

URL: https://kywi-docs-production.up.railway.app/authoring/slugs-paths-and-moving-a-page
Type: docPage

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.

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.

## The Parent field moves the page too

Saving a new value in the Parent field on a page’s Navigation tab is the same move as **Move to…**: the page and its children get new URLs and the old ones redirect. The field takes a raw content id, so **Move to…** is the easier way to pick a parent. A parent inside the page’s own subtree is refused.

## The old URL redirects to the new one

Kywi records the old path whenever a page moves or its slug changes, and a request for it is answered with a permanent redirect to where the page lives now, query string included. If the page is unpublished, outside its Unpublish At, or restricted, the old URL is a 404 too. Menu items follow the page on their own; links typed into body copy work through the redirect, but fix them when you can.

## 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.

## Restoring can drop the override

If another page took the address while this one was deleted or on an older version, a restore still succeeds but leaves the override empty and says so — a warning in the editor on a version restore, a `restoreWarning` in the API response on a version or trash restore. Publishing a changeset or approving a revision does the same and reports the warning in the API response. Check the Navigation tab after restoring a page that had one; the Trash screen does not show the warning.

## Two pages, one URL

## A slug a sibling page already uses is refused

Creating a page, changing its slug or moving it is refused when a sibling page in the same language already has that slug; a copy takes the next free `-copy`, `-copy-2` slug instead. A page and a form may still share one. The check runs only when a slug or parent changes, so two sibling pages that already shared a slug before the upgrade still do: the older one answers every request and the newer one is unreachable. If a page shows something else’s content, look for the sibling that got there first and re-slug one of them.
