Sites Overview
Sites are the publishing destinations for your Atomicat pages.
In Atomicat, a site connects three important parts of your online presence:
- The pages you build in the page builder
- The domain or Atomicat-provided URL visitors use to access those pages
- The hosting, DNS, SSL, and publishing settings that make the pages available online
Use Sites when you want to publish landing pages, sales pages, quizzes, lead capture pages, product pages, and campaign flows under a reliable URL.
How sites work in Atomicat​
A site acts like a container for published URLs.
When you publish a page, you choose:
- The site or domain where the page should be published.
- The URL slug for that page.
- Whether the page should replace an existing URL or publish to a new path.
For example:
| Site or domain | Page slug | Final URL |
|---|---|---|
brand.com | / | https://brand.com/ |
brand.com | offer | https://brand.com/offer |
brand.com | quiz | https://brand.com/quiz |
campaign.atomipages.net | webinar | https://campaign.atomipages.net/webinar |
This structure helps you keep pages organized and avoids publishing every page as a disconnected link.
What you can manage from Sites​
Depending on your plan, setup, and enabled modules, the Sites area may let you:
- Create a new site
- Use an Atomicat domain or subdomain
- Connect a custom domain
- Verify DNS records
- Request or check SSL
- Open the live site
- Assign sites to projects
- Connect an image domain
- Manage Turbo Hosting when available
- Clear or unpublish existing published pages
- Delete sites when allowed by account permissions
Some options may not appear if your plan, account setup, module access, or project permissions do not include them.
Sites, pages, and domains​
These terms are related but different.
| Term | Meaning |
|---|---|
| Page | A single web page built in Atomicat, such as a landing page or sales page. |
| Site | A publishing destination that can hold one or more page URLs. |
| Atomicat domain | A domain or subdomain provided by Atomicat for publishing without connecting your own domain first. |
| Custom domain | A domain you own, such as yourbrand.com, connected through DNS records. |
| Slug | The path after the domain, such as /offer, /quiz, or /thank-you. |
| SSL | The secure HTTPS certificate that protects the published URL. |
Recommended publishing workflow​
For most users, the best workflow is:
- Create a site.
- Publish a test page using the Atomicat domain.
- Connect a custom domain when the campaign is ready.
- Add or verify the required DNS records at your domain provider.
- Check SSL after DNS is correct.
- Publish final pages using clear URL slugs.
- Test every live URL on desktop and mobile.
This workflow reduces launch risk because you can build and preview before pointing a production domain to Atomicat.
When to use an Atomicat domain​
Use an Atomicat domain when:
- You want to publish quickly.
- You are testing a page before connecting a custom domain.
- You do not yet own a domain.
- You need a temporary campaign URL.
- You want to confirm the page works before editing DNS.
When to use a custom domain​
Use a custom domain when:
- You are launching a professional campaign.
- You want stronger brand trust.
- You are sending paid traffic.
- You need cleaner URLs for ads, SEO, or email.
- You want users to recognize your brand in the browser.
Custom domains are especially important for conversion-focused pages because the domain is part of the visitor’s trust experience.
Best practices​
- Use one site per brand, campaign group, or main publishing destination.
- Use clear slugs such as
offer,webinar,quiz, orthank-you. - Avoid changing DNS during active campaigns unless you understand the impact.
- Confirm SSL is active before sending traffic to a custom domain.
- Test forms, pixels, buttons, and redirects after publishing.
- Keep old test pages separate from live campaign pages.
- Use projects to organize sites when you manage multiple campaigns, clients, or brands.
Frequently asked questions​
Is a site the same as a page?
No. A page is the content you build. A site is the destination where one or more pages can be published.
Can I publish before connecting a custom domain?
Yes. You can use an Atomicat domain first, then connect a custom domain later when the campaign is ready.
Why does my Sites area look different?
The available options can change based on plan, account setup, enabled modules, permissions, and product updates.
Do I need SSL for every custom domain?
Yes. SSL is required for secure HTTPS access. Atomicat helps request and verify SSL, but DNS must be correctly configured first.