cPanel Addon Domain: How to Host Multiple Websites on One Account

What is a cPanel addon domain and what does it do?

A cPanel addon domain is an extra domain name you attach to a single cPanel hosting account, where it runs as a separate website from its own folder. It lets you publish a second or third site next to your main domain while sharing one control panel, one disk quota and one bill.

Think of your hosting account as an apartment and your main domain as the name on the door. An addon domain gives one room inside that apartment its own street address. When a visitor types example.net, they see the site in the folder you assigned to that domain, not your main site. As a result, you can launch a small campaign site, a second brand or a blog without opening a new account.

In this guide we walk through adding an addon domain, pointing DNS, setting up SSL and email, sharing resources and the security trade-off, all based on the official cPanel documentation. We are Talha Aslan and team, a digital marketing and web team, not a hosting company. So we verify every interface name against cPanel's own docs. Still, if your provider runs a different panel version, some labels may differ.

Who is this for? Business owners with several small sites, developers who manage their own cPanel account, and anyone deciding whether a new project needs its own account. We also explain, honestly, when a cPanel addon domain is the wrong choice. After all, every shortcut comes with a trade-off somewhere.

How is an addon domain different from a subdomain or an alias?

cPanel's Create a New Domain documentation defines three separate concepts. An addon domain is an additional domain the account owns, and the system stores each addon domain in its own configurable directory. An alias, formerly called a parked domain, is a second name that points to the main domain, so the same site opens under two addresses. A subdomain is a subsection of a website, such as blog.example.com.

In short, use an addon domain when you want different content. Instead, use an alias when you want the same content under another name. If you need a separate user and separate limits, move to the last row of the table: a separate account.

What do you need before adding a cPanel addon domain?

Not every cPanel account can add domains. According to cPanel's documentation, your hosting provider must enable the relevant feature in WHM's Feature Manager before you can create a new domain. In addition, your package needs an addon domain quota. The new domain screen also shows your account's quota status.

Before you start, check the following:

• You own the domain and it is registered with a registrar. cPanel cannot register or renew domains.
• You can edit the domain's DNS, either at the registrar or at a separate DNS provider.
• Your package still has addon domain slots left.
• The same domain does not already exist in another account on the server.
• Your disk and inode quota has room for another site.

For example, entry level shared plans may include no addon domains at all, or only a handful. If the plan description does not say, then ask your provider. Guessing usually ends in a half finished setup.

Finally, if you have not bought the domain yet, cPanel's Temporary Domain option lets you start building on a provisional address. However, the documentation notes that temporary domains do not support DNS editing, email or SEO features. So it does not replace a real cPanel addon domain setup.

How do you add a new domain in the Domains interface?

In current cPanel versions you no longer use a separate Addon Domains screen. Instead, you use the Domains interface. The official steps look like this:

1. On the cPanel home page, open Domains under the Domains section.
2. Next, click Create a New Domain.
3. Select Registered Domain and type the domain in the Domain box, for example example.net.
4. Uncheck Share document root. Otherwise the new domain serves the main site's content.
5. Review the folder in the Document Root box, or change it to match your own structure.
6. Click Submit.

Per the docs, when you uncheck Share document root and set a separate directory, the system creates an addon domain. The interface then fills in the remaining boxes for you, and cPanel recommends that you keep those values. The system also creates an associated subdomain automatically. You can list these from the gear icon in the domains table with Show Associated Subdomains. We also come back to that automatic subdomain in the SEO section.

How should you choose the document root folder?

The document root is the folder that holds the files visitors see for a domain. According to cPanel, you cannot create a document root outside public_html. You also cannot use system folders such as mail, ssl, tmp, logs, etc or cgi-bin as a site folder.

Here are a few simple naming rules our team recommends:

• Name the folder after the domain itself, for example public_html/example.net. So you never have to guess which folder belongs to which site.
• Keep addon folders apart from the main site's files. Then a cleanup job on the main site cannot wipe another site by accident.
• Use Share document root on purpose only. The documentation states plainly that this setting is permanent.

