Easy Tech TutsHow to Connect GoDaddy Domain to Webflow, Add Easily 2026
By Impran M NLast checked against official docs
Pointing a domain you bought on GoDaddy at a Webflow site comes down to telling Webflow which domain to expect and making sure DNS routes traffic there. Webflow added a Quick Connect option built specifically for GoDaddy, which handles the DNS side through an authorization flow, so most people no longer need to copy records by hand. This guide covers Quick Connect first, then the manual DNS path for anyone whose domain isn't on GoDaddy's default nameservers, plus the email-safety check that matters most either way.
Before you start
- A domain registered with GoDaddy that you already own
- A Webflow site on a paid Site plan, since custom domain connections require one
01Open the domain settings in Webflow
In the Designer, click Publish in the top right to open the destination picker, or go to Site settings, then Publishing. Under Production you'll see an Add a custom domain link once no custom domain is attached. Clicking it offers two paths: Quick connect domain, which automates the DNS side for supported providers, and Manually connect domain, for anyone who'd rather add the records themselves.
02Try Quick Connect first
Quick Connect uses a service called Entri to detect your DNS provider and configure everything automatically. Choose GoDaddy from the provider list, sign in with your GoDaddy credentials, and authorize Entri to manage the domain's DNS.
Webflow then adds the A and CNAME records for both the root domain and the www subdomain, plus the TXT verification record it needs. This only works if the domain is still on GoDaddy's default nameservers, ns01.domaincontrol.com and ns02.domaincontrol.com. If you've pointed it elsewhere, skip to the manual method below.
03Get your DNS values for a manual connection
If Quick Connect isn't offered, or you'd rather not authorize a third party to touch DNS directly, choose Manually connect domain and type in the domain exactly as you own it, with no https:// prefix. Webflow generates the records your DNS needs: an A record for the root domain, a CNAME for www, and a TXT record used only to verify you control the domain. Copy these values somewhere you can paste from before switching to GoDaddy.
04Log into GoDaddy and open DNS management
From your GoDaddy account dashboard, go to the Domain section for the site you're connecting. This is the same account hub where you manage renewals, billing, and any hosting products tied to the domain, so confirm you're editing DNS on the correct domain if you manage more than one. A wrong edit here affects live traffic immediately, not after a review step.
05Add the A, CNAME and TXT records
In GoDaddy's DNS records editor, set the A record on host @ to 198.202.211.1, add a CNAME record on host www pointing to cdn.webflow.com, and add the TXT record on host _webflow with the one-time-verification value exactly as Webflow displayed it. A single mismatched character fails verification.
Before saving anything, scroll through the existing record list and confirm your MX records are untouched. Those route your email, and they live in the same table as the records you're about to change, which is exactly how people accidentally break their inbox during a domain move.
06Set your default domain in Webflow
Back in Webflow's domain settings, decide whether the root domain or the www version should be the canonical one that the other redirects to. Search engines treat these as separate URLs unless you pick one, so leaving both live without a redirect can quietly split your SEO signals. Most sites default to the root domain, but either choice works as long as it's consistent.
07Check propagation and publish
DNS changes don't take effect instantly. Propagation can run from a few minutes up to 48 hours depending on your previous records' TTL settings.
Use any DNS checker to confirm the new records are visible, then return to the publish panel, check your new domain alongside staging, and click Publish. SSL provisions automatically once Webflow confirms the domain is correctly pointed, so an inactive certificate is usually a sign DNS hasn't fully propagated, not a Webflow-side problem.
| Method | Requirements | What it does |
|---|---|---|
| Quick Connect | Domain still on GoDaddy's default nameservers; paid Webflow Site plan | Signs in to GoDaddy via Entri and adds the A, CNAME and TXT records automatically, for both root and www |
| Manual DNS | Access to GoDaddy's DNS records editor; paid Webflow Site plan | You copy the exact A, CNAME and TXT values Webflow generates into GoDaddy yourself |
From Webflow's official Help Center.
When it doesn't work
Quick Connect isn't offered as an option
Why: The domain isn't using GoDaddy's default nameservers, ns01.domaincontrol.com and ns02.domaincontrol.com, which Quick Connect needs to detect GoDaddy as the provider.
Fix: Use the manual DNS method instead, or point the domain back at GoDaddy's default nameservers first if you'd rather use Quick Connect.
The TXT record won't verify
Why: The value was copied with an extra space or a truncated character, or it was added under the wrong host.
Fix: Recopy the one-time-verification value from Webflow exactly, and confirm it's on the host _webflow, not the root domain.
Email stops working after the domain change
Why: An MX record was edited or deleted while adding the A, CNAME and TXT records, since they live in the same DNS table.
Fix: Compare the current MX records against what your email provider expects and restore any that changed.
SSL certificate isn't active yet
Why: SSL provisions only after Webflow confirms DNS has fully propagated, which can take up to 48 hours.
Fix: Wait and recheck the domain status in Webflow's publish panel instead of assuming something failed.
Frequently asked questions
What's the difference between Quick Connect and manual DNS?
Quick Connect signs in to GoDaddy through an authorization service called Entri and adds the required records for you; it only works if the domain is still on GoDaddy's default nameservers. Manual DNS means copying the A, CNAME and TXT values Webflow gives you into GoDaddy's DNS editor yourself, and it works regardless of nameservers.
Will connecting my domain break my existing email?
It shouldn't, as long as your MX records are left untouched while you add the records for Webflow. Check the full record list in GoDaddy before saving any changes, or before authorizing Quick Connect.
Do I need both an A record and a CNAME record?
Yes, for a manual connection: the A record on host @ points the root domain to 198.202.211.1, and the CNAME on host www points to cdn.webflow.com. Quick Connect adds both automatically.
How long does it take for the domain to go live?
DNS propagation can take anywhere from a few minutes to 48 hours depending on your provider and the TTL on your existing records, so don't assume something's broken if it's not instant.
Why isn't my SSL certificate showing as active?
SSL provisioning depends on DNS fully propagating first, so give it time and recheck the domain status in Webflow's publish panel before assuming something is wrong.
Sources and last check
Click path and screens come from a walkthrough recorded before Webflow added Quick Connect. Re-checked against Webflow's official Help Center in September 2026: this rewrite adds the Quick Connect and Entri path for GoDaddy specifically, confirms the exact A, CNAME and TXT values, and adds the paid-plan requirement, none of which the original draft stated.
About the author
Impran M N
I've been hooked on technology for as long as I can remember — especially the new tools and AI apps that seem to land every other week. Easy Tech Tuts is where I write up whatever I've just worked out: I do the task in the real product, record the screen, and turn it into the guide I wish I'd found first.
