{"id":115,"date":"2026-06-08T21:32:42","date_gmt":"2026-06-09T04:32:42","guid":{"rendered":"https:\/\/cpanelreview.com\/?p=115"},"modified":"2026-06-08T21:32:42","modified_gmt":"2026-06-09T04:32:42","slug":"setup-manage-subdomains-cpanel-guide-2","status":"publish","type":"post","link":"https:\/\/cpanelreview.com\/index.php\/2026\/06\/08\/setup-manage-subdomains-cpanel-guide-2\/","title":{"rendered":"How to Set Up and Manage Subdomains in cPanel: A Complete Guide for Hosting Multiple Sites"},"content":{"rendered":"

If you manage a cPanel hosting account, subdomains are one of the most powerful features at your disposal. They let you run multiple independent websites, web applications, or test environments under a single domain \u2014 without needing separate hosting plans. Whether you’re setting up a blog at blog.yoursite.com<\/code>, a client portal at portal.yoursite.com<\/code>, or a staging environment for development work, subdomains give you the flexibility to organize everything under one roof.<\/p>\n

In this guide, you’ll learn exactly how to create, configure, and manage subdomains in cPanel. We’ll cover the underlying DNS mechanics, folder structure best practices, common pitfalls like redirect loops and SSL issues, and how to use subdomains with addon domains so you can get the most out of your hosting account.<\/p>\n

<\/p>\n

What Are Subdomains and How Do They Work?<\/h2>\n

A subdomain is a prefix added to your primary domain name. Instead of visiting yourdomain.com<\/code>, visitors go to subdomain.yourdomain.com<\/code>. Technically, it’s still part of the same domain, but cPanel treats it as its own website with its own document root folder.<\/p>\n

When you create a subdomain in cPanel, two things happen automatically:<\/p>\n

    \n
  1. A new folder is created<\/strong> inside your public_html directory (by default, named after the subdomain)<\/li>\n
  2. A DNS record is added<\/strong> \u2014 typically a CNAME or A record pointing the subdomain to your server’s IP address<\/li>\n<\/ol>\n

    For example, if you create dev.yourdomain.com<\/code>, cPanel will create a folder at public_html\/dev<\/code>. When someone visits dev.yourdomain.com<\/code>, the server knows to serve files from that folder instead of the main public_html<\/code>.<\/p>\n

    How to Create a Subdomain in cPanel<\/h2>\n

    Creating a subdomain takes less than a minute. Here’s the step-by-step process:<\/p>\n

      \n
    1. Log into cPanel<\/strong> \u2014 your hosting provider will send you the URL (usually https:\/\/yourdomain.com\/cpanel<\/code> or a dedicated URL like https:\/\/server.hosting.com:2083<\/code>)<\/li>\n
    2. Navigate to Domains section<\/strong> \u2014 look for the Subdomains<\/strong> icon under the Domains category<\/li>\n
    3. Enter the subdomain name<\/strong> \u2014 type the prefix you want (e.g., blog<\/code>, shop<\/code>, docs<\/code>) in the Subdomain field<\/li>\n
    4. Select the main domain<\/strong> \u2014 choose the parent domain from the dropdown (if you have multiple domains registered in cPanel)<\/li>\n
    5. Set the document root<\/strong> \u2014 by default, cPanel suggests public_html\/subdomain<\/code>. You can change this to any path you prefer, like public_html\/apps\/blog<\/code> for better organization<\/li>\n
    6. Click Create<\/strong> \u2014 cPanel will create the folder and add the necessary DNS entries<\/li>\n<\/ol>\n

      After creation, DNS propagation can take anywhere from a few minutes to 24-48 hours depending on your domain’s TTL settings. During this time, the subdomain may not be immediately accessible from all locations.<\/p>\n

      Verifying DNS Propagation<\/h3>\n

      To check if your subdomain’s DNS has propagated, open a terminal and run:<\/p>\n

      dig blog.yourdomain.com +short\n\n# Or using nslookup\nnslookup blog.yourdomain.com<\/code><\/pre>\n
      If the command returns your server’s IP address, the DNS record has propagated and your subdomain is live.<\/p>\n
      Subdomain vs Addon Domain: What’s the Difference?<\/h2>\n
      This is a common point of confusion for cPanel users. Both features let you host additional websites under a single account, but they work differently:<\/p>\n\n\n\n\n\n\n\n\n
      Feature<\/th>\nSubdomain<\/th>\nAddon Domain<\/th>\n<\/tr>\n<\/thead>\n
      URL format<\/td>\nsub.yourdomain.com<\/code><\/td>\naddondomain.com<\/code><\/td>\n<\/tr>\n
      New domain required?<\/td>\nNo \u2014 uses your existing domain<\/td>\nYes \u2014 you must own and register the domain<\/td>\n<\/tr>\n
      DNS management<\/td>\nAutomatic via cPanel<\/td>\nRequires nameserver delegation or DNS edits<\/td>\n<\/tr>\n
      Best for<\/td>\nApp sections, dev environments, staging<\/td>\nSeparate websites with different brand names<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
      Use subdomains when you want to organize different sections of your main site or run separate services. Use addon domains when you need completely separate brand identities with their own domain names.<\/p>\n
      Managing Subdomain Content and Folder Structure<\/h2>\n
      Once your subdomain is created, you manage its files just like any other website on your account. Here are a few best practices to keep things organized:<\/p>\n
      Recommended Folder Structure<\/h3>\n
      public_html\/                 # Main website root\n\u251c\u2500\u2500 assets\/                  # Shared resources\n\u251c\u2500\u2500 blog\/                    # blog.yourdomain.com\n\u251c\u2500\u2500 shop\/                    # shop.yourdomain.com\n\u2502   \u2514\u2500\u2500 wp-config.php\n\u251c\u2500\u2500 staging\/                 # staging.yourdomain.com\n\u2502   \u2514\u2500\u2500 index.php\n\u2514\u2500\u2500 api\/                     # api.yourdomain.com\n    \u2514\u2500\u2500 app.php<\/code><\/pre>\n
      This approach keeps your subdomain folders at the same level inside public_html<\/code>, making backups, permissions management, and navigation through the File Manager much cleaner.<\/p>\n
      Installing WordPress on a Subdomain<\/h3>\n
      You can install WordPress on a subdomain the same way you would on a primary domain. Use the WordPress Toolkit<\/strong> in cPanel (if available) or do a manual installation:<\/p>\n
        \n
      1. Create the subdomain (e.g., shop.yourdomain.com<\/code>)<\/li>\n
      2. Navigate to the subdomain’s document root via File Manager<\/li>\n
      3. Upload the WordPress installation files<\/li>\n
      4. Create a new MySQL database and user for this WordPress instance<\/li>\n
      5. Run the WordPress installation script at the subdomain URL<\/li>\n
      6. Update the WordPress Address and Site Address in Settings > General if needed<\/li>\n<\/ol>\n
        Each WordPress installation on a subdomain gets its own database, plugins, and theme \u2014 completely independent from the main site.<\/p>\n
        Common Subdomain Issues and How to Fix Them<\/h2>\n
        Even with a straightforward setup, you may run into a few common problems. Here’s how to diagnose and resolve them:<\/p>\n
        Issue 1: The Subdomain Shows the Main Site’s Content<\/h3>\n
        This usually means the subdomain’s document root is pointing to the same folder as the main domain. Check the document root path in cPanel’s Subdomains interface and make sure it points to a separate folder. If the path is correct, verify that an index file (like index.html<\/code> or index.php<\/code>) actually exists in that folder.<\/p>\n
        Issue 2: Subdomain Redirects to the Main Domain<\/h3>\n
        This can happen if your main site’s .htaccess<\/code> file contains a redirect rule that catches the subdomain. Open the .htaccess<\/code> file in your main public_html<\/code> folder and look for RewriteRule<\/code> directives. You can add a condition to exclude the subdomain:<\/p>\n
        RewriteCond %{HTTP_HOST} !^subdomain\\.yourdomain\\.com [NC]<\/code><\/pre>\n
        Issue 3: SSL Certificate Doesn’t Cover the Subdomain<\/h3>\n
        If your subdomain loads over HTTPS but shows a certificate warning, SSL isn’t set up for it. cPanel’s AutoSSL feature supports wildcard certificates that cover *.yourdomain.com<\/code>, but not all hosting providers enable this. To fix it:<\/p>\n
          \n
        1. Go to SSL\/TLS<\/strong> in cPanel and check if AutoSSL is enabled for the subdomain<\/li>\n
        2. If using Let’s Encrypt via cPanel, run AutoSSL again \u2014 it often discovers new subdomains automatically<\/li>\n
        3. If your provider only issues single-domain certificates, you may need to manually request a certificate for the subdomain<\/li>\n<\/ol>\n
          Best Practices for Subdomain Management<\/h2>\n
          To keep your cPanel account organized and performant as you add more subdomains, follow these guidelines:<\/p>\n
            \n
          • Use descriptive names<\/strong> \u2014 Choose subdomain prefixes that clearly describe their purpose (blog<\/code>, api<\/code>, docs<\/code>) instead of generic names<\/li>\n
          • Set up separate error pages<\/strong> \u2014 Each subdomain can have its own custom error pages. Configure these under the Advanced > Error Pages section in cPanel<\/li>\n
          • Monitor resource usage<\/strong> \u2014 A resource-heavy subdomain (like a busy e-commerce store) can affect other subdomains on the same account. Check resource usage in cPanel’s Metrics section<\/li>\n
          • Keep backups per subdomain<\/strong> \u2014 Use cPanel’s Backup Wizard or a partial backup to back up individual subdomain folders rather than the entire account<\/li>\n
          • Remove unused subdomains<\/strong> \u2014 If a subdomain is no longer needed, remove it through the Subdomains interface to free up disk space and reduce attack surface<\/li>\n
          • Use subdomains for staging<\/strong> \u2014 Set up a staging.yourdomain.com<\/code> subdomain to test site changes before deploying to the live site<\/li>\n<\/ul>\n
            Key Takeaways<\/h2>\n
              \n
            • Subdomains in cPanel let you host multiple independent sites or apps under one domain, each with its own document root folder<\/li>\n
            • Creating a subdomain is a two-step process: define the prefix and document root, and cPanel handles DNS and folder creation automatically<\/li>\n
            • Use subdomains for functional divisions of your main domain (blog, shop, docs); use addon domains for completely separate brands<\/li>\n
            • Common issues include wrong document root paths, .htaccess redirect rules interfering with subdomains, and missing SSL coverage<\/li>\n
            • DNS propagation after creating a new subdomain can take up to 48 hours \u2014 verify with dig<\/code> or nslookup<\/code><\/li>\n
            • Each subdomain gets its own separate error pages, analytics, and resource footprint within your cPanel account<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"
              Learn how to set up, manage, and troubleshoot subdomains in cPanel. Step-by-step guide with DNS configuration, folder structure best practices, and common fixes.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[99],"tags":[100,301,153,300,299],"class_list":["post-115","post","type-post","status-publish","format-standard","hentry","category-domain-management","tag-cpanel-domain-management","tag-cpanel-hosting-guide","tag-cpanel-subdomains","tag-subdomain-dns-setup","tag-subdomain-setup-guide"],"_links":{"self":[{"href":"https:\/\/cpanelreview.com\/index.php\/wp-json\/wp\/v2\/posts\/115","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cpanelreview.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cpanelreview.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cpanelreview.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cpanelreview.com\/index.php\/wp-json\/wp\/v2\/comments?post=115"}],"version-history":[{"count":1,"href":"https:\/\/cpanelreview.com\/index.php\/wp-json\/wp\/v2\/posts\/115\/revisions"}],"predecessor-version":[{"id":116,"href":"https:\/\/cpanelreview.com\/index.php\/wp-json\/wp\/v2\/posts\/115\/revisions\/116"}],"wp:attachment":[{"href":"https:\/\/cpanelreview.com\/index.php\/wp-json\/wp\/v2\/media?parent=115"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cpanelreview.com\/index.php\/wp-json\/wp\/v2\/categories?post=115"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cpanelreview.com\/index.php\/wp-json\/wp\/v2\/tags?post=115"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}