Create your first website in Plesk

Before you begin

Make sure the hosting space is ready

• Active hosting service: The domain must have web hosting, not only registration or UKC Parking.
• Domain in Plesk: It should appear under Websites & Domains on the assigned UKC server.
• Backup: Save existing files and databases before replacing a site or publishing a builder.
• Email plan: Know where mail is hosted before changing nameservers or MX records.

Choose your method

Match the platform to the website

Option 1

Create a website with Sitejet Builder

1. Open the domain in Plesk. Go to Websites & Domains and select its Get Started view.
2. Choose Create Website or Sitejet Builder. Select a template suited to the purpose of the site.
3. Add real content. Replace sample text and images, check contact details and review the mobile layout.
4. Preview before publishing. Check every page, form, button and external link.
5. Publish only when ready. The generated site is placed in the domain's document root.

Option 2

Install WordPress or another application

Use Plesk's WordPress Toolkit or application installer where available. Select the exact target domain and directory, create a unique administrator account and remove any temporary credentials after setup.

• An automatic CMS installation normally creates its required database.
• Do not install into a subdirectory unless the website should use that path.
• Apply core, theme and plugin updates before launch.
• Enable scheduled backups and use only extensions you trust and maintain.
• Keep the application administrator password separate from Plesk and the Client Area.

Option 3

Upload an existing website

1. Open File Manager for the correct domain and enter its document root, normally httpdocs.
2. Back up or remove the placeholder safely. Do not overwrite an existing production site without a recovery copy.
3. Upload the website. For many files, upload a ZIP archive and extract it in the document root; FTP is useful for larger or repeat deployments.
4. Check the entry file. A static site normally needs index.html; a PHP application commonly uses index.php.
5. Configure dependencies. Create/import a database and update the application's configuration only when the site requires one.

Use the assigned UKC server hostname or IP when the domain does not yet point to the hosting server. Avoid sending FTP passwords in email or support tickets.

Make it public

Connect the domain to UKC hosting

The domain can use the nameservers assigned to its UKC hosting server, such as a ukc01.uk through ukc13.uk pair, or retain other authoritative nameservers with web records pointing to the hosting IP. The Domain Control Centre identifies UKC-hosted routes.

Launch checks

Enable HTTPS and test the real website

1. Issue a certificate. Use the SSL/TLS or Let's Encrypt controls in Plesk for the domain and required www hostname.
2. Open both hostname forms. Confirm the preferred address redirects consistently and presents a trusted certificate.
3. Test on mobile and desktop. Review navigation, forms, images, downloads and error pages.
4. Check application functions. Test login, password reset, email delivery, orders and integrations where applicable.
5. Keep the previous site available briefly. Monitor the new logs and retain a rollback path until acceptance.

Need help?

Describe the website and the stage you reached

Include the domain, hosting service, chosen build method, assigned UKC server, current nameservers, the exact error and whether email must remain with another provider. Never put passwords, private keys or API keys in a ticket.