How do AI website builders connect multiple domains?

What you need before connecting

If the domain lives in a different Cloudflare account, add it first or follow the prompt to configure a CNAME. The Cloudflare guide covers token permissions and domain onboarding.

• A domain already added to Cloudflare, or one whose DNS you can edit.
• A Cloudflare Account ID and an API token with Pages permissions, entered in CloudSite settings.
• A site that has been published at least once, so the Pages project exists.

Primary domain vs alias

The primary domain is the preferred public address, used for share links and canonical URLs. Aliases serve the same site and are useful for old domains, campaign domains or regional backups.

When several domains point at the same content, keep one primary and redirect or canonicalize the rest. Otherwise search engines may see several duplicate pages competing with each other.

How DNS and HTTPS are handled

CloudSite calls the Cloudflare API to add the custom domain to the Pages project and creates or adjusts the CNAME record. Cloudflare issues and renews the HTTPS certificate.

DNS usually takes minutes to propagate. The status moves through initializing and verifying to active; failures include an error message.

SEO impact of multiple domains

• Pointing the same content at many domains does not raise rankings; it can split authority.
• Set a canonical URL so one address is clearly primary.
• For different languages or regions, use hreflang instead of copying the page.
• Do not stack many near-identical domains on one page — that is classic site-network abuse.

Common failure causes

• The API token lacks Pages or DNS permissions.
• The domain is not in the current Cloudflare account, so records cannot be created automatically.
• The domain is already attached to another Pages project and must be detached first.
• DNS caches have not refreshed, so the status stays in verification.