Redirects send visitors from one URL to another. Common use cases: redirect www.example.com to example.com, redirect an old path to a new one, or forward a temporary domain to a live site.
Creating a Redirect
- In Hosting Mode, go to Domains → Redirects
- Click New Redirect
- Fill in the form:
| Field | Description |
|---|---|
| Source domain/path | The URL that should redirect. Can be a full domain or a domain + path prefix. |
| Destination URL | Where visitors are sent. |
| Redirect type | 301 (permanent) or 302 (temporary). |
- Click Save
The Agent writes an Nginx return directive for the matched rule and reloads Nginx. The redirect takes effect immediately.
Redirect Types
301 — Permanent. Browsers and search engines cache this redirect. Use it when the move is final (old domain → new domain, old URL → new URL after a site redesign). Once cached, changing the destination can take time to propagate to returning visitors.
302 — Temporary. Not cached. Use it during maintenance, A/B testing, or when you genuinely intend to bring the source URL back later.
Common Examples
Redirect www to non-www (or vice versa):
Add a redirect with source www.example.com → destination https://example.com. The path is preserved automatically.
Redirect an entire domain:
Source: oldsite.com → Destination: https://newsite.com
All paths under oldsite.com will redirect to the equivalent path on newsite.com (e.g., oldsite.com/about → newsite.com/about).
Redirect a specific path:
Source: example.com/old-page → Destination: https://example.com/new-page
Deleting a Redirect
Go to Domains → Redirects, find the redirect, and click Delete. Nginx is reloaded and the rule is removed.