Domain Checklist Before Website Launch

Launching a website does not just consist of uploading files or installing WordPress. For a website to be reliably accessible, several technical areas must work together: domain, DNS, hosting, Document Root, SSL certificate, HTTPS redirection, email deliverability, and, if applicable, redirects from old URLs.

This checklist is aimed at customers who are publishing a new website, moving an existing website to CURIAWEB, or connecting a new domain to a hosting package.

1. Domain registered and active?

First, check whether the domain is actually registered and active. A domain that is not registered, expired, or locked cannot be reliably connected to the hosting.

• Is the domain registered?
• Is the domain paid for and not expired?
• Can the domain be found at the correct registrar?
• Are there locks, transfer statuses, or registry problems?

2. Domain created in cPanel?

The domain must be set up in the cPanel account so that the web server knows which website to deliver for this domain.

1. Log in to cPanel.
2. Open the Domains section.
3. Check whether the domain appears in the list.
4. If not, click on Create A New Domain.
5. Create the domain with the appropriate Document Root.

3. Document Root correct?

The Document Root is the folder from which the website is loaded. If it is incorrect, another website or a blank page may appear.

Check:

• does the domain point to the desired folder?
• are the website files located in this folder?
• does a start file such as index.php or index.html exist?
• was WordPress or the CMS installed in the correct directory?
• was the main directory public_html/ used by mistake?

4. DNS and nameservers correct?

The domain must technically point to the CURIAWEB hosting. Depending on the setup, this is done via the CURIAWEB nameservers or via individual DNS records at the external DNS provider.

Check:

• are the correct nameservers being used?
• does the A record point to the correct CURIAWEB server IP?
• is an incorrect AAAA record present?
• is www set up correctly?
• has the DNS change been waited for long enough?

5. SSL certificate valid?

Before launching, the website should be accessible via HTTPS. Check the SSL/TLS Status section in cPanel. There you can see whether a valid certificate exists for the domain.

Check:

• is the main domain secured via SSL?
• is www also secured?
• are relevant subdomains secured?
• has AutoSSL worked successfully?
• does the browser show a padlock or no security warning?

6. HTTPS redirection active?

If the SSL certificate is valid, the website should automatically redirect from HTTP to HTTPS. In cPanel, this can be enabled in the domain management via Force HTTPS Redirect.

Test:

• http://yourdomain.ch redirects to https://yourdomain.ch,
• http://www.yourdomain.ch redirects correctly,
• there is no redirect loop,
• the website shows no mixed content warnings.

7. www or without www specified?

Decide which variant should be your main domain: with www or without www. Both variants should be accessible, but in the long term, one variant should redirect to the preferred version via a 301 redirect.

Example:

• yourdomain.ch is the main variant,
• www.yourdomain.ch redirects to yourdomain.ch,
• or vice versa, if you prefer www.

8. Email and deliverability checked?

If the domain is used for email, email reception, sending, and authentication should be checked before launching. MX, SPF, DKIM, and DMARC are particularly important.

Check:

• are email accounts created?
• does email reception work?
• does sending work?
• are MX records correct?
• are SPF, DKIM, and DMARC set up?
• have external services such as Microsoft 365, Google Workspace, or newsletter tools been taken into account?

9. Old URLs and redirects checked?

If an existing website is replaced or moved, important old URLs should redirect to appropriate new pages. This is important for visitors and search engines.

Check:

• are there old pages with important search engine rankings?
• are there old URLs from Google, brochures, social media, or emails?
• have 301 redirects been set up?
• do old URLs redirect to topically appropriate new pages?
• are there no redirect loops?

10. Website functions tested?

Before launching, not only the homepage and design should be checked. Test all important functions of the website.

• contact form sends correctly,
• form emails do not land in spam,
• login areas work,
• shop orders work,
• payment methods are set up correctly,
• links and menus work,
• images and downloads load correctly,
• website works on smartphone and desktop,
• legal notice, privacy policy, and contact details are up to date.

11. Search engines and SEO basics checked

For a clean launch, basic SEO settings should also be correct.

• page titles and meta descriptions make sense,
• website is not accidentally set to "noindex",
• sitemap is present,
• robots.txt does not block important content,
• old URLs redirect correctly,
• main domain is consistently defined with or without www,
• HTTPS is active,
• canonical URLs are correct, if used.

Compact Launch Checklist

When should CURIAWEB support be involved?

Contact CURIAWEB support if you are unsure whether DNS, SSL, email, or the cPanel domain are set up correctly. A careful check before launching is highly recommended, especially for existing business websites and active email services.

The following details are helpful:

• affected domain,
• planned launch date,
• whether email runs via CURIAWEB or externally,
• whether an existing website move is taking place,
• whether old URLs need to be redirected,
• whether external DNS providers like Cloudflare are used.

Frequently Asked Questions Before Launch

Can I put the website live before DNS is switched?
The website can be prepared, but it will only be correctly accessible to the public once the DNS points to the correct hosting.

Should I delete old hosting data immediately?
No. Keep old data at least until after successful DNS propagation and functional testing.

When do I activate HTTPS?
Only when a valid SSL certificate is present.

What is the most common mistake during a launch?
Often, an incorrect Document Root, uncopied email DNS records, or missing SSL are the cause.

Can CURIAWEB help with the launch?
Yes, CURIAWEB support can check technical points such as domain, DNS, SSL, and cPanel configuration.