Set Up a New Hosting Site in cPanel or Plesk
Start with the account, not the website
If you need to set up a new hosting site in cPanel or Plesk, start with the account details, not the homepage design. A clean launch depends on the right domain, the correct PHP version, mail routing, and SSL in place before anyone visits.
On Hostperl shared hosting, the first step is usually to confirm that the domain is attached to the right account and that DNS points where you expect. If the site will grow beyond a small brochure build, check our Hostperl VPS plans before you commit, especially if you expect heavier email use, staging copies, or more than one site.
If you are comparing control panels before a new launch, the panel choice can matter more than the installer. That is why we keep practical references like cPanel, Plesk, or DirectAdmin for Real Hosting Teams close at hand during migrations and new builds.
Set up the domain and DNS first
Before you upload a single file, make sure the domain resolves to the new server. If the domain uses external DNS, update the A record for the root domain and the CNAME for www. If you are using Hostperl DNS, point the nameservers from your registration panel and allow time for propagation.
- Root domain:
Arecord to the server IP. - WWW:
CNAMEto the root domain, or a matchingArecord. - Mail: confirm
MXrecords before creating mailboxes. - SSL: plan for HTTPS before launch day, not after.
If you are not sure whether your DNS and mail setup is ready, follow our email, DNS, and SSL setup guide. It walks through the order that avoids the most common launch-day mistakes.
Create the site in cPanel
In cPanel, open Domains and add the domain as a new site or addon domain, depending on your plan and the panel version you use. Then open MultiPHP Manager and choose the PHP version that matches your application. For a WordPress site in 2026, PHP 8.2 or 8.3 is usually the safest starting point, unless a plugin forces an older version.
Next, go to File Manager and place the files in the domain’s document root, usually something like /home/username/public_html or a domain-specific folder under it. If the site is a fresh build, upload a clean application package. If it is a migration, restore the files first, then import the database, then test the site on a temporary URL or hosts-file preview.
For a more detailed walkthrough of the hosting-side setup, use How to Set Up a New Hosting Site in cPanel or Plesk as the panel-by-panel reference.
Create the site in Plesk
Plesk works differently, but the order stays the same. Open Websites & Domains, click Add Domain, and enter the new site name. Then check the subscription limits so storage, traffic, and mailbox counts match the customer’s plan. If you skip that step, a site can look active while email or database creation later fails because of quota limits.
After the domain appears, open PHP Settings and choose the version you want for the site. Plesk also makes it easy to set a document root, which helps if you are running a legacy app under a subfolder. Upload the site files, create the database, and keep the database name and password in a secure password manager before you edit the application config.
If you are choosing between panels for a new client project, our guide to cPanel vs Plesk for Hosting Customers is the quickest way to match the panel to your workflow and support expectations.
Install SSL before the first live test
Do not wait for a browser warning to tell you the certificate is missing. In cPanel, use SSL/TLS Status or AutoSSL. In Plesk, use SSL/TLS Certificates or the built-in Let’s Encrypt extension if it is available on the server.
After installation, open the site with https:// and check three things: the certificate is valid, the redirect from HTTP to HTTPS works, and the browser does not show a mixed-content warning. If images or scripts still load over HTTP, fix the application settings or rewrite rules before you announce the site.
A practical checklist for this stage is in SSL, DNS, and Email Setup Checklist for Hosting Customers, which covers the launch pieces customers most often miss.
Set up email the same day
Email is part of the hosting launch, not a separate task. Create at least one mailbox, verify the outgoing mail settings, and test delivery to a Gmail or Outlook address. On shared hosting, the most common issue is not sending itself but poor deliverability because SPF, DKIM, or a correct MX record was skipped.
In cPanel, open Email Accounts for mailbox creation and Email Deliverability for authentication records. In Plesk, use Mail settings and confirm the domain has the right DNS entries. If the customer relies on mail for orders or lead forms, send a few test messages from the live domain before you migrate any forms.
For a field-tested walkthrough, link your setup to Hostperl SSL, DNS, and Email Setup Tutorial for New Sites. It keeps the launch order clear and reduces back-and-forth support tickets.
Upload the files and restore the database
Once DNS and SSL are in motion, upload the application files and restore the database. For WordPress, that usually means copying the site files into the document root, then importing the .sql file into MySQL, then updating wp-config.php with the new database name, user, and password. For a custom PHP site, check the config file path before you change anything else.
A common mistake here is restoring the database but forgetting to change the site URL. WordPress will still point to the old domain until you update it. If the old site was on another host, use a temporary hosts-file entry or a staging URL to confirm the pages load before switching DNS fully.
When you are migrating rather than building from scratch, our tutorial on How to Move Hosting Sites Without Downtime in 2026 is the better companion guide. It covers timing, verification, and the final DNS cutover.
Run a launch checklist before you publish
Use this short list before you tell anyone the site is live:
- Open the homepage, contact page, and checkout or form pages.
- Confirm HTTPS loads without warnings.
- Send one test email and receive one reply.
- Check the site on mobile and desktop.
- Verify the domain resolves from the public internet.
- Make a backup after the first successful test.
If the site is for a business customer, this checklist usually catches the problems that matter: broken mail, the wrong document root, expired SSL, or a forgotten redirect. That is the difference between a site that is uploaded and a site that is ready.
Common problems and quick fixes
Blank page after upload: check the PHP version and look for a fatal error in the application logs. In cPanel, that is usually under Metrics or the site’s error log. In Plesk, check Logs in the domain view.
404 after DNS change: confirm the domain points to the correct document root. A site can resolve correctly and still fail if the app is installed in the wrong folder.
Email not sending: verify SPF and DKIM, then test SMTP credentials from the mailbox settings. Shared hosting often sends fine, but unauthenticated mail gets filtered or rejected.
SSL warning remains: clear cached redirects and search for hard-coded HTTP links inside the theme or template.
When you need a little more capacity for testing, staging copies, or client sites with heavier mail use, a managed VPS often gives you a cleaner path than stretching a crowded shared account. Hostperl’s shared hosting is still a good fit for simple launches, but the move should be intentional.
If you want a clean start without spending the afternoon untangling DNS and mail settings, Hostperl can help you launch the site in the right order. For small business projects, shared hosting is often enough; for busier sites or multiple client installs, Hostperl VPS hosting gives you more room to grow.
Our team works through migrations, SSL checks, and launch troubleshooting every day, so you are not left guessing when the site goes live.
FAQ
Should I build a new site on shared hosting or VPS?
Use shared hosting for a small site, a brochure project, or a low-mail-volume business. Choose VPS if you need more control, multiple sites, heavier email use, or more performance headroom.
Which is better for a new site, cPanel or Plesk?
Both work well. cPanel suits many classic shared hosting workflows, while Plesk feels more organized if you manage multiple domains or move between Linux and Windows-oriented teams. Your support preference matters as much as the interface.
Why does my new site still show the old domain?
That usually means the application URL, database content, or cached redirect still points to the old address. Check the site settings, clear cache, and confirm the DNS cutover has finished.
Do I need SSL before launch?
Yes. Install SSL before you publish the site so visitors never see a warning page. It also avoids mixed-content issues in the first crawl by search engines.
What is the fastest way to verify email on a new hosting account?
Create one mailbox, send a message to an external address, and reply from that inbox. If both directions work and SPF/DKIM are present, the setup is usually healthy.
