---
title: "Connecting a domain to Coframe Landing Pages, for engineers | Coframe guidebook"
description: "What a DNS or web admin needs to point a subdomain, root domain or site folder at Coframe. One or two records. Five minutes."
url: https://www.coframe.com/guide-for-your-engineer
format: agent version of this page (the same facts as the page, as text)
updated: 2026-11-03
---

| Question | Example | What you add | Good for |
| --- | --- | --- | --- |
| Subdomain | `go.yourbrand.com` | One `CNAME` to `pages.cofra.me` | Most teams. Independent of your main site. |
| Root domain | `yourbrand.com` | An `ALIAS`/`ANAME` at the root (or a flattened `CNAME`) plus a `CNAME` for `www` | A domain bought for one campaign or product. Coframe serves the whole domain. |
| Subfolder | `www.yourbrand.com/lp/` | A proxy or rewrite rule on the platform that serves your site | Sharing your root domain's search authority. |

## The two-step setup

1. Step 1: **Verify and issue the certificate first.** The Domains panel lists a `TXT` record and an `_acme-challenge` `CNAME`. These don't change where the domain points, so nothing goes down. The panel re-checks every 30 seconds.
2. Step 2: **Then point the domain at Coframe.** Add the `CNAME` (or the root `ALIAS`). The certificate already exists, so the switch has no downtime.

The exact names and values are in the panel, and the marketer can send you a link that shows them. That link needs no login.

## Things that trip people up

- **Cloudflare:** set the records to **DNS only** (gray cloud).
- **CAA records:** if your domain has them, allow `letsencrypt.org`, `pki.goog` and `ssl.com`.
- **Root domains:** plain `CNAME` records aren't allowed at the root. Use your provider's `ALIAS`/`ANAME`, or serve the site on `www` and forward the root. Route 53, GoDaddy and Google Cloud DNS don't support alias records to outside hosts.
- **Never copy IP addresses** into `A` records. They change.

## Security notes

- Coframe is SOC 2 Type II.
- Pages are served from a global edge network with automatic HTTPS.
- Your DNS stays with you. Removing the record removes the pages from your domain.
- Nothing is installed on your main site unless you choose the subfolder option.

## 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=6ad27cd664e466030bcdc6c7&token=d78292989e330c78d156eb6a&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=6ad27cd664e466030bcdc6c7&token=d78292989e330c78d156eb6a&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": "6ad27cd664e466030bcdc6c7", "token": "d78292989e330c78d156eb6a" }
```

- **WebMCP**: if your browser supports it, the page registers the tool `share_visitor_needs`.

`needs` is up to 2000 characters; `constraints` up to 1000.