Cascading updates

A folder's URL is part of every page beneath it, so changing it can rewrite many URLs at once. The plugin only does that when you ask for it explicitly.

A URL can change in two ways, and both cascade to descendants:

• Moving a folder. When you move a folder in the tree, choose Keep existing URLs (the default — pages stay where they are) or Update URLs (every page in the folder and its subfolders gets a new slug from the new path).
• Edit URL on a folder. Changing a folder's pathSegment regenerates the slug of every page beneath it.

Edits made through Payload's standard folder edit screen never cascade. Only the tree's Update URLs choice, Edit URL and Regenerate URLs rewrite descendant slugs.

Edit URLCopy Anchor Link

Right-click any page or folder and choose Edit URL to change its URL segment without touching its display name. The modal has two safeguards.

• Live availability check. As you type, a debounced (300 ms) server check shows a green "Available" or a red "URL is already in use" indicator. Save stays disabled until the segment is valid and available, so a duplicate segment can't be saved. The server checks again on save and answers 409 if the segment was taken in the meantime.
• Type-to-confirm gate. Changing a folder's segment — or moving a folder with children while choosing Update URLs — shows the exact number of pages affected and asks you to type the new segment before it proceeds. This applies to single and bulk folder moves.

Use these controls to reorganise content without breaking existing links: keep URLs when a move is only organisational, and update them when the new structure should show in the address.

Every old URL is kept in the page's URL history, so you can still build redirects after a cascade.

pnpm payload migrate:create
pnpm payload migrate