Domain Setup
Domain setup covers every DNS and domain-related configuration your team can handle before the onboarding form comes back. Custom domains, SSL certificates, subdomain routing, email authentication records. If it involves a domain and does not require client-specific content decisions, it belongs in this pre-build window.
Why This Matters
Domain propagation takes time. DNS changes can take anywhere from a few minutes to 48 hours to fully propagate, and email authentication records like SPF, DKIM, and DMARC can take even longer to verify. If you wait until the build phase to start domain work, you are adding unnecessary days to the timeline. Days where the client is waiting and wondering why things are not live yet.
Getting domain setup done during pre-build means that by the time your team is ready to build, the infrastructure is already in place. The custom domain is pointing where it needs to point. SSL is issued. Email deliverability records are verified. Your builders can focus on building instead of troubleshooting DNS.
There is also a credibility element. When you send the client a link to their new system and it is on a branded domain instead of a generic GHL subdomain, it reinforces that this is a professional operation. Small details like this compound into the client’s overall perception of your agency’s competence.
How to Think About It
Domain setup is infrastructure work, not creative work. It does not require brand guidelines, content decisions, or client preferences. It requires access to the domain registrar, knowledge of what DNS records need to exist, and the patience to verify everything propagates correctly.
The approach depends on who controls the domain. If the client’s domain is registered with GoDaddy, Namecheap, Cloudflare, or another common registrar, you need either login credentials or specific DNS records for the client to add. Many agencies request registrar access during the sales process or quick start call so the team can handle domain work independently. Others provide the client with exact records to add and verify from their end.
For agencies using GoHighLevel’s built-in website and funnel hosting, you will need to configure custom domains within the GHL Sites module. This typically involves adding a CNAME record pointing to GHL’s servers and verifying ownership. For email sending, you need SPF and DKIM records configured so messages sent through GHL Email do not land in spam.
Think of domain setup as removing a bottleneck before anyone hits it. Every hour spent on DNS during the build phase is an hour that should have been handled here.
Common Mistakes
Waiting until the build phase to start DNS work. This is the most common mistake and the entire reason this element exists in pre-build. DNS propagation is unpredictable. Start it early so propagation delays do not become build delays.
Not requesting domain access during quick start. If you need registrar access and you wait until the build phase to ask for it, you have created a dependency on the client that could stall the entire project. Get access or get the records added during the earliest touchpoint possible.
Forgetting email authentication records. Setting up a custom domain for the website but skipping SPF, DKIM, and DMARC for email is a half-done job. When the build phase hits and your team starts configuring email campaigns through GHL Workflows, messages will bounce or hit spam. Do all the DNS work at once.
Not verifying propagation before moving on. Adding DNS records and assuming they are live is a recipe for build-day surprises. Use a DNS lookup tool to confirm every record has propagated before marking domain setup as complete. Check from multiple locations if possible.
Skipping documentation of the DNS changes made. Six months from now, someone on your team will need to troubleshoot a deliverability issue or add a new subdomain. If nobody documented what records were added, where they point, and why, that troubleshooting session turns into a detective operation.
Tools Involved
Domain configuration within GoHighLevel happens in the Sites module for website domains and the Email settings for sending domain authentication. DNS management depends on the client’s registrar. Common registrars include Cloudflare, GoDaddy, Namecheap, and Google Domains. For agencies managing DNS programmatically, Cloudflare’s API and the GHL MCP endpoints can automate parts of this process. SSL is typically handled automatically by GHL once the domain is verified.
Where This Fits
Domain setup sits in the Pre-Build Setup phase at sequence position 15. It depends on Sub-Account Provisioning being complete, because you need an active GHL sub-account to configure custom domains against. Domain setup runs in parallel with other pre-build work like Reviews AI and Pre-Build Work. All of this happens while the client is filling out the Onboarding Form, so the build phase starts with infrastructure already in place.
Common Questions
What if the client will not give us domain access? Provide them with the exact DNS records to add, including record type, name, value, and TTL. Send screenshots if needed. Some clients are protective of their domain registrar, and that is reasonable. Just make sure you verify the records are added correctly before marking this complete.
Do we need a separate sending domain for email? It depends on volume and risk tolerance. For most small businesses, authenticating their primary domain for email sending through GHL is fine. For agencies sending high volumes or managing clients in competitive industries, a subdomain like mail.clientdomain.com isolates sending reputation from the main domain.
What if the client does not have a domain yet? This happens more often than you would expect, especially with new businesses. Help them register one through a reputable registrar, or handle it as part of your service. Do not let the lack of a domain stall the entire pre-build process. Register it, configure it, and move on.