To change the folder later, use the New Document Root box on the Manage screen. Note the important warning in the docs, though: the server does not move your files. Instead, it simply starts looking in the new folder. Therefore you have to move the files yourself. You also cannot change the main domain's document root from this screen.

How do you point the domain's DNS to your hosting?

Adding the addon domain in cPanel is only half the job. The domain's public DNS also has to point at this server. You have two ways to do that: change the nameservers or set an A record.

With the nameserver method, you switch the domain's nameservers at your registrar to the ones your hosting provider gives you. You then manage the DNS zone from cPanel's Zone Editor. This is usually the least effort, because cPanel sets up the website, email and SSL validation records in one zone.

With the A record method, you keep DNS at your current provider and only point the web records to the hosting server's IP. For example, a zone could look like this. The IP comes from a block reserved for documentation:

example.net.       3600  IN  A      203.0.113.10
www.example.net.   3600  IN  CNAME  example.net.

If you also want email on this server, you need to set the MX records separately with this method. Do not guess the IP address or record values; use the ones your hosting provider gives you. After you save the records, check with our DNS lookup tool that the A, CNAME and MX records return what you expect.

How long does DNS propagation take, and why is there a delay?

DNS changes do not reach everyone at once. The cPanel documentation says changes to DNS records may take two days or more to reach every nameserver on the internet. In practice, people call this DNS propagation.

The main reason for the delay is caching. Every DNS record has a TTL value, and resolvers keep the record for that long. In other words, some users can still get the old record for a while. Nameserver changes often take longer still, because the records at the top level domain side get cached as well.

While you wait, keep these points in mind:

• If you are migrating, do not shut down the old hosting right away. Instead, let both servers run in parallel for a while.
• Lowering the TTL before a change makes later switches faster.
• If you still see the old site, remember your browser and operating system caches too.

That said, if the problem lasts beyond two days, stop blaming propagation and look for a wrong record. If the domain returns an NXDOMAIN error, the nameserver setting or registration status at the registrar is the more likely cause.

How do you get a separate SSL certificate for each addon domain?

According to cPanel, when you create a domain the system first tries to secure it with an existing certificate. If none fits, it generates a temporary self signed certificate. If your provider enabled AutoSSL on your account, the system also queues an AutoSSL request for the new domain and installs the certificate once it is available.

The key step here is validation. AutoSSL needs proof that the domain really points at this server. cPanel's SSL/TLS Status screen lists domains that do not resolve to an IPv4 address on the internet under the Has AutoSSL Problems filter. As a result, the certificate may not arrive until DNS propagation finishes.

Also check for CAA records. If the zone has a CAA record, it limits which certificate authorities may issue certificates for the domain, and a conflicting entry can block AutoSSL. Once the certificate is in place, use the Force HTTPS Redirect toggle in the domains list to send visitors to HTTPS. The docs also note that this toggle does not appear for aliases.

After setup, use our SSL checker to confirm the certificate covers both example.net and www.example.net. For certificate types and why HTTPS matters, see our SSL certificate guide.

How do you set up email for an addon domain?

On the email side, an addon domain is an independent domain too. Each domain in the list has a Create Email action, and it takes you to the Email Accounts screen. Then you create addresses such as info@example.net.

For email to work, the domain's MX record has to point to this server. With the nameserver method, cPanel usually sets this up for you. With the A record method, however, you have to add the MX record at your external DNS host. On top of that, SPF and DKIM records help keep your outgoing mail out of spam folders.

There is also one more detail. Every domain in a single account shares the same disk quota. So one site's bloated mailbox can stop the other sites from uploading files. For that reason, we recommend a quota on every mailbox. Also, cleaning out unused mailboxes on a schedule keeps the shared quota from filling up quietly.

For business email, you may prefer a dedicated email service over cPanel mailboxes. We also compare the options in our custom domain business email guide.

How do sites on one account share its resources?

The biggest upside and the biggest downside of an addon domain come from the same place: everything lives in one account. Disk space, the inode (file count) quota, monthly bandwidth and, where your provider enforces them, CPU, memory and process limits all apply at the account level. Consequently, five sites share the limits of one.

