Back up the existing .htaccess file, including application-generated rewrite blocks. Identify the required directory and confirm the directive is supported by the server’s active web and PHP configuration.

1. Open Hosting Features > Htaccess, select the correct domain and log in to its directory-options view.
2. Choose the exact existing directory configuration or create the intended custom-directory configuration. Avoid a global-root change for a single preview folder.
3. Edit the relevant setting, such as access control or a redirect, and read how its order interacts with existing rules.
4. Save one change at a time. If adding custom text, preserve the panel’s and application’s managed blocks and use the supported placement.
5. Test both a request that should match and one that should remain unaffected. Review web-server logs if a 403, 500 or redirect loop appears.

The targeted behaviour should work without breaking application routes or unrelated domains. Keep a dated copy and brief explanation of each custom rule.

If a page fails immediately, restore the saved file and inspect syntax or unsupported directives. PHP settings suitable for one handler may fail under another. Do not replace the entire application .htaccess with a short example from an unrelated tutorial.

Only after checking inheritance and the application’s routing. A root-level setting can reach more paths than intended; choose a narrower directory when the requirement is local.

• Protecting a SiteWorx preview directory with a browser password
• Redirecting a SiteWorx website to HTTPS after certificate setup
• Following SiteWorx web-server logs during a reproducible error
• Deactivating a SiteWorx user while preserving the account

• InterWorx: Manage Advanced Settings .htaccess Siteworx