Recent searches

in

What is a Custom Domain?

Last modified: November 4th, 2026

On this page

A Custom Domain is a domain you own and connect to your CloudCannon Organization, so visitors reach your Site at your own address instead of its Testing Domain. For example, CloudCannon's domain is cloudcannon.com. The domain is the part of your URL that visitors are most likely to remember. You can purchase a domain name from a domain registrar.

  • Domain Name — The unique address used to access a website (e.g., cloudcannon.com). This is made of a name of your choice (normally your brand name) and a top-level domain (TLD) from the available list (e.g., .com, .org, .site, .io).
  • Domain Registrar — A third-party company that sells and renews domain names. The registrar records who owns each domain, and which nameservers answer DNS questions about it. You can purchase a domain name from a registrar such as Cloudflare Registrar or Namecheap.
A diagram of a URL shows labels for protocol, subdomain, domain, top-level domain, subdirectory, slug, and path.

Do you need a Custom Domain?#

A Custom Domain can help with brand recognition and search engine optimization.

You don't need to purchase a Custom Domain to create and edit a Site on CloudCannon, as CloudCannon automatically provides a free Testing Domain to all Sites. However, using your Testing Domain as your primary URL has two drawbacks.

One, you cannot change the automatically generated Testing Domain name without creating a new Site on CloudCannon. The automatically generated domain may not be right for you or your Site. You can generate a new one by creating a new Site with the same files; however, recreating a Site takes time.

Two, CloudCannon asks search engines not to index Testing Domains, so they don't appear in search results.

How Custom Domains work#

To use a Custom Domain on CloudCannon you can connect a Custom Domain to your Organization, then add a Custom Domain to your Site. When CloudCannon builds your Site, it serves the new output on your Custom Domain.

You manage each Custom Domain from its Domain page, which you open from the Domains Browser. For more information, please read our documentation on what the Domain page is.

A Custom Domain belongs to one Organization, along with every Subdomain on it. You can't connect a domain that another Organization has already connected, or split its Subdomains between Organizations. When you transfer a Site to another Organization, its Custom Domain and every other Site on it move too. For more information, please read our documentation on resolving ownership over a Custom Domain and transferring a Site between Organizations.

Your Site must be in Hosted Mode to serve it on a Custom Domain. For more information, please read our documentation on what Site Building Mode is.

When you connect a Custom Domain, you choose its DNS Provider. On CloudCannon DNS, CloudCannon manages the DNS records for each Subdomain. On external DNS, you add the records CloudCannon lists at another DNS Provider, such as your domain registrar or Cloudflare. For more information, please read our documentation on what DNS is.

Your Subscription Plan sets how many Custom Domains your Organization includes. The Lite Plan includes 1, the Standard Plan 5, and the Team Plan 10, and you can add more with Add-Ons. The Enterprise Plan doesn't set a limit. CloudCannon counts each Subdomain that serves Sites. Subdomains with no Site yet and Redirect Subdomains are free. If serving a Site on a Subdomain takes your Organization over the number of Custom Domains in its Subscription Plan, CloudCannon asks you to confirm the extra cost first. For more information, please read our documentation on what Add-Ons and Overages are.

In a Client Organization on its extended six-month Free Trial, serving a Site on a Subdomain that had no Sites shortens the trial so that it ends five days later, whether or not the Client Organization is still within the limits of its Subscription Plan. CloudCannon asks you to confirm before it shortens the trial. For more information, please read our documentation on how billing works in the Partner Program.

Subdomains#

Every address you host on a Custom Domain is a Subdomain in CloudCannon, including the Base Domain itself (e.g., example.com). Each Subdomain either serves one or more Sites or redirects visitors to another domain, and has its own hosting, HTTPS, and DNS settings. CloudCannon sends visitors to subdomains you haven't set up to your Fallback Redirect, which is one of the Subdomains on your Custom Domain. On external DNS, visitors only reach a subdomain you haven't set up if you add a wildcard record (e.g., *.example.com⁠) at your DNS Provider. For more information, please read our documentation on what a Subdomain is.

The default robots.txt file#

A robots.txt file tells search engines which pages of your website not to crawl. If your Site doesn't have its own robots.txt file, CloudCannon serves this default file at /robots.txt on your Custom Domain:

Text
Copied to clipboard
User-agent: *
Disallow: /cc-connection-test
Disallow: /update
Disallow: /login
Disallow: /logout

CloudCannon uses these paths on Sites it hosts:

  • /cc-connection-test — CloudCannon answers this path itself to check that your domain reaches CloudCannon.
  • /update — The default path of the Guest Login Page, which sends visitors to CloudCannon to edit the Site. You can change this path. For more information, please read our documentation on configuring the Guest Login Page.
  • /login and /logout — CloudCannon uses these paths to sign visitors in and out of a Site that requires authentication.

CloudCannon doesn't serve a page of your own at /cc-connection-test, or at the path of your Guest Login Page. While CloudCannon serves the default robots.txt file, search engines also skip any page of your own at /login, /logout, or /update. The default file always lists /update, even if you change the path of the Guest Login Page.

If your Site has its own robots.txt file in its build output, CloudCannon serves your file instead of the default. Add the lines above to your file to keep search engines away from the reserved paths.

Your Testing Domain always serves a different robots.txt file, which asks search engines not to crawl any page.

Related Resources

Open in a new tab