THE CONNECTIONS BEHIND YOUR BUSINESS
Getting Started with cPanel Hosting
Set up your hosting account, document root and first website safely, without disrupting existing email.
New to cPanel hosting? This guide walks through the website directory, first upload, domain connection and checks that help you get started without disrupting existing email.
Start here: a new site or an existing business?
For a new site, set up the account and test it before pointing your domain. For a working business, first inventory the existing website and email. Buying hosting does not automatically move either service, and changing nameservers can affect both.
Have your provider’s account welcome information ready. Sign in through your secure customer portal; do not follow an unexpected email asking for your password. Never publish cPanel credentials or a screenshot containing account secrets.
1. Find the correct website directory
Open Domains in cPanel and locate your domain’s document root. It might be public_html, or a separate folder for that domain. Use the displayed path rather than assuming every site belongs in the same directory.
Open File Manager and select that document root. Before replacing files, download a copy and confirm that a usable database backup exists for a database-driven site. An account can contain several websites: deleting the wrong folder can affect another business.
2. Choose the right installation
- Static HTML or Astro: upload the built website output, with its
index.htmlat the correct root. Do not upload development dependencies or secrets. - WordPress or another CMS: follow the application’s supported installation and database requirements. Availability of an installer depends on your hosting account.
- Existing website: use a migration plan rather than installing over the old copy.
An index.php and index.html in the same folder can create ambiguity. Ask the provider which file Apache serves first before removing either. Do not alter shared .htaccess rules without a backup and a reviewed reason.
3. Connect the domain and HTTPS
Use the host’s exact DNS instructions. If email stays elsewhere, preserve its MX, TXT, Autodiscover and relevant host records. A website-only A-record change is different from moving nameservers.
Map the domain in hosting, configure its certificate, then test HTTPS with the real hostname. A temporary preview address may not reproduce application links, cookies or certificate behavior. Do not bypass a certificate warning to enter account credentials.
4. Check the first page and its dependencies
Open the home page and at least one internal page. Check images, CSS, JavaScript, forms and mobile navigation. For a safe, read-only response check on Windows:
curl.exe -I --max-time 15 https://your-domain.example/Expect a successful response or an intentional redirect to the canonical HTTPS hostname. A 403, 404 or 500 needs investigation: check document root, default index, permissions and application errors. A successful header alone does not prove the page renders or forms work.
Keep administration routine
Use unique credentials and available MFA, keep application software maintained, and arrange restorable backups outside the hosting account. File permissions should follow the provider’s guidance; do not use 777 as a troubleshooting shortcut.
If something breaks, restore only the files or settings changed in this step. Avoid a whole-account restore when a small, identified correction will do.
Official references
Documentation checked 2026-10-18. Examples use reserved names and addresses; replace placeholders only for systems you are authorized to manage. Interfaces and included features depend on your provider and account.