In practice, this means:

• A traffic spike on one site can slow down the others.
• A runaway cache or log folder can fill the disk quota for the whole account.
• If the provider throttles the account for exceeding limits, all five sites feel it.
• You can pick a PHP version per domain, yet server resources stay shared.

For example, if an online store gets heavy traffic during a sale, the company profile site in the same account takes part of that load. Therefore it is safer to run revenue sites with spiky traffic in their own account, not as addons. To set PHP versions per site, our cPanel PHP version guide covers it step by step.

If one site gets hacked, are the other sites in the account at risk?

Yes, most likely, because addon domains run under the same cPanel user. In other words, every site's files belong to the same Linux user. An attacker who gets in through an outdated plugin on one site can read and change the other folders with the same permissions.

For instance, WordPress stores database credentials in wp-config.php. A compromise on one site in the account can expose the database passwords of the other sites as well. During cleanup, you have to scan every site in the account, not only the one that got hit.

Separate cPanel accounts, on the other hand, are separate Linux users. If your provider uses account isolation such as CageFS, accounts cannot see each other's files. Still, that isolation works between accounts; it does not separate addon sites inside the same account. We also cover this in detail in our CageFS and account isolation article.

Put simply, keep only sites with the same trust level in one account. In practice, the risk may be acceptable for your own small side projects. For client sites, stores that take payments and forms that collect personal data, a separate account is far healthier.

How do you install WordPress on multiple addon domains?

You can install a separate WordPress site on each addon domain, and the cleanest approach is to give each site its own database. The order goes like this:

1. Add the addon domain and note its document root.
2. Create a new database and a separate database user in Manage My Databases or the Database Wizard.
3. Then upload the WordPress files only to that addon domain's folder.
4. Enter this site's own database details on the install screen.
5. Use a separate admin account and a strong password on each site.

If your provider offers an auto installer such as Softaculous, simply pick the addon domain as the target during install; the tool creates the database for you. These tools also make it easier to track updates.

If you want to manage very similar sites from one dashboard, WordPress Multisite is another option. However, Multisite means one install, one database and a shared plugin pool, so a single error can affect the entire network. For simple needs, separate installs cause fewer surprises.

Also, do not forget backups. Because addon folders sit inside public_html, the main site's backup plugin may include them and bloat the archive. For a separate, tested backup plan per site, read our website backup strategy guide.

Does using a cPanel addon domain hurt SEO?

No, using a cPanel addon domain does not cause an SEO penalty or a ranking drop on its own. Search engines evaluate a site by its domain; which account or folder it lives in is not a ranking factor. Sharing a server IP with other sites is also normal on shared hosting.

The real risk is a technical side effect. Since the addon folder sits inside public_html, the same content can load from more than one address:

• example.net, the address you actually want.
• A folder path under the main domain, such as example.com/example.net/.
• The associated subdomain that the system created automatically.

Google treats several URLs that lead to the same content as duplicates and picks one as canonical. Google Search Central's guide on consolidating duplicate URLs recommends signals such as 301 redirects and rel=canonical to show which URL you prefer. This is not a penalty. That said, if you do not state a preference, the search engine chooses for you.

We explain how canonical tags work in our canonical tag guide. Next, we show how to close those extra addresses.

How do you close the extra addresses with a 301 redirect?

The most reliable fix is a host check in the .htaccess file inside the addon domain's own folder. On servers running Apache with mod_rewrite, the example below permanently redirects any request that arrives under a host other than example.net:

RewriteEngine On
RewriteCond %{HTTP_HOST} !^(www\.)?example\.net$ [NC]
RewriteRule ^(.*)$ https://example.net/$1 [R=301,L]

Because these rules live in the addon folder, they only affect requests for that folder. So both the folder path and the automatic subdomain end up at the real address. If you run WordPress, add the rules above the # BEGIN WordPress line.

Before going live, check the following:

• Does the example.net home page load without a loop?
• Does the folder path reach the real address in a single 301 hop?
• Do the HTTPS redirect and this rule avoid triggering each other?

You can see every hop with our redirect checker. If your server runs a web server other than Apache, ask your provider how to adapt this rule.

