# Connect a domain to your AI-built landing page

> Use your own hostname for a published Pageree page. Understand the returned DNS record, certificate checks, apex-domain limits, and verification steps.

- Canonical: https://pageree.com/guides/ai-landing-page-custom-domain/
- Published: 2026-09-15. Updated: 2026-09-15.
- Collection: Guides (https://pageree.com/guides.md)
- Site index for agents: https://pageree.com/llms.txt

**The short answer.** Publish the page first, then give your assistant the exact hostname you own. Pageree returns the DNS record to add at your provider. After you add it, check the domain status and open the HTTPS address. Use the returned record rather than a guessed target.

## Pick the hostname before changing DNS

A hostname is the exact address that should serve the page: for example, `get.example.com` rather than the broad instruction “use my website.” Choose a hostname you own and check whether it already serves something important.

For an existing business website, a campaign subdomain is often a practical organizational choice. It avoids replacing the main site's address while you test a focused offer. It is not an automatic search-ranking advantage.

Pageree's custom-domain workflow starts with an already published page. The hosted page address continues to work when a custom hostname is added. Use a consistent preferred URL in your page metadata and links rather than treating both addresses as separate pieces of content.

## Ask Pageree for the actual DNS record

Connect your assistant and identify the existing page. Then make the request specific:

```text
Connect the hostname [the exact hostname I own] to my existing published Pageree page.

Read the custom-domain instructions first. Check which page will use the hostname, explain any existing assignment, and ask before disconnecting anything. Return the exact DNS record from the setup response. Do not guess a CNAME target or alter unrelated DNS records.
```

The returned record contains the target your DNS provider should use. Copy that value from the actual response. A target pasted from somebody else's example can point the hostname at the wrong service.

The agent can explain the steps; you may still need to sign in to the provider that manages your domain. Do not share the provider password in the conversation.

## Add the record at your provider

For a supported subdomain setup, create the CNAME record described by the returned instructions. Check how your provider represents the name: some interfaces want only the subdomain label, while others accept the full hostname. Review the resulting record before saving.

If a conflicting record already exists for the hostname, investigate what uses it. Do not delete a record simply because a tutorial shows a clean DNS screen. Changing the main business website or an active campaign address can interrupt its existing visitors.

Apex domains, such as `example.com` without a subdomain, require provider support for CNAME flattening or ALIAS-style behavior in this workflow. If your provider cannot support it, choose a suitable `www` or campaign hostname. Pageree's current instructions also call for DNS-only mode when the CNAME sits in the user's own Cloudflare account.

## Check status and HTTPS

After adding the record, ask the assistant to check the custom-domain status. Read any returned errors before changing additional settings. A pending state can mean the record is not visible yet or that its name or target is wrong.

When the domain is active, open the HTTPS address yourself. Confirm the intended page, images, internal links, and form. The certificate is part of the hosting setup; a green-looking dashboard state should still be followed by a browser check.

| Symptom | Useful check |
|---|---|
| Wrong page appears | Confirm the hostname, existing DNS record, and page assignment. |
| Status stays pending | Compare the visible DNS name and target with the returned instructions. |
| Certificate error | Inspect domain status and certificate errors; do not tell visitors to bypass the warning. |
| Form stops working | Test the page's same-origin form route and published markup on the new hostname. |

## Finish the launch checks

Submit a clearly marked test on the new public address and verify its final destination. Update the preferred canonical URL, social metadata, and links where appropriate. Use the [SEO checklist](https://pageree.com/guides/landing-page-seo-checklist/) to keep those signals consistent.

If the page came from Claude, the [artifact publishing guide](https://pageree.com/guides/publish-claude-artifact/) explains the earlier adaptation step. For an existing ChatGPT file, see [publishing HTML](https://pageree.com/guides/publish-chatgpt-html/).

Keep a record of which page uses the hostname. Moving it later requires a deliberate change; disconnecting an active domain can stop it serving the page immediately. Review that operation before applying it.

## Related
- [Landing-page custom domain not working?](https://pageree.com/guides/landing-page-domain-troubleshooting.md): Diagnose a landing-page domain problem by checking the exact hostname, DNS record, routing status, certificate, and redirects before changing the page.
- [Custom domain or hosted subdomain for your landing page?](https://pageree.com/guides/landing-page-domain-options.md): Compare hosted and owned landing-page addresses by setup, brand, continuity, and maintenance. Plan canonical URLs and migration without assuming SEO gains.
- [SEO checklist for an AI-built landing page](https://pageree.com/guides/landing-page-seo-checklist.md): Check search intent, titles, crawlability, canonical URLs, mobile experience, and useful content. A practical SEO checklist for a single landing page.

## Build it with your agent

Pageree is an MCP server. Add https://mcp.pageree.com/ to an MCP client that supports Streamable HTTP and OAuth, sign in, and the agent can build, publish and measure the page. Setup for every supported client: https://pageree.com/docs.md. Sign up: https://console.pageree.com/signup.