An addon domain is a separate website on your shared hosting account, with its own document root and content. An alias is simply another hostname that serves the same files as an existing site. A subdomain is a hostname under your main domain that points to its own folder. On LogicWeb shared hosting you manage all three in cPanel, and AutoSSL can issue a certificate for each name once public DNS points here.
What each option is for
Use an addon domain when you want a second full site under the same cPanel account. Give it its own folder outside the main site root so the two properties do not share one .htaccess file or fight over rewrites. An alias (sometimes called a parked domain) is for extra names that should show the same site, such as the bare domain and www, an old brand name, or a common misspelling. A subdomain is ideal for staging, apps, or a separate section of the brand, for example staging.example.com in its own directory with Directory Privacy and a noindex tag while you work.
DNS still has to point each name at your hosting. Point the A record (or use our nameservers ns1.logicweb.com and ns2.logicweb.com) so the hostname resolves publicly. After that, AutoSSL and Let’s Encrypt can issue a certificate per name. If AutoSSL stays red on an addon, check the A record first; it is usually DNS rather than a certificate authority problem.
Document roots and clean setup
Do not point a second addon at public_html unless you truly want two sites sharing one tree. Create a dedicated folder for the addon and install there once. Aliases should not get their own WordPress install; they load the same files as the primary site. Redirect www and the apex domain in one place so visitors do not bounce through a chain of hops.
Remove unused subdomain folders and old installs when you no longer need them. A leftover vhost with outdated software is an easy target. SFTP accounts can be limited to one addon folder so a contractor never sees your other sites. File Manager shows every tree when you log in as the main cPanel user, so confirm which folder you are in before you extract a zip or edit files.
Quick checklist before you go live
- Create the addon, alias, or subdomain in cPanel with the correct document root.
- Point DNS for that hostname to your account, then wait for propagation.
- Confirm AutoSSL issues a certificate for the new name.
- Install WordPress only on an addon or subdomain root, never on an alias.
- Set one clear redirect for www versus the apex domain.
- Delete staging or unused trees when the project is finished.
If something still fails after DNS is correct, open a ticket with the exact hostname and what you see in the browser. We can check the vhost, the document root, and AutoSSL from our side without needing root on shared hosting.
Tagged
Was this article helpful?
Be the first to rate this article.
