Why the customer's own Cloudflare account
Site files are published to your Cloudflare Pages project, so the domain, DNS and certificates stay in your account. CloudSite does not hold your domain or place your site on shared hosting.
That also means you provide a Cloudflare Account ID and an API token with Pages and DNS permissions.
Prepare the Account ID and API token
- Account ID: the 32-character hex string in the Cloudflare dashboard URL.
- Account → Cloudflare Pages → Edit: create projects, upload files and manage domains.
- Zone → DNS → Edit: create or adjust the CNAME record.
- Zone → Zone → Read: list your domains.
- Do not use the Global API Key. Delete a leaked token in Cloudflare immediately.
The binding flow
- Enter the Account ID and API token in CloudSite settings and click verify.
- Publish the site first so the matching Pages project exists.
- Add the domain from the site's domain settings.
- CloudSite calls the Cloudflare API to add the custom domain and create the CNAME.
- Wait for Cloudflare to issue the HTTPS certificate and the status to become active.
Domain limits
The number of domains per Cloudflare Pages project depends on your Cloudflare plan: 100 on Free, 250 on Pro, and 500 on Business/Enterprise.
CloudSite treats the first domain as primary and the rest as aliases. When several domains serve the same content, set a canonical URL or redirect the others.
HTTPS and propagation
- Cloudflare issues and renews certificates automatically; no separate purchase is needed.
- DNS usually takes minutes to propagate, depending on caches and the registrar.
- The first certificate can take a few minutes; use Full (strict) once it is active.
Common failure causes
- The token lacks Pages or DNS permissions.
- The Account ID is wrong, or a token was pasted instead of the Account ID.
- The domain is not in the current Cloudflare account, so records cannot be created automatically.
- The domain is already attached to another Pages project.
- A conflicting A, AAAA or CNAME record exists.