How to Set Up a New Hosting Site in cPanel or Plesk
Start with the right panel and plan
To set up a new hosting site in cPanel or Plesk, start with the plan that fits the workload, not just the monthly price. A small brochure site can run happily on shared hosting, while a client portal, WooCommerce store, or busy agency site often needs a VPS from Hostperl VPS before launch day.
If you are moving from another host, the cleanest approach is to prepare the new account first, then change DNS only after the site, email, and SSL are ready. That avoids the awkward middle stage where some services still point to the old server. If you want to compare panels first, our guide on cPanel vs Plesk for hosting buyers in 2026 is a good place to start.
Set up the account and domain
After you log in to cPanel or Plesk, add the domain as a new site or addon domain, depending on the panel layout and plan type. Use the exact domain you plan to publish, including the version you want live, such as example.com instead of a temporary subdomain.
In cPanel, open Domains, then confirm the document root, usually /home/username/public_html/ or a folder beneath it. In Plesk, go to Websites & Domains, then check that the hosting type is correct and the site directory sits under httpdocs. If the site already exists elsewhere, our panel migration guide helps you avoid the usual path and permissions problems.
- Confirm the primary domain spelling.
- Choose the correct PHP version for the application.
- Check the document root before uploading files.
- Keep a note of the database name and username.
Upload files and restore the application
For a WordPress or CMS site, upload the files through File Manager or an SFTP client, then restore the database if you are migrating. If the site is new, install the application cleanly instead of mixing old configuration files into a fresh account.
Use the current public web root only. On cPanel, that is usually public_html. On Plesk, it is typically httpdocs. If the homepage shows a directory listing instead of the site, the files are in the wrong folder or the index file is missing. A quick check for index.php or index.html in the web root usually shows you what went wrong.
For WordPress customers, a fresh setup is often faster than restoring a broken package. Shared hosting works well for smaller sites, and our shared hosting plans fit that use case well. If you expect steady traffic or want more control over PHP workers and memory, move the site to a VPS before launch rather than after visitors arrive.
Connect DNS before you switch traffic
Most launch problems start with DNS records that were changed in a rush. Before pointing the domain to the new server, confirm the correct nameservers, then set the A record for the root domain and the www record if you use one.
For a standard web launch, you usually need these records:
- A record for
@pointing to the server IP. - CNAME for
wwwpointing to the root domain, or an A record if your setup prefers it. - MX records only if email will be hosted on the same server.
If the site does not resolve after you change records, check propagation against the current TTL. A 300-second TTL is easier to manage during a migration than a 24-hour value. For a fuller launch checklist, link this step with our SSL, DNS, and email setup checklist, which covers the order that avoids most support tickets.
Issue SSL and force HTTPS
Once the domain resolves to the new server, issue the SSL certificate before you announce the site. In cPanel, AutoSSL usually handles this after DNS points correctly. In Plesk, use SSL/TLS Certificates or the built-in Let’s Encrypt integration if it is available on the plan.
Test both the root domain and www in a browser. If one version shows a certificate warning, the certificate was issued for only one hostname. That is easy to fix, but it can break login pages and checkout forms if you miss it during launch. For WordPress users on shared plans, our article on email deliverability on shared hosting also helps, because SSL and email authentication often go live at the same time.
After the certificate is active, turn on HTTP to HTTPS redirection in the panel or application settings. If the site has old mixed-content links, fix image and stylesheet URLs before forcing redirects, or some pages will load with broken assets.
Create email accounts and protect deliverability
Do not leave email until after launch. That mistake creates some of the most avoidable support calls. Create the mailbox, set a strong password, and confirm the MX records before you start sending invoices or password resets.
On a new cPanel or Plesk site, create at least one admin mailbox and a catch-all only if you truly need it. Then set up SPF, DKIM, and DMARC so your messages are less likely to land in spam. If you are unsure whether email belongs on shared hosting or a VPS, our guide on shared hosting vs VPS for email explains the real tradeoffs without the jargon.
- Use one mailbox for admin notifications.
- Enable DKIM signing in the control panel.
- Add an SPF record that matches your mail server.
- Test deliverability with a Gmail or Outlook address.
Check PHP, database, and file permissions
Before the site goes live, confirm the PHP version and database settings match the application requirements. A CMS that worked on PHP 8.1 may fail on PHP 8.3 if an old plugin or theme still depends on deprecated code. That is why we recommend testing on the target panel before you switch the public DNS.
In cPanel, look for Select PHP Version or MultiPHP Manager. In Plesk, check the domain’s PHP handler under Hosting Settings. For database-driven sites, confirm the host, database name, username, and password in the app configuration file. For WordPress, that file is wp-config.php. For many PHP apps, it is a separate .env or config.php.
If you need a clean environment for a growing site, a VPS gives you more control over PHP-FPM, memory, and database tuning. Our managed VPS hosting is often the right next step when shared resources start to feel tight.
Run a simple pre-launch test
This is the part that saves time later. Open the site on the new server using the temporary URL or hosts-file preview, then click through the main pages, forms, and login screens.
Use this short test list:
- Homepage loads over HTTPS.
- Contact form sends a message to the correct inbox.
- Admin login works without a redirect loop.
- Images and CSS load without mixed-content warnings.
- Email from the form reaches an external mailbox.
If something fails, the issue is usually one of four things: DNS still points to the old host, the certificate is incomplete, the database credentials are wrong, or the PHP version does not match the app. Those are the first places our support team checks during launch requests.
What to do after launch
After the domain points to the new server, keep the old hosting account active for a short window so queued mail and late DNS updates can settle. Then compare access logs, mail logs, and application error logs for the first 24 to 48 hours. That overlap catches missing images, old absolute URLs, and forgotten mailbox settings.
If you are moving the site later to a different panel or a larger plan, save your setup notes now. The next migration is much easier when you already know the document root, PHP version, database name, and DNS provider. For teams that expect growth, plan the next step early, whether that means a stronger shared plan or a larger dedicated server hosting package.
Hostperl can set up the site with the right DNS, SSL, email, and hosting layer from the start, which helps you avoid the most common launch mistakes. If you want a clean start on a reliable platform, compare shared hosting and VPS hosting before you publish.
Our support team handles real migrations and cutovers every day, so if your launch needs a second pair of eyes, that is part of the service.
FAQ
Should I use cPanel or Plesk for a new hosting site?
Use the panel your team already understands if the site is simple. Choose Plesk if you manage mixed Linux workloads or want a cleaner view across multiple domains. Choose cPanel if your team already supports it well and your workflow fits its layout.
Can I set up a site on shared hosting and move it later?
Yes. Many customers start on shared hosting, then move to a VPS once traffic, email volume, or plugin load grows. Plan the migration early so your DNS, email, and backups are already in order.
Why does my SSL certificate still show a warning after DNS changes?
The certificate may not have been issued for every hostname yet, or DNS has not fully propagated. Check both the root domain and www, then re-run AutoSSL or the certificate request from the panel.
What is the most common setup mistake?
The web files are uploaded to the wrong directory, or the MX records are left pointing at the old host. Either one can make a brand-new site look broken even when the server is fine.
