Adding a subdomain in Plesk is a common task when you want to separate parts of a website, create a staging area, host a blog or store, or build a dedicated location for app files and test environments. In a managed hosting setup, Plesk makes this process straightforward, but the exact options available depend on your subscription limits, DNS setup, and whether the domain is using the server’s nameservers.
In this guide, you will learn how to create a subdomain in Plesk, where to find the relevant settings, how to connect DNS correctly, and what to check if the subdomain does not open after creation. The steps apply to standard Plesk hosting environments used across Europe and are suitable for websites hosted on Apache or Nginx-based stacks managed through Plesk.
What a subdomain is in Plesk
A subdomain is a separate web address that sits under your main domain name. For example, if your main domain is example.com, a subdomain could be shop.example.com, blog.example.com, or dev.example.com.
In Plesk, each subdomain can have its own document root, web content, SSL certificate, mail settings, and PHP configuration, depending on the hosting plan and permissions. This makes subdomains useful for:
- building a staging or testing environment
- separating a blog, shop, or support portal from the main site
- hosting multilingual or regional content
- running applications in isolated directories
- organising projects under one main domain
Before you create a subdomain, it is important to check whether your hosting package allows additional domain objects. Some plans include a limit on the number of subdomains, and in managed hosting environments the feature may be restricted by the subscription settings.
Before you add a subdomain
To avoid problems after creation, review the following points first:
- Domain is active: The main domain should already be added to Plesk and properly configured.
- DNS is available: The subdomain needs a DNS record if the DNS zone is managed in Plesk or at an external provider.
- Hosting space is available: The subscription should have enough disk space and available domain objects.
- SSL needs planning: If you want HTTPS, decide whether you will use a separate certificate or a wildcard certificate.
- Application structure: Know where you want the subdomain files to be stored, especially if you are using a CMS or custom app.
If you are working in a European hosting environment, the process is the same, but it is also a good idea to confirm that any region-specific content, cookie tools, or app settings match your compliance requirements.
How to add a subdomain in Plesk
The most common way to create a subdomain in Plesk is through the Domains section. The interface may differ slightly depending on the Plesk version, but the general steps are the same.
Step 1: Sign in to Plesk
Log in to your Plesk control panel using your hosting account credentials.
If you manage multiple subscriptions or domains, make sure you are working inside the correct subscription before making changes.
Step 2: Open the Domains section
From the left menu or the main dashboard, go to Domains. In some layouts, this may appear as Websites & Domains.
This area shows the main domain and any existing subdomains, domain aliases, or parked domains associated with the subscription.
Step 3: Click Add Subdomain
Select Add Subdomain. Plesk will usually ask you to enter:
- Subdomain name — for example, blog or shop
- Main domain — the base domain the subdomain belongs to
- Document root — the folder where the website files will be stored
When you enter the subdomain name, Plesk automatically combines it with the main domain to form the full address. For example, entering blog under example.com creates blog.example.com.
Step 4: Set the document root
The document root is the directory where the subdomain’s website files will live. Plesk may suggest a default path such as /subdomains/blog/httpdocs or a similar folder structure.
It is usually best to keep the default folder unless you have a specific deployment structure in mind. If you are installing a CMS, staging copy, or application framework, make sure the selected path matches your project setup.
Useful examples:
- blog.example.com → a WordPress blog in its own folder
- store.example.com → an e-commerce instance with separate assets
- dev.example.com → a development copy of the main website
Step 5: Confirm hosting settings
Depending on your Plesk configuration, you may be able to choose additional hosting options during subdomain creation, such as:
- PHP version
- PHP handler
- SSL/TLS support
- DNS settings
- mail service for the subdomain
If the subdomain is meant only for web hosting, you may not need email services enabled. If you plan to use email addresses like [email protected], verify that mail is configured correctly.
Step 6: Save and create the subdomain
Click OK, Create, or Add Domain depending on the interface. Plesk will create the subdomain and its hosting directory.
After creation, you should see the new subdomain listed in the domains overview. From there, you can upload website files, install an application, or configure additional settings.
How DNS works for a subdomain
Creating a subdomain in Plesk is only part of the process. The DNS record must point the subdomain to the correct server so that browsers can find it.
If Plesk manages the DNS zone for your domain, the system often creates the required record automatically. This is usually an A record or AAAA record pointing to the hosting server’s IP address, or a CNAME record in some setups.
If DNS is managed elsewhere, you may need to add the subdomain record manually at your DNS provider.
Common DNS record types for subdomains
- A record: points the subdomain to an IPv4 address
- AAAA record: points the subdomain to an IPv6 address
- CNAME record: points the subdomain to another hostname
Example DNS setup for blog.example.com:
- Type: A
- Name: blog
- Value: your server IP address
DNS changes can take time to propagate. Depending on the TTL and provider, it may take from a few minutes to several hours before the subdomain becomes reachable.
How to upload files to the subdomain
Once the subdomain exists, you need website files in its document root. In Plesk, you can upload content using File Manager, FTP, or a deployment tool if your hosting plan supports it.
Using File Manager
- Open the subdomain in Plesk.
- Click Files or File Manager.
- Open the document root folder.
- Upload your website files, such as index.html or index.php.
If the folder is empty, the browser may show a default page or an error until you upload content.
Using FTP
If you prefer to upload files via FTP, connect using the FTP credentials assigned to the subscription or the specific subdomain, if separate access is configured. Make sure you upload the files into the correct directory linked to the subdomain’s document root.
A common issue is placing the files in the main domain folder instead of the subdomain folder. When that happens, the site will not appear at the expected address.
How to enable HTTPS for the subdomain
For production websites, HTTPS is strongly recommended. In Plesk, you can usually secure a subdomain with an SSL certificate from Let’s Encrypt or another certificate authority, depending on the hosting setup.
Typical HTTPS steps
- Open the subdomain settings in Plesk.
- Go to SSL/TLS Certificates or the SSL section.
- Issue or upload a certificate for the subdomain.
- Enable the option to redirect HTTP to HTTPS if needed.
If your certificate is a wildcard certificate, it may already cover multiple subdomains. If not, each subdomain might need its own certificate.
For hosted sites in Europe, HTTPS is especially important when the subdomain handles forms, logins, checkout flows, or personal data.
How to change subdomain settings in Plesk
After the subdomain is created, you can adjust several settings from the Plesk panel.
Change the document root
If you need to move the website files to another directory, update the document root in the subdomain settings. Be careful when changing the path, as existing content may need to be moved too.
Change PHP settings
Plesk allows you to assign a specific PHP version or handler to the subdomain. This is useful when one application requires PHP 8.2 and another still depends on a different version.
Enable or disable DNS and mail
Depending on the configuration, you may choose whether the subdomain should have its own DNS zone entries or mail service. If you only need a web-only address, mail can often remain disabled.
Configure redirects
You can set the subdomain to redirect to another page or domain if it is used as an alias, campaign page, or temporary location. This is often done through hosting settings or a .htaccess file, depending on the web server configuration.
Common problems when adding a subdomain
Even though Plesk simplifies the process, a few issues can prevent the subdomain from working correctly.
The subdomain does not open in the browser
Possible causes:
- DNS record is missing or incorrect
- DNS changes have not propagated yet
- Document root is empty
- Web server configuration has not updated
- SSL certificate is missing or not trusted
Start by checking the DNS record and confirming that the subdomain points to the correct server IP. Then verify that an index.html or index.php file exists in the document root.
You get a 403 Forbidden error
This usually means the web server can reach the folder, but access is blocked or no default file is present.
Check the following:
- folder permissions
- file ownership
- presence of a default index file
- security rules or .htaccess directives
You see the main site instead of the subdomain
This often indicates that the subdomain DNS record points to the same IP, but the web server is serving the wrong site configuration, or the document root was assigned incorrectly.
Review the subdomain’s hosting settings in Plesk and confirm the folder path matches the intended content.
SSL warning appears after enabling HTTPS
If the browser shows a certificate warning, the certificate may not include the subdomain name, or the certificate installation may be incomplete.
Check that the certificate covers the exact subdomain, such as blog.example.com, and that it is assigned to the correct hosting object in Plesk.
Best practices for managing subdomains
To keep your hosting environment clean and easy to maintain, it helps to follow a few practical rules when using subdomains.
- Use clear names that describe the purpose of the site.
- Keep staging and production on separate subdomains.
- Store files in the correct document root from the start.
- Use HTTPS on every public-facing subdomain.
- Review permissions carefully if multiple users manage the account.
- Remove unused subdomains to reduce confusion and security risk.
For managed hosting environments, this kind of structure helps support teams troubleshoot issues faster because the purpose of each subdomain is easier to identify.
Example use cases for a subdomain
Subdomains are flexible and useful in many real-world hosting scenarios:
- blog.example.com for content marketing
- shop.example.com for an online store
- help.example.com for documentation or support content
- staging.example.com for pre-production testing
- cdn.example.com for asset delivery or static files
In each case, Plesk lets you manage the subdomain separately while keeping it under the same main domain and hosting subscription.
FAQ
Can I create a subdomain without changing the main website?
Yes. A subdomain is separate from the main site. You can create it in Plesk and configure it with its own files, PHP version, and SSL certificate without affecting the root domain.
Does Plesk create the DNS record automatically?
Often yes, if Plesk manages the DNS zone for the domain. If DNS is hosted elsewhere, you will need to add the record at your DNS provider manually.
How long does it take for a new subdomain to work?
If DNS is set correctly, it may work within minutes, but global propagation can take longer depending on the TTL and the DNS provider.
Can a subdomain have its own SSL certificate?
Yes. In Plesk, you can usually assign a dedicated certificate to the subdomain. Some wildcard certificates may also cover it.
Can I install WordPress on a subdomain?
Yes. You can install WordPress or another CMS in the subdomain’s document root, just like on a main domain.
Why is my subdomain showing a default page?
This usually means the subdomain is active but no website files have been uploaded yet, or the document root points to a folder containing a placeholder page.
Can I delete a subdomain later?
Yes. You can remove a subdomain from Plesk when it is no longer needed. Before deleting it, back up any files, databases, and DNS records you want to keep.
Conclusion
Adding a subdomain in Plesk is a simple but important hosting task. By creating the subdomain, assigning the correct document root, checking DNS, and enabling SSL where needed, you can launch separate website sections or applications with minimal effort. For most hosting environments, the main points to remember are to create the subdomain in Plesk, confirm that the DNS record points to the correct server, and place your website files in the right folder.
If the subdomain does not work immediately, review DNS propagation, file placement, SSL assignment, and hosting permissions. Once these are set correctly, the subdomain will behave like an independent website while remaining part of your main domain structure.