Confirm the parent domain is managed in the correct account and the service permits another subdomain. Decide which folder will contain the site, and avoid reusing a production folder unintentionally.

1. Open Hosting Features > Domains > Subdomain and choose the add control.
2. Enter the subdomain prefix and choose the correct parent domain. Review the complete hostname before adding it.
3. After creation, inspect the subdomain’s document root. Use its edit action if you need an approved custom path or a PHP setting different from the inherited parent setting.
4. At the authoritative DNS provider, add or verify the required record. If DNS is hosted elsewhere, make the change there rather than assuming the local zone is public.
5. Upload content into the assigned folder and arrange a certificate covering the new hostname before directing visitors to HTTPS.

Check public DNS, then visit the subdomain over HTTPS and confirm it serves the correct application. Verify the parent website still behaves normally.

For a project at preview.example.com, decide first whether it should show its own files or the same content as another hostname. Choose a document root that matches that intention and record it before uploading anything.

Creating the subdomain in SiteWorx and making it resolve publicly can involve separate steps, particularly when DNS is hosted elsewhere. Check the authoritative DNS provider and add the required record there rather than changing an unused local zone.

How should I test the new subdomain?

Use a harmless test page in the assigned document root, verify the hostname reaches it and then configure the application. Check HTTPS before collecting credentials or customer information. Remove the temporary test page once the real site is ready.

For a staging or preview site, prevent public access or indexing using suitable application and server controls. Merely giving it a name containing preview does not make it private. Contact us with the subdomain, intended content location and DNS provider if you are unsure which layer is incomplete. Do not move the main website's files into a new folder just to make the preview hostname respond.

If the subdomain shows the parent site, compare its document root and DNS destination. If it fails certificate validation, resolve DNS and reachability first. Deleting and recreating the hostname repeatedly is unlikely to fix an external DNS problem.

• Removing a SiteWorx subdomain after retiring its website
• Adding a secondary domain to SiteWorx
• Uploading website files with SiteWorx File Manager
• Changing a SiteWorx subdomain’s document root

• InterWorx documentation