An AI companion subdomain, such as ai.example.com, gives Answer Cloud content a branded address while the main website stays on its current host. It is a separate integration from a hosted website's custom domain.
The hosted set_custom_domain MCP tool does not manage companion CMS sites. Use the organization's companion integration settings and support-assisted completion instead.
Before changing DNS#
Confirm that your organization already has the intended Answer Cloud companion. Ask your agent to list sites and verify its kind, existing collections, and public address. If no companion exists, contact support to establish the correct setup rather than using the standalone /new launch flow.
Choose an unused subdomain, usually ai. Check that it is not already serving another application. Record the main site's current apex and www DNS records so you can confirm that they remain intact.
You need access to the authoritative DNS provider for the domain and to the Answer Cloud organization that owns the companion.
Add the companion CNAME#
- Sign in to Answer Cloud and select the correct organization.
- Open Integrate from the organization menu and locate its CNAME/subdomain setup instructions.
- Confirm the organization's main domain and companion subdomain.
- At your DNS provider, add the CNAME using the exact Name/Host and target shown by the integration instructions.
- Inspect the saved record to confirm that it names the intended full hostname, such as
ai.example.com. - Contact jared@answer.cloud to complete companion activation after the DNS record is in place, as directed by the current integration flow.
Do not copy a CNAME target from another customer's setup or change the apex and www records. A CNAME cannot share its exact name with conflicting address records, so inspect only the selected subdomain when resolving a conflict.
Verify after activation#
Open the companion's HTTPS address and a known published article. Confirm the certificate, article content, links, styling, and generated discovery resources. The integration panel can report when its llms.txt address is accessible; open that actual URL rather than assuming that a saved DNS record proves the service is ready.
Return to the main website and test its navigation, forms, and any external chat installation. Ask a question based on the companion's published content and check the answer.
A reachable companion does not guarantee that another AI service will cite its pages. Keep content accurate and measure separate outcomes.
If HTTPS or routing is still unavailable after DNS is visible, send support the organization, companion hostname, saved record type/name/target, and the time checked. Keep private account credentials out of screenshots.