/ghl-domain

Agent 46: GHL Domain Connection (S6 GHL ops)

Connects a business's own custom domain to its GHL funnel and assigns custom paths per page. No domain-management API exists in GHL -- this is a manual-fallback unit by design (registrar CNAME + GHL 'Add Domain' screen), but propagation is genuinely verified with a real public DNS-over-HTTPS lookup rather than assumed. Path assignments trace to /ghl-funnel's (#45) own page plan.

verified (fixture) 2026-09-08 · needs-connector: ghlv0.1.0

Run it All agents

Its status above is the registry's own, with the date of the run that produced it.

What it is for

Contract A

#46 — GHL domains · registrar DNS per §3.13; custom paths

Example requests

“connect our domain to GHL”
“point our website's domain at the funnel”
“set custom paths for our pages”
“ghl domain”

What it needs, and what it hands back

Needs connected

Uses WebFetch, which exist in Claude Code. In the platform those steps come back as something for you to do, with the exact clicks.

Hands back

clients/<business-slug>/plans/ghl/domain-<date>.md (checklist, DNS-lookup result, path assignments)

Stops and asks

Nothing this agent does is irreversible on its own, so it asks for no approval of its own. Spending, sending and publishing are approved wherever they happen.

Steps it cannot do through an API, and hands you instead: adding the CNAME/ALIAS record at the business's own registrar; the GHL-side Add Domain and per-page path screen -- no API exposes either.

How it runs

These are the headings of its own written instructions — 203 lines you can read and change.

Step 0 — Environment, connection, and profile
Step 1 — The domain checklist (manual-fallback, by design)
Step 2 — Real DNS propagation check
Step 3 — Custom paths per page