DirectAdmin’s Site Redirection creates simple redirects without editing files.
Steps
- Open Account Manager then Site Redirection.
- Choose the domain.
- Enter the local path to redirect from, such as
/old-page. - Choose the redirect type (301 or 302).
- Enter the full destination URL, such as
https://yourdomain.co.uk/new-page. - Save, then test in a private browser window.
301 or 302?
| Type | Means | Use when |
|---|---|---|
| 301 | Moved permanently | The old URL is gone for good. Search engines pass its ranking to the new one. |
| 302 | Found / temporary | The move is temporary and the old URL will return. |
For almost every real-world case — a renamed page, a moved site — use 301.
When to use .htaccess instead
Site Redirection handles one path at a time. Use .htaccess for:
- redirecting whole patterns (every page under
/blog/to a new domain) - forcing HTTPS or choosing www / non-www
- conditions based on the requested host
Redirects with .htaccess: copy-ready examples has ready-made rules.
Avoiding loops
Never redirect a page to itself, or two pages to each other. If you already force HTTPS in WordPress or .htaccess, don’t add a second HTTPS redirect here. “Too many redirects” and HTTPS redirect loops