Redirects

URL redirects let you manage HTTP redirections for your site. Use redirects to handle moved content, URL structure changes, vanity URLs, or migrated pages.

Accessing Redirects

Navigate to Redirects in the sidebar. The page shows all configured redirects for the currently selected site.

Redirect Listing

Column	Description
Source path	The original URL path that triggers the redirect.
Target URL	The destination URL the user is sent to.
Type	The HTTP status code: 301, 302, 307, or 308. Permanent codes (301, 308) render in primary color; temporary codes (302, 307) in secondary.
Status	Active or Inactive.
Created	When the redirect was created.

Redirect Types

Type	Status Code	When to Use
Permanent	301	The content has moved permanently. Search engines update their index. Use for URL structure changes and content migrations. The browser is allowed to change the request method to GET on retry — don't use for forms or APIs that depend on POST/PUT.
Temporary	302	The content is temporarily at a different location. Search engines keep the original URL. Use for A/B tests or temporary maintenance pages. Same method-rewrite caveat as 301.
Temporary (preserves method)	307	Like 302, but the browser must keep the original HTTP method on retry. Use when the redirect must survive a POST or PUT — for example, redirecting a form submission to a new endpoint without losing the body.
Permanent (preserves method)	308	Like 301, but method-preserving. The modern recommendation for any permanent redirect that might be hit by something other than a GET — API endpoints, webhook receivers, form actions.

Which code should I pick?

For a moved blog post or marketing page, 301 is the safe, well-understood default. For an API endpoint, webhook receiver, or form action that has moved, prefer 308 (or 307 if the move is temporary) so client tooling doesn't silently demote POST to GET on retry.

Creating a Redirect

1. Click the New Redirect button.
2. Fill in the redirect details:
   • Source path -- the path to redirect from (e.g., /old-blog-post). This is relative to your site's domain.
   • Target URL -- the destination URL. Can be a relative path (e.g., /new-blog-post) or an absolute URL (e.g., https://example.com/new-location).
   • Type -- select one of the four codes (301, 302, 307, 308).
3. Click Save.

tip

Use a leading slash for source paths (e.g., /old-path not old-path). The source path is matched against the incoming request path.

Editing a Redirect

Click on a redirect in the listing to edit it. Modify the source path, target URL, or type and save.

Deleting a Redirect

Click the delete icon on a redirect and confirm. The redirect stops working immediately.

Common Use Cases

Content Migration

When you move a blog post from /blog/old-slug to /blog/new-slug:

• Source: /blog/old-slug
• Target: /blog/new-slug
• Type: 301 Permanent

Domain Change

When redirecting old domain paths to a new domain:

• Source: /about
• Target: https://newdomain.com/about
• Type: 301 Permanent

Vanity URLs

Create short, memorable URLs that redirect to longer paths:

• Source: /go
• Target: /getting-started/installation
• Type: 302 Temporary

Best Practices

• Use 301 (Permanent) for content that has permanently moved. This helps search engines update their index and pass link equity to the new URL.
• Use 302 (Temporary) sparingly, only when the redirect is genuinely temporary.
• Prefer 307 or 308 whenever the redirected URL might be hit by a non-GET request (form submissions, API calls, webhook deliveries). These codes guarantee the original HTTP method is preserved on retry.
• Avoid redirect chains (redirect A to B to C). Point directly to the final destination.
• Regularly review your redirects and remove any that are no longer needed.

Permissions

Action	Required Role
View redirects	Viewer
Create/edit redirects	Admin
Delete redirects	Admin