Creating a website in Nicepage is easy with ready-made templates, and publishing it should be just as smooth. Also, when you’re ready to go live, the final step is to connect your domain and make your website publicly available. This guide explains how to properly publish a Nicepage site and avoid the most common launch issues with domains, SSL, and site visibility.
Quick Checklist Before Publishing
Before you connect the domain, ensure:
- Your website is completely saved.
- Every page is published using Nicepage.
- You can manage your domain registrar (GoDaddy, Namecheap, Cloudflare, etc.)
- Old DNS records are deleted if no longer need them.
- Decide whether you plan to use a root domain (yourdomain.com), www version (www.yourdomain.com), or both.
Read more about how to buy a domain name. This helps prevent conflicts later.
Connect Your Domain
To connect a custom domain, you need to update DNS records at your domain provider.
Typically, this includes the A record for the root domain, and the CNAME record for the www subdomain.
These values must match the instructions shown in Nicepage. In the Desktop Application or Online Builder, open the Site Settings -> General Tab, сlick the Connect button, and enter the domain name into the "My Domain" field:
Please check the Setup Guide.
Problem 1: Website Does Not Open After Connecting the Domain
It is one of the most common issues. and, usually, the reasons are:
- A domain points to the wrong IP address.
- The required DNS records were entered incorrectly.
- DNS changes have not propagated yet.
To fix, check your DNS settings in your domain provider panel. Make sure the records match the values provided by Nicepage.
Typical setup includes:
- A Record for the root domain.
- CNAME Record for www
If there are old records from another host, remove them.
Important! DNS Changes Need Time
After updating DNS, changes may take time to appear worldwide. Please note that propagation may take anywhere from a few minutes to several hours, sometimes up to 72 hours. If the site does not open immediately, wait and try again later.
Problem 2: Website Shows "Not Secure" SSL Warning
After connecting your domain, you may see a warning like “Not Secure,” “SSL certificate error,” or “The connection is not private.” In most cases, this happens because DNS needs to be set up correctly before SSL can be issued.
The Most Common Causes are:
Missing www CNAME Record. Many users configure only the root domain and forget the www subdomain. If www.yourdomain.com is missing or broken, SSL may fail.
Extra Old A Records. If your DNS zone still contains old IP addresses from previous hosting, they may conflict with Nicepage verification.
How to Fix It:
- Make sure your DNS zone contains only the necessary records.
- Add the www CNAME as shown in Nicepage.
- Clear any old A records that may conflict.
- Wait until the DNS updates are fully propagated.
- Once the DNS is valid, the SSL certificate is usually generated automatically.
Tip: Do not try to install certificates manually unless necessary. Nicepage usually handles this automatically.
Problem 3: www Version Works, but Root Domain Does Not
Or, it may be the opposite: www.site.com opens, but site.com does not. This means the root and subdomain are not configured together.
To resolve the issue, you can use both:
- A Record for root domain
- CNAME for www
Then set your preferred version so it redirects properly. This gives users a consistent experience and helps SEO.
Problem 4: Domain Is Already in Use
You try to publish the website, but the domain cannot be connected.
You may see issues like:
- The domain is already in use.
- The domain cannot be assigned.
This usually happens because the domain is still linked to another Nicepage project.
The Most Common Causes are:
Domain Is Still Connected to a Previous Website
Many users connected the domain to an older Nicepage project and never removed it. As a result, the system still treats that domain as active on another website.
The Domain Was Used in the Nicepage Online Builder
Sometimes the domain was previously attached to a site created in Nicepage Online Builder. Later, the user tries to publish from Nicepage Desktop using the same domain. The old connection must be removed first.
Old Domain Binding Was Never Cleared
Even if the previous website is no longer in use, the domain may still be assigned in the project settings.
How to Fix It:
- Open the previous Nicepage project
- Remove or unbind the custom domain
- Make sure your changes are saved
- Go back to the new project
- Reconnect your domain
- Publish the website again.
Important! If you recently changed DNS records or moved hosting, wait for propagation before trying again.
Tip: Before launching a new Nicepage site, always check whether the domain is already connected somewhere else.
Problem 5: Site Looks Old After Publishing
You made changes, but visitors still see the old version. Usually, it's an issue with caching.
To fix the issue, you can clear the browser cache and CDN cache. Then reload in Incognito Mode.
Best Practice to Publish a Nicepage Site Correctly
Please follow the steps below to resolve the issue.
- Step 1: Finish design and save changes.
- Step 2: Publish the website through Nicepage and enter your custom domain in the Editor.
- Step 3: Add the DNS records exactly as shown in the instructions.
- Step 4: Allow time for the DNS updates to take effect.
- Step 5: Test both domain versions: yourdomain.com and www.yourdomain.com
- Step 6: Confirm that the website opens with HTTPS.
- Step 7: Test on mobile and desktop.
Conclusion
Nicepage itself is usually not the reason for most publishing problems. These issues are more often caused by DNS settings, SSL configuration, or outdated hosting records. After your domain records are cleaned up and set correctly, publishing usually becomes easier and more stable.
If your Nicepage website is not working after you launch it, check the DNS settings first. In many cases, fixing DNS is enough to solve the problem.