How do You Create Subdomains in cPanel?
When you create a subdomain in cPanel, you will be asked to choose the name of the subdomain, the domain the subdomain is for and the location from which the new subdomain will load it's content.
Note: Some subdomain names are reserved: mail, www, ftp, cpanel, whm, webmail, webdisk. You can use any name except these.
How do I create a subdomain (something.yourdomain.com)?
- Log into cPanel and click on the "Subdomains" icon.
- In the "Subdomain" field, please select the name of the subdomain which you wish to use, for example, you might choose "blog". If you choose blog, then your subdomain will look like "blog.example.com".
- Next, select the desired domain you wish to create this subdomain for from the drop down menu to the right of the "Subdomain" field. You may create a subdomain for any addon, parked or subdomain that already exists in your cPanel.
- When you click on the "Document Root" field, it should automatically populate with a cPanel suggested location from which the subdomain will load it's content. For instance, if you chose "blog" as your new subdomain, then the "Document Root" field will populate with "/public_html/blog". This means that the new subdomain will load it's content from the folder named "blog" from within the "public_html" directory.
- Once all three fields are set the way you prefer, simply click on the "Create" button to complete the creation of your new subdomain.
NOTE: When you've completed these steps, you must contact us and let us know what subdomain you've setup because we have to update our internal DNS tables in order for it to take effect. This process will take from 1-4 hours to propagate.
If you have addon or parked domains that you wish to have the same subdomain name for, but wish for those subdomains to load different content, then you must pay close attention to the "Document Root" field. For example, if you own several domains and wish to have a different blog set up for each domain that loads from the subdomain name blog, then you will have change the "Document Root" of each domain that you set up. This is very important because if you create blog.yourdomain.com and blog.yourotherdomain.com on the same cPanel server, but leave the "Document Root" as the cPanel suggested location, then both of your blog subdomains will load from the same directory of "/public_html/blog" and you will not have separate content for each subdomain.
To avoid experiencing this issue, when you create your new subdomain, make sure you set the "Document Root" to something other than "/public_html/blog", instead, set it to something like "/public_html/blog1". If you have done this correctly, then you will have more than one domain using "blog" as a subdomain, but both subdomains will be loading separate content.
IMPORTANT SEO INFORMATION: We've seen a lot of people setup subdomains for sites they were just starting out but after a while they discovered that Google or other search engines started to send them a lot of traffic. So they decided they wanted to setup the site with its very own new domain. BUT, doing this comes with a huge risk that they may no longer be so highly ranked in Google or other search engines. For instance, when using a subdomain, the URL to their content might look something like this: http://blog.yourdomain.com/pages/pages-google-really-likes.php. But, when they move the site to its own domain, the new address will be: http://yourNEWdomain.com/pages/pages-google-doesnt-like-anymore.php.
When you move a site from a subdomain (or addon or parked domain), the address to each page changes. And this change often is not welcomed by Google! Therefore, we recommend only using subdomains (addon and parked domains), for pages and sites that you will never want to become popular.
Was this answer helpful?
AUTOMATED SETUP: First, you should know that cPanel provides a feature that may be able to setup...
To create an email account:Login to cPanel by going to YourDomain.com/cpanel - and...
First, login to your cPanel control panel by going to YourDomain.com /cpanel. Like almost...