Connect a custom domain and check your launch

Guides

Prepare access and a change window

You need authority to change the website's domain, access to the domain's DNS provider, and an approved launch time. Confirm the exact website and intended primary hostname. Record the existing domain setting and DNS records before changing them, including mail-related records that must remain untouched.

This guide does not provide generic A or CNAME values. Use the current instructions shown for the selected website and verify them against its actual hosting configuration. Do not copy records from a different workspace, an old screenshot, or an example domain.

Keep a working administrator access route and an approved way to reverse the domain change. Saving a domain is a production change; coordinate it with whoever manages hosting and DNS rather than making it during unrelated content editing.

Connect in the correct order

1. Open Domain for the selected website. Review Beeboo Subdomain, Custom Domain, and Active domain. Enter the intended custom hostname carefully. Do not include an accidental path or choose another website's hostname.
2. Choose Save domain setting. This stores the site's domain choice; it does not itself attach the hostname to Vercel. The interface also notes that the Beeboo subdomain is disabled while custom-domain mode is active, so do not assume both addresses remain interchangeable.
3. In DNS & Verification, choose Create Vercel domain records when the hostname has not been connected. Review the reported result and any verification requirement. If only one hostname is attached, the action is Create missing Vercel domain records. Resolve that partial state rather than treating the connection as complete.
4. At the DNS provider, apply only the records currently required for this website's hostname. Preserve unrelated records, especially email and ownership verification. If existing records conflict, have the domain owner approve their replacement. Never guess a hosting IP address or CNAME target.
5. Return to Beeboo and use Check DNS Status. Attachment, DNS validity, and hostname verification are separate conditions. Pending verification can also mean certificate setup is unfinished. Wait for the reported state and resolve the indicated issue instead of repeatedly disconnecting and reconnecting.
6. Once the hostnames are verified, check the website's separate public/private status with the authorized administrator. Connecting a domain does not publish private content. Review page availability and launch navigation without changing access controls as an accidental side effect.

Test the launch from outside the CMS

Open the primary HTTPS URL in a signed-out browser and follow a deep page link. Check certificate warnings, the expected page, main navigation, forms, and sharing images. Test the relevant www variant and trailing-slash behavior, including a URL with a harmless query parameter. Inspect redirects rather than assuming every alias has the same policy.

If the domain reaches the wrong website, stop promotion and verify site selection and hosting attachment. If verification stays pending, review authoritative DNS and the provider's instructions with the domain owner. Local development does not provide production domain verification. See site administration and domains and search visibility.