cPanel Addon Domains vs Subdomains: How to Add Each

If you're running more than one site under a single hosting account, you've probably hit this fork in the road: do you add an addon domain or a subdomain? They look similar in cPanel and both end up serving a separate site, but they behave differently in ways that matter for SEO, DNS, and SSL. Here's how to tell them apart and add each one correctly.

Addon Domain vs Subdomain: What's Actually Different

Both let you host a second website inside the same cPanel account, and both create a new folder under public_html. The real difference is what the outside world sees.

• Addon domain — a completely separate, registered domain (say mysecondbrand.com) hosted from your existing cPanel account. Visitors see the new domain in the address bar with no trace of your primary domain. It needs its own nameserver or A record pointing at your server.
• Subdomain — a prefix on your existing domain (say shop.yourprimarydomain.com). It's part of the same domain's DNS zone, so it inherits the parent domain's nameservers automatically. No separate registration needed.

Rule of thumb: if you bought a brand-new domain name for it, it's an addon domain. If it's a section of a domain you already own, it's a subdomain.

Before You Start: What You'll Need

• cPanel login (Domains section — older themes call it "Addon Domains" and "Subdomains" separately).
• For an addon domain: the domain registered and, ideally, its nameservers already pointed at Getwebup, or you'll be adding an A record manually.
• A rough idea of where the new site's files should live — cPanel will suggest a folder, but you can change it.

How to Add an Addon Domain in cPanel

1. Log in to cPanel and open Domains.
2. Click Create A New Domain.
3. Enter the full domain, e.g. mysecondbrand.com. Leave "Share document root" unchecked unless you specifically want it to reuse an existing folder.
4. cPanel auto-fills a document root like /home/username/mysecondbrand.com. You can rename it, but keep it inside public_html unless you have a reason not to.
5. Click Submit. cPanel creates the folder, sets up a subdomain-style DNS entry inside your account, and (if the domain's nameservers already point to Getwebup) it starts resolving immediately.

If the domain's nameservers point elsewhere — GoDaddy, Namecheap, wherever it was registered — you have two options: switch the nameservers to Getwebup's, or add an A record at the current registrar pointing to your server's IP. Check your server's IP from cPanel's home page under "Shared IP Address" or your VPS dashboard.

How to Add a Subdomain in cPanel

1. In cPanel, open Domains and click Create A New Domain (same tool handles both — cPanel figures out it's a subdomain because you're using an existing domain).
2. Type just the prefix, e.g. shop, and select the parent domain from the dropdown, or type the full shop.yourprimarydomain.com.
3. Set the document root, e.g. /home/username/public_html/shop.
4. Submit. Because the subdomain lives under your existing domain's zone, DNS is created automatically on Getwebup's nameservers — there's usually nothing to configure at the registrar.

Propagation for a subdomain is nearly instant if your domain already uses Getwebup's nameservers, since it's just a new record in a zone that's already live.

Common Mistakes That Break Addon Domains and Subdomains

DNS not pointed correctly

The single most common issue: the addon domain shows a parking page, a "site can't be reached" error, or someone else's site entirely. That's almost always a DNS problem, not a cPanel problem. Run dig mysecondbrand.com or check dnschecker.org — if it's not resolving to your server's IP, fix the nameservers or A record at the registrar first. Give it 15–30 minutes for a fresh A record, longer if you just switched nameservers.

SSL not issued for the new domain

AutoSSL runs on a schedule (usually every 12 hours) and needs the domain to already resolve correctly before it can validate ownership and issue a certificate. If you just added the domain and it's showing "Not Secure," don't panic — go to SSL/TLS Status in cPanel and click Run AutoSSL manually once DNS has propagated. It won't succeed while the domain still points elsewhere.

Wrong document root

If you upload your site files to public_html instead of the addon domain's actual folder (e.g. public_html/mysecondbrand.com), the new domain will either show your primary site or a blank directory listing. Double-check the path in Domains before uploading anything — it's listed right next to the domain name.

Migrating an Existing Site to an Addon Domain

If you're moving a site you already run elsewhere onto this cPanel account as an addon domain:

1. Create the addon domain first (as above) so the folder and DNS zone exist.
2. Upload files via File Manager or FTP into the addon domain's document root — not public_html.
3. If there's a database, create it under MySQL Databases, import the .sql file via phpMyAdmin, and update the site's config file (e.g. wp-config.php) with the new database name, user, and password.
4. Only switch the domain's nameservers or A record to Getwebup once the files and database are in place and you've tested via a temporary hosts-file edit or the server's shared IP with a Host header. This avoids visitors hitting a half-set-up site mid-migration.

Prevention: Keep Multiple Sites Organized

A few habits save real headaches once you're managing three or four sites in one account:

• Name folders after the domain, not a project codename — six months later you won't remember which folder is which.
• Keep each site's database credentials in that site's own config file only; don't share one database user across multiple sites unless you mean to.
• Note down each addon domain's document root somewhere outside cPanel — a password manager note or a shared doc — so anyone on your team can find it fast.
• If a site is going to get real traffic, consider giving it its own cPanel account instead of stacking it as an addon domain. It isolates resource usage and makes backups cleaner.

Addon domains and subdomains both do the job of running multiple sites from one account — the trick is matching the right tool to whether you're dealing with a brand-new domain or a section of one you already own, and getting DNS and the document root right the first time.