Before you begin
You need an active hosting plan, control of the domain's DNS, the website files or chosen application, and any database export required by the site. Decide the document root before uploading anything. If replacing a live website, also record its current DNS records and lower their time to live in advance when possible.
1. Create the site mapping
Attach the complete domain or subdomain and assign a dedicated relative document root such as www or shop. Do not reuse a non-empty root unless the new site is meant to replace its contents. Attaching the domain does not change its registration, nameservers or public DNS.
2. Prepare the runtime and database
Choose a PHP version supported by the application. Create a database if the site needs one and save its hostname, name, username and password in your password manager. Import application data before public traffic is moved, then verify the application can both read and write through the database connection.
3. Publish the website
Upload the site through SFTP, deploy the reviewed Git branch, publish from Site Studio, or install one supported application into the empty document root. Do not mix publishing methods in the same root. Before changing DNS, use a temporary hostname or local hosts-file override when available to test the homepage, administration login, forms, media and a representative dynamic page.
4. Point DNS to the hosting
Publish the exact A and, when used, AAAA records shown for the hosting. A subdomain may use an appropriate CNAME when the DNS design permits it. You do not need to transfer the domain or replace its nameservers simply to host the website. Keep old hosting available until public DNS checks resolve to the new destination.
5. Enable and verify HTTPS
Enable TLS for every hostname that visitors will use, including the www variant when applicable. Wait until certificate coverage is confirmed, open each hostname over HTTPS and only then enable a permanent HTTP-to-HTTPS redirect in the application or .htaccess file. Check for mixed-content warnings and redirect loops.
6. Complete the launch checks
Test from a second network or device, submit every important form, verify outbound application email, inspect a missing-page response and confirm the application administrator still works. Create a fresh database dump and file copy after launch, document any cron jobs, and keep the previous recoverable version until the new site has operated normally.
