Redirects

Redirects send visitors from one URL to another. They're essential when you rename or restructure pages — without redirects, old links and bookmarks would lead to "Page Not Found" errors.

When to use redirects

• You changed a page's slug (URL path)
• You moved a page under a different parent
• You deleted a page but want the old URL to go somewhere useful
• You want a short vanity URL (e.g., /give → your giving platform)

Setting up a redirect manually

1. Go to Settings → Redirects
2. Click Add item
3. Enter the source path (the old URL, starting with /)
4. Enter the destination (where visitors should be sent)

Automatic redirects from slug changes

When you change a page's slug and publish, Studio detects the change and offers to create a redirect for you automatically — so existing links to the old URL keep working.

What happens when you publish

A dialog titled Slug change detected appears before the page is published. It shows:

• This page — the old URL and the new URL
• Child pages (if any) — any nested pages whose URLs will also change, each listed with their old and new paths

Click Publish & create redirects to accept. Studio will:

1. Update the page's slug (and patch child page slugs so they stay correct)
2. Create a redirect entry in Settings → Redirects for each URL that changed
3. Mark those redirects as auto-generated

Click Cancel to back out without publishing.

Finding auto-generated redirects

In the redirect list, automatic entries show:

• A • auto label next to the destination in the preview
• A read-only Created by field set to "Auto (slug change)"
• A read-only Source page field linking back to the page whose slug changed
• A Created at timestamp

You can edit or delete auto-redirects the same as manual ones.