What you need before you start
- A domain name. If you do not have one, register it first. See "How to Choose a Domain Name and TLD That Ages Well".
- A hosting plan. Shared hosting is enough for most small sites. A VPS or Coolify is for custom applications or high traffic.
- Content. Text, images, a logo, and the pages you want at launch. A launch with placeholder text is harder to finish later.
- About an hour. DNS and certificates can take longer to become visible everywhere.
Important: do not delete the default page or install a second site over an existing one until you have a backup. If the account already has a website, treat this as a migration, not a fresh launch.
Step 1: Choose how the site will be built
| Option | Best for | Maintenance |
|---|---|---|
| Website builder | Simple brochure sites, no code | Low, but tied to the builder |
| WordPress | Blogs, business sites, stores | Regular updates and backups |
| Static site | Documentation, portfolios, fast marketing pages | Low, but needs a build workflow |
| Custom app | Web applications and APIs | High; needs a developer |
If you are unsure, see "Website Builder vs WordPress vs Static Site: Which Should You Use?". Do not install WordPress and a builder on the same domain at the same time.
Step 2: Connect the domain
Point the domain at SysopHost before or while you build. The site will not be reachable at the domain until DNS resolves to the hosting server.
- Use the nameservers from your welcome email, or the A record method if DNS stays elsewhere.
- If the domain is new, allow time for delegation to publish.
- Do not change nameservers and records at the same time.
Full steps: "How to Point Your Domain to SysopHost Hosting".
Step 3: Confirm the domain in cPanel
- Log in to cPanel.
- Open Domains and confirm the domain is listed.
- Check the document root. The main site is usually
public_html; a second site should use its own folder. - If the domain is missing, add it before installing anything.
See cPanel Tutorial for Beginners if the interface is new to you.
Step 4: Install the site
The exact path depends on the platform:
- WordPress: if your cPanel includes WordPress Manager or a one-click installer, use it. Otherwise upload WordPress to the document root and complete the installer. Create a dedicated database and user first.
- Builder: use the builder available on your plan. Site Publisher was removed in cPanel 134; SiteJet Builder is the current cPanel option where enabled.
- Static: upload the built files to the document root. The entry point must be
index.html. - Custom app: follow the application's deployment guide, or see the Coolify articles for container deployments.
Do not install into a folder that already contains another site unless you intend to replace it.
Step 5: Enable HTTPS
A new site should be served over HTTPS from day one. Depending on your plan, cPanel may issue a certificate automatically, or you may need to install one.
- Confirm the certificate covers both
example.comandwww.example.comif both are used. - Enable Force HTTPS Redirect after the certificate is valid.
- Fix mixed content before launch, not after.
See How to Generate a CSR and Install a Paid SSL Certificate and How to Fix "Not Secure" and Mixed Content Warnings.
Step 6: Test before announcing
- Load the home page, every menu item, and a 404 page.
- Submit the contact form and confirm the email arrives.
- Test on a phone, not only on a desktop browser.
- Check that search engines are not blocked by a staging password or
noindextag. - Confirm backups are running.
- Check the site over HTTPS with and without
www.
Step 7: Launch essentials
| Item | Why |
|---|---|
| Backups | A launch is the moment you have the most to lose. |
| Admin email | Password resets, form notices, and security alerts go there. |
| Analytics | You cannot improve what you do not measure. |
| Sitemap and robots.txt | Help search engines find the right pages. |
| Privacy and cookie notice | Required in many jurisdictions if you collect data. |
| Spam protection | Contact forms attract bots within days. |
Security basics
- Use a unique admin password and two-factor authentication.
- Keep the platform, themes, and plugins updated.
- Remove unused themes, plugins, and default accounts.
- Do not use
adminas the username if the platform lets you choose. - Take a backup before the first update, not after it breaks.
See WordPress Security Hardening Checklist for WordPress specifics.
Related articles
- Website Down? Diagnose 403, 404, 500, 502, 503, and 504
- How to Migrate a Website to SysopHost Without Downtime
- Website Builder vs WordPress vs Static Site: Which Should You Use?
- How to Add a Contact Form (and Fix Missing Emails)
- cPanel Tutorial for Beginners
- How to Take a Full cPanel Backup (and Restore It)
If you are not sure which platform or plan fits your site, contact SysopHost support with what the site needs to do, expected traffic, and whether you will maintain it yourself. Do not install a second platform over an existing site.