What should you do when your plan's addon limit is full?

According to cPanel's documentation, your hosting provider decides how many addon domains you can add. Once you hit the limit, the Domains interface will not let you create a new domain and shows your quota status. At that point you have three options.

First, you can upgrade to a plan with more addon slots. Make sure disk, process and memory limits grow at the same rate, though. Otherwise you just squeeze more sites into the same tight resources.

Second, you can clean up addon domains you no longer use. Expired campaign sites, or domains that do nothing but redirect, take up slots for no reason. Moreover, a domain that only forwards to the main site works better as an alias than as an addon.

Third, you can split sites into separate accounts. You can do that by buying separate plans or by using a reseller hosting account. We cover which path fits in the decision section below.

How do you remove or rename a cPanel addon domain?

You remove a domain from the Manage screen in the domains list with a few clicks, yet you should understand the consequences before you confirm. The cPanel docs strongly recommend a full account backup before removing a domain. The steps: click Manage, choose Remove Domain and confirm with Yes, remove this domain.

So what goes away and what stays? Per the documentation, this action only removes the domain's vhost entries and DNS entries. The folder and its files stay on the server. Email accounts disappear from the Email Accounts screen; however, the mail folders remain, and the accounts come back if you add the domain again.

Therefore, if you actually want to free up space, you need to clean the folder, the database and the mail folders separately after removal. Before you do, download a backup and confirm that it opens.

Renaming is a newer feature. The Rename Domain action on the Manage screen works for main, addon and parked domains, but not for subdomains. The system updates email accounts, DNS records and the document root to the new name. Even so, you still need to update absolute URLs inside the site and the site address in WordPress settings yourself.

When does a separate cPanel account or reseller hosting make more sense?

An addon domain is a practical fix for small sites that belong to the same owner and trust each other. In some cases, though, convenience should not outweigh risk. A separate account or reseller hosting is the better choice when:

• The sites belong to different clients or different companies.
• One of the sites takes payments or processes personal data.
• One site's traffic swings slow down the others.
• Each site needs its own panel login and its own invoice.
• A site may be moved, sold or handed over in the future.

For example, if an agency or freelancer keeps client sites as addons in their own account, every handover turns into a messy untangling job. Reseller hosting, on the other hand, lets you open a separate cPanel account for each client. That way limits, backups and security boundaries split cleanly per account. For details, read our cPanel reseller hosting guide.

In short, if the sites share an owner and none is critical, an addon is enough. If ownership or risk differs, split the accounts too. Making that call early is also much cheaper than moving sites between accounts later, when you go through DNS, SSL and email all over again.

Which tasks should you leave to your hosting provider?

The cPanel interface makes adding a domain easy, but you cannot fix every problem from the panel. In the following cases we recommend opening a support ticket instead of digging in yourself:

• The Domains interface does not show up, or the Create a New Domain button is inactive. The feature may be off in WHM.
• You cannot add the domain because it already exists in another account on the server.
• AutoSSL keeps failing for days even though DNS looks correct.
• You need to change records you cannot see in Zone Editor. The cPanel docs tell you to contact your provider in this case.
• Account limits keep maxing out and you cannot tell which site uses them.

Also, if you suspect a hack, only the provider can see the server level logs. In that case, alert the support team right away. We explain how to judge that support quality when picking a host in our guide to choosing web hosting.

What should you check after setup?

Once the addon domain is live and DNS has propagated, wrap up with a short checklist:

1. Do example.net and www.example.net open the right site?
2. Does the certificate cover both addresses, and is Force HTTPS Redirect on?
3. Do the folder path and the associated subdomain 301 to the real address?
4. Can the email account both send and receive?
5. Is the site's database and user tied to this site only?
6. Does your backup plan include the new site?
7. Did you add a separate Search Console property for the new domain?

These seven points prevent most of the problems that could show up later. If you need help building a new site, migrating an existing one or cleaning up search visibility, reach us through our web design services and SEO consulting pages. For the latest interface labels, keep cPanel's Create a New Domain and Manage the Domain docs as your reference.