Plesk subdomain hosting

How to add a subdomain website in Plesk

Create an address such as shop.example.co.uk with its own document root, content and optional application inside an existing hosting subscription.

Exampleshop.example.co.uk
ContentSeparate folder
FinishAdd HTTPS

A subdomain is part of an existing domain

Use a subdomain for a distinct area such as shop, portal or staging. Add a full domain instead when the website uses a separately registered name, or an alias when two names should show the same content.

Add it under the correct parent domain

  1. Open My Services, select the hosting service and log in to Plesk.
  2. Open Websites & Domains and choose Add Subdomain.
  3. Enter only the prefix, such as shop, and select the correct parent domain.
  4. Review the suggested document root. Use a dedicated folder unless content is intentionally shared.
  5. Select OK or Add Subdomain.
  6. Upload content, install the application or open Sitejet Builder if available.
Plesk domains guide

Make the new name resolve to the hosting server

If Plesk hosts the authoritative DNS zone, it normally creates the required record. If DNS is managed elsewhere, add an A or CNAME record there using the destination supplied for the hosting service.

A wildcard record can hide mistakes

A wildcard may make an unconfigured name reach the server, but Plesk still needs the subdomain object to map requests to the intended document root.

Add the subdomain to its certificate

  1. Wait until the subdomain resolves publicly to the hosting server.
  2. Open SSL/TLS Certificates or the Plesk security control for the site.
  3. Issue or renew a certificate that includes the new subdomain.
  4. Confirm https://subdomain.example.co.uk opens without a warning.
  5. Enable HTTPS redirection only after that test succeeds.

If the subdomain does not open the expected website

Server not found
The public DNS record is absent or has not reached the resolver being used.
Plesk page appears
The name reaches the server but is not mapped to the expected Plesk object.
Parent website appears
Check the subdomain object and its document root; a wildcard or shared root may be taking effect.
403 or empty page
Check files, index page, permissions and application deployment in the subdomain document root.
Certificate warning
The subdomain is not covered by the selected certificate or DNS still points elsewhere.

Subdomain still not working?

Send us the full subdomain, parent domain, hosting service, intended document root, DNS provider, current DNS result and exact browser error. Do not send passwords.

Ask the Hosting team

Was this answer helpful?

« Back