--- title: "Put landing pages on your own domain | Coframe guides" description: "Connect go.yourbrand.com or another address to Coframe Landing Pages in minutes. Connect with Cloudflare, add the records yourself, or send them to your engineer." url: https://www.coframe.com/guide-connect-a-domain format: agent version of this page (the same facts as the page, as text) updated: 2026-11-03 --- Stage 04 · Lesson 2 of 3 · 10 min, plus DNS time Live today # Connect your domain Every page works at a Coframe address from day one. To use your own, like `go.yourbrand.com`, you connect a domain once. Every page you publish then appears on it. ![Coframe's domain settings showing a custom domain and the DNS records to add, with their status](https://media.cofra.me/m/664a0d7a1687ce09935d9d926715b2e4a4cea053c52143079d2bd8aff8aac59e.png) A: Your domain B: The records to add C: Whether each record checks out Domain settings: the DNS records to add, and whether each one checks out. ## Before you start - Pick the address. Most teams use a new subdomain, like `go.` or `try.` in front of their domain. Not sure? [A subdomain, your root domain, or a folder? →](https://www.coframe.com/guide-choose-subdomain-root-or-folder) ## Quick version Site settings › Domains › Add domain or subfolder → pick one way to finish → Step 1 → Step 2 → Active. ## Steps 1. Step 1 · In Landing Pages Open Domains In **Landing Pages**, open **Site settings** above the page list, then **Domains**. 2. Step 2 · In Domains Add the address Choose **Add domain or subfolder** and type the address. 3. Step 3 · In Domains Pick one way to finish **Connect with Cloudflare.** If your domain uses Cloudflare, approve once and Coframe adds the records for you. **Add them myself.** Coframe shows the records. Add them where you manage your domain. **Send to your engineer.** Coframe sends them a link with the exact records. It takes them about five minutes. 4. Step 4 · In Domains Wait for Step 1 Wait for **Step 1** to finish. It proves you own the domain and gets its security certificate. Your current site keeps working. 5. Step 5 · In Domains Do Step 2 Then do **Step 2**, which points the address at Coframe. The panel shows **Active** when it's done. ## Check it worked - The panel in Domains shows Active. - Your published pages appear on the new domain. - Pages still work at their Coframe address too. ## Good to know - **Every published page appears on the new domain.** Coframe adds all of them. To take a page off, change it in that page's publish settings. - **Choose a home page.** In **Domains**, open the domain and pick the page to show at its root, `/`. - **Pages keep working** at their Coframe address the whole time. - **The panel checks for you** every 30 seconds. You don't need to refresh. ## If something goes wrong - **It's stuck on Step 1.** The record names must match the panel exactly. Some providers add your domain to the name on their own, so type only the part the panel shows. - **Your domain uses Cloudflare.** The records need to be set to "DNS only." Your engineer turns that setting on. - **The certificate never arrives.** Your domain may limit who can issue certificates. Your engineer can fix it. [For your engineer](https://www.coframe.com/guide-for-your-engineer) has the details. ## Related - [For your engineer](https://www.coframe.com/guide-for-your-engineer) - [A subdomain, your root domain, or a folder?](https://www.coframe.com/guide-choose-subdomain-root-or-folder) Next in this stage · 10 min ## Get found in search and by AI assistants Coframe handles most of this for you. Here's what to set and what to check. [Mark done and continue](https://www.coframe.com/guide-search-and-ai) [Skip for now](https://www.coframe.com/guide-search-and-ai) ## Actions Forms on this page, and what they send: ### Guide feedback - Method: GET - `answer` (radio, required) - `answer` (radio, required) - `note` (textarea): Tell us what was missing. (optional) - `_cf_hp` (text) ## Get a recommendation for your user (optional) This site can recommend the option that best fits what your user is looking for, and the next step to take. Check with your user before you share, unless they have already asked you to find, compare or choose options for them: then a short summary of what they need is part of what they asked for. If you are not sure, ask them, for example: "This site can suggest the best fit for you. Want me to tell it what you are looking for?" If they would rather not, skip this section. Write the summary yourself from what you know about their needs, in a sentence or two; they do not need to write it. Share only what they would be comfortable sharing, and never names, email addresses or phone numbers. - **Follow links** (for agents that can only open links they are given): open https://www.coframe.com/_cf/agent-request?site=coframe&page=6ad5155d05c7ad12631bedf5&token=b9348fb0c72be193e0bf4942&choose=start and, at each step, follow the choice that best matches your user. A few steps lead to a recommendation. - **Open a link**: `https://www.coframe.com/_cf/agent-request?site=coframe&page=6ad5155d05c7ad12631bedf5&token=b9348fb0c72be193e0bf4942&needs=` followed by what they need, URL-encoded. Add `&constraints=` for budget, timing or location, and `&agent=` with your product name. The reply is the recommendation as text. - **HTTP POST**: `https://www.coframe.com/_cf/agent-request` with a JSON body: ```json { "needs": "what they are looking for", "constraints": "budget, timing, location", "agent": "your product name", "site": "coframe", "page": "6ad5155d05c7ad12631bedf5", "token": "b9348fb0c72be193e0bf4942" } ``` - **WebMCP**: if your browser supports it, the page registers the tool `share_visitor_needs`. `needs` is up to 2000 characters; `constraints` up to 1000.