Introduction #

In this doc you will learn more about managing your website within the cPanel enviorment. This can be helpfull when you manage more sites in 1 cPanel account, when making changes to your website through it’s files, or when uploading a custom website to your cPanel account.

---

Hosting Multiple Websites in One Account #

Web Hosting and Site Hosting can allow multiple websites to be managed under a single hosting account. In this setup, each website is linked to its own domain or subdomain and uses its own document root, while still sharing the same overall hosting environment.

This makes it possible to manage several websites from one account, but it also means the structure should be kept organised. Each website should be clearly separated so that files, settings, and databases do not become mixed.

How Multiple Websites Work #

When multiple websites are hosted in one account, each site normally has:

• its own domain or subdomain
• its own document root
• its own website files
• its own database, if the site uses dynamic software

Even though the websites are separate in structure, they still share the same hosting account and the same available resources.

Addon Domains and Subdomains #

A common way to host multiple independent websites is by using addon domains. An addon domain links an additional domain to the hosting account and assigns it its own folder, allowing it to function as a separate website within the same environment.

Subdomains work differently, but can also be used for separate website sections or projects. A subdomain is created under an existing domain, such as blog.yourdomain.com, and can also use its own document root.

In both cases, the website has it’s own clear folder structure so that content stays organised.

File and Database Separation #

When managing multiple websites, it is good practice to keep each site as separate as possible. This means using a dedicated document root for each website and avoiding unnecessary file sharing between sites unless there is a clear reason to do so.

For websites that use databases, separate databases and database users are also recommended. This improves organisation, reduces risk, and makes troubleshooting easier if a problem affects only one site.

Email and DNS #

Each connected domain can have its own DNS records and, where included, its own email-related setup. These are managed per domain rather than as one shared website setting. This means changes to one domain generally do not automatically affect the others.

Shared Resources #

Although websites may be separated by domain, files, and databases, they still share the same hosting account resources. This includes things such as storage, processing capacity, and package limits.

As a result, one poorly optimised or heavily used website can affect the overall performance of other websites in the same account. For that reason, hosting multiple websites in one account works best when the environment is kept organised and each site is managed carefully.

---

Understanding the Document Root #

The document root is the folder from which a domain or subdomain serves its website files. In simple terms, it is the location the server checks when someone visits that website in a browser. Only files inside that assigned folder are publicly served through that specific domain or subdomain.

Understanding the document root is important when uploading, editing, or troubleshooting a website, because files must be placed in the correct location to appear online.

What the Document Root Does #

The document root determines where a website starts within the hosting account. It links a domain or subdomain to a specific folder and tells the server which files should be used when requests come in for that address.

When a visitor opens a website, the server reads the files from the document root assigned to that domain. If the files are uploaded to the wrong folder, the website may not load as expected even though the files exist somewhere else in the account.

Common Document Root Locations #

The exact folder depends on how the domain is configured, but common examples include:

• public_html for the primary domain
• public_html/subfolder for an additional domain
• a separate assigned folder for a subdomain

The primary domain usually uses public_html as its main document root. Files placed in that folder are normally served when someone visits the main domain.

Additional domains and subdomains can use different document roots. In many cases, an addon domain points to its own subfolder, while a subdomain may be assigned its own folder during setup. The important part is that each website must use the folder assigned to its own domain or subdomain.

Why the Correct Folder Matters #

When managing a website, files should always be uploaded to the document root that belongs to the site you want to change. Uploading files to the wrong folder is a common reason why website changes do not appear online or why the wrong content is shown.

This is especially important when multiple websites or subdomains exist within the same hosting account, because each one may point to a different location.

Index Files #

Inside the document root, the server usually looks for a default index file such as index.html or index.php. This file acts as the starting point of the website.

If no valid index file exists in the document root, the website may show an error, display a directory listing, or appear blank depending on the server and site configuration.

---

Uploading Your Website (Files) #

If you already have a website that was created elsewhere, you can upload its files to your ProRedLine hosting account to make it available online. This is mainly relevant for manually built websites, migrated websites, or projects that were prepared outside of cPanel.

This is not required for every website setup. For example, if you install WordPress through WP Toolkit, the basic website structure is created automatically and you do not need to upload the full site manually in the same way.

To publish a manually prepared website, the files must be uploaded to the correct document root of the domain or subdomain that should load the site. Files uploaded outside the correct document root will not be publicly accessible through the browser.

In most cases, website files can be uploaded using either the File Manager in cPanel or a secure FTPS connection. Both methods place files on the same hosting account, but they are typically used in different situations. File Manager is usually more practical for smaller uploads, quick edits, or simple changes, while FTPS is generally the better option for larger websites, larger numbers of files, or repeated uploads.

Because the full explanation of these tools is covered elsewhere, it is best to refer to the dedicated file management documentation for more detailed guidance on:

• File Manager,
• FTPS,
• Web Disk,

here: File Management Tools

Whatever upload method is used, the most important part is making sure the files are placed in the correct document root and that the main website files are present there. After the upload is complete, the website should be tested in the browser to confirm that the expected content is loading correctly.

Common problems after uploading are usually caused by files being placed in the wrong folder, missing index file, missing extracted content, or the website expecting additional configuration such as a database or updated settings. If the files have been uploaded correctly but the website still does not load as expected, the next step is usually to review the site structure and configuration rather than the upload method itself.