How to Set Up a New Hosting Site in cPanel or Plesk
Start with the hosting plan, not the panel
Before you set up a new hosting site in cPanel or Plesk, decide where the site belongs. A brochure site with a contact form can live happily on Hostperl shared hosting. A larger WordPress build, a staging copy, or a site that needs tighter control usually belongs on a VPS.
If you are still choosing the right tier, compare the workload first. Site size, email volume, backups, and traffic spikes matter more than the control panel logo on the login screen. Hostperl customers often save time by choosing the right platform up front, especially when they plan a migration or a rebrand launch.
If you want a broader buying guide before you start, our shared, VPS, and dedicated comparison and VPS vs dedicated guide explain where each plan fits.
Create the account and confirm the basics
Once your plan is active, log in to the control panel and create the hosting account or subscription. In cPanel, that usually means checking the primary domain, username, document root, and assigned PHP version. In Plesk, confirm the subscription, service plan limits, and the primary domain before you touch DNS.
Use this quick checklist before uploading anything:
- Primary domain is spelled correctly.
- Document root points to the right folder, usually
public_htmlor the subscription web root. - PHP version matches the app you are deploying.
- Email mailbox names are decided in advance.
- Backup policy is enabled or scheduled.
That five-minute check prevents the support tickets we see most often: the site loads on the wrong domain, email lands in the wrong mailbox, or the application points to the old path after launch.
Point DNS before launch, then wait for it to settle
Now connect the domain. If your nameservers are staying at the registrar, update the A, AAAA, and MX records to the new hosting server. If you are moving the whole DNS zone, make sure the zone contains the web, mail, and verification records before switching nameservers.
Our SSL, DNS, and email setup checklist is a good companion while you do this. For domains, mail routing, and reputation-sensitive setups, Hostperl’s IP and DNS services are useful when you need consistent routing for mail or a clean split between web and email.
Use a short propagation test from a shell or an online DNS checker:
dig yourdomain.com A +short
dig yourdomain.com MX +shortIf the old IP still appears, wait. Changing DNS too early is how teams end up publishing to the wrong server during a live launch.
Install SSL before you move real traffic
Do not launch a site over plain HTTP and “fix it later.” Issue the certificate first, then confirm the site redirects cleanly to HTTPS. In cPanel, that usually means checking AutoSSL status. In Plesk, use the Let’s Encrypt extension or your preferred certificate flow, then force HTTPS for the domain.
A quick browser test should show one valid certificate chain and no mixed-content warnings. If images or scripts still load over HTTP, the browser will flag the page, and some checkout or login flows may break. That is especially common after a WordPress migration or when a developer hard-codes old asset URLs.
Create email accounts and test deliverability
Email is the part most site owners underestimate. Create mailboxes, set the right quota, and decide whether you want forwarders, aliases, or direct inboxes. For business sites, one mailbox per role is easier to manage than one shared inbox that everyone accesses.
Before you tell clients or staff to start using the new domain mail, send a test message to Gmail, Outlook, and one mobile app. Confirm that SPF, DKIM, and DMARC are in place, then review the first outbound message headers. If you need a mail-focused checklist, see our email deliverability checklist and the cPanel email hosting guide.
For customers on VPS plans, poor IP reputation can delay delivery even when the DNS records look correct. That is why Hostperl support teams often check mail logs and not just panel settings when a launch ticket comes in.
Upload the site and verify the file path
Now move the content. For a static site, upload the files into the document root. For WordPress or another CMS, restore the database, update the config file, and confirm that the domain in the database matches the new hostname.
If you are moving from another host, a careful migration guide helps more than a hurried copy job. Our shared hosting migration tutorial and migration checklist cover the practical parts: files, databases, email, and the final cutover window.
After upload, open the site in a private browser window and check:
- Homepage loads on the new server.
- Contact forms send mail to the right address.
- Login pages use HTTPS.
- Images, CSS, and JavaScript load without 404 errors.
- Old cache is cleared in the CMS and browser.
Set PHP, permissions, and backups the sensible way
For most sites, the default PHP version is not the best choice. Match the version to the application, then test the admin area, checkout, and form submissions. If a plugin or extension fails, you will often see it before your visitors do.
Keep permissions conservative. Web files usually need readable access, while config files and secrets should stay protected. In shared hosting, the panel handles much of this for you. On VPS hosting, you should also confirm ownership so the web server can write only where it needs to.
Backups are part of launch readiness, not a separate project. Schedule daily backups for active sites and keep at least one off-server copy. If you need a stronger baseline for a growing customer site, Hostperl VPS hosting gives you more room for backup schedules, test restores, and larger databases than a busy shared account.
Check the site like a customer would
Do a short launch test before you announce the site. Open the homepage, submit a form, log in to the admin area, and place a test order if the site sells anything. Then confirm that the success page, receipt email, and admin notification all arrive.
If the site feels slow, check the basics first: image size, plugin count, caching, and server resources. Do not start with a full rebuild. A lot of launch-day slowdowns come from oversized images or a theme that loads too many scripts.
This is also a good moment to compare your current setup against the panel and server choice you made. If you are still unsure whether cPanel, Plesk, or DirectAdmin fits your workflow, our cPanel vs Plesk comparison and three-panel guide will save you from buying the wrong setup twice.
Common launch problems and the fastest fix
Most support calls after a new site goes live follow the same pattern. The domain points to the wrong server, the SSL certificate is missing, the mail MX record still points to the old host, or the CMS cache is serving stale content.
Here is the fastest order of attack:
- Confirm DNS resolves to the new IP.
- Verify SSL is active on the live domain.
- Check the web root and file ownership.
- Send and receive one test email.
- Clear any site cache and CDN cache.
If the issue only appears in one browser or one region, it is usually DNS caching or mixed content. If the issue appears everywhere, the problem is usually in the server configuration or the application itself.
If you want help setting up a new hosting site without bouncing between DNS, SSL, and mail issues, Hostperl can handle the practical parts with you. Start with shared hosting for smaller sites or move up to VPS hosting when you need more control, backups, and room to grow.
Our team works with real launches, migrations, and panel changes every day, so we know where setup goes wrong and how to keep the handoff clean.
FAQ
Should I set up DNS or SSL first?
Set DNS first so the domain points to the right server, then issue SSL once the host is reachable. If the certificate depends on HTTP validation, the DNS change has to be live first.
Can I use cPanel for WordPress and email on one account?
Yes. That is a common setup for small businesses. Just keep an eye on mailbox quotas, backups, and PHP version compatibility.
How long should I wait after changing nameservers?
Most changes settle within a few hours, but you should allow up to 24 hours. If mail or web traffic is still hitting the old host after that, check TTL values and cached DNS.
What if my site works but email does not?
Check MX, SPF, DKIM, and DMARC records first. The web site may be fine while mail still points at the old provider or fails authentication checks.
When should I move from shared hosting to a VPS?
Move when you need more consistent performance, larger backups, custom services, or better control over email and server settings. Our upgrade signals guide explains the usual triggers.
