A redirect sends a browser from one URL to another. Use a path redirect for a moved page or a carefully planned site move, and choose its status according to whether the move is temporary or permanent.
IN THIS ARTICLE
Check access and requirements
Identify the source domain and path and confirm the destination already works. Record existing application, CDN and web-server redirects. Overlapping rules can create loops, and a permanent redirect can remain cached after you edit the server.
01 Create a website or path redirect in DirectAdmin
- Select the source domain in DirectAdmin, then open Account Manager > Site Redirection.
- Choose Create New Redirect. Enter the local path you intend to redirect; use the root path only when the entire site should move.
- Select the offered redirect type appropriate to the change. A permanent move and a temporary maintenance destination have different caching and indexing implications.
- Enter the full destination URL, including
https://where supported. Review the hostname and path to avoid sending visitors to the wrong site. - Create the rule and test the source with a fresh browser session or an HTTP-header check. Review what happens to inner paths and query strings before applying a broad rule.
02 Example: move one help page
Suppose the old address is https://example.com/old-help and its replacement is https://example.com/help. Select example.com, enter /old-help as the local path, and use the full replacement URL as the destination. Choose a temporary redirect while checking the rule if that option is available; use a permanent redirect only when the move is confirmed permanent.
Test the exact old URL, the replacement URL and an unrelated page. The old URL should reach the replacement, the replacement should not redirect back, and the unrelated page should keep working. Check any nested paths and query strings used by real visitors before treating the rule as complete. Record the rule so it can be removed if a loop appears.
How do I test the website redirect?
Confirm the status, destination and final content, and check that login, checkout or other important paths still behave correctly. HTTPS on the source must work before a browser can follow its redirect without a certificate error.
Resolve setup problems
If a loop occurs, disable the new rule and compare application and CDN redirects. If a removed or changed destination persists, test outside the browser cache. Do not stack more redirects blindly or edit the whole server configuration for a single account path problem.