GoDaddy DomainControl

If your domain is registered with GoDaddy and your site is hosted on Webflow, connect the two through Quick Connect, manual DNS setup, or API-based workflows. Site design, CMS, hosting, and SSL certificates live inside Webflow — domain registration stays at GoDaddy, so you need to configure DNS records there before your domain resolves to your site.

In GoDaddy DomainControl, you add DNS records, manage nameservers, and set up forwarding. Connecting it with Webflow points your domain to Webflow's servers while keeping registration, renewal, and email at GoDaddy — and an OAuth-based Quick Connect flow can handle the DNS records for you automatically.

How to integrate GoDaddy DomainControl with Webflow

What is GoDaddy DomainControl? Use GoDaddy DomainControl, also called the Domain Control Center, to manage DNS settings on domains registered with or hosted through GoDaddy. It supports A, CNAME, MX, TXT, and SPF record types, along with nameserver management and domain forwarding. DomainControl is active whenever a domain uses GoDaddy's default nameservers (ns01.domaincontrol.com and ns02.domaincontrol.com).

Connect GoDaddy DomainControl with Webflow whenever you need a GoDaddy-registered domain to resolve to a Webflow-hosted site. The domain stays registered at GoDaddy, and only the DNS records change. That separation means email services, WHOIS privacy, and domain renewals continue at GoDaddy without interruption.

You can connect GoDaddy DomainControl with Webflow in 3 ways:

• Quick Connect handles automated DNS configuration through an OAuth flow in the Webflow dashboard, with no manual record entry required.
• Manual DNS configuration lets you add A, CNAME, and TXT records directly in GoDaddy's DNS panel for full control over each record.
• The Webflow and GoDaddy APIs let you manage DNS records and site publishing through code, but require server-side development.

Most implementations use either Quick Connect or manual DNS configuration. Reach for the API path when you need to set up many domains across many sites — typical for agencies and SaaS platforms.

Quick connect your GoDaddy domain

Quick Connect is the native OAuth-based integration that detects GoDaddy as your DNS provider and configures all required DNS records automatically. It creates the A record, CNAME record, and TXT verification record in GoDaddy's DNS panel, then begins SSL certificate provisioning through Let's Encrypt and Google Trust Services. You don't need to enter any records manually in GoDaddy. This method works only when the domain uses GoDaddy's default nameservers (ns01.domaincontrol.com / ns02.domaincontrol.com), and you need a paid Webflow site plan.

To set up Quick Connect:

1. Open Site settings > Publishing > Production.
2. Click Add a custom domain.
3. Select Quick connect domain and click Continue.
4. Enter your domain (e.g., yourdomain.com) and click Continue.
5. Search for and select GoDaddy as your DNS provider.
6. Click Connect with GoDaddy to open the OAuth login.
7. Sign in to your GoDaddy account and click Connect to authorize.
8. Click Close window, then click Done.

After authorization, Quick Connect applies the following automatically:

• An A record pointing the root domain to Webflow's servers
• A CNAME record pointing www to Webflow's CDN
• SSL certificate provisioning (typically completes within 1 to 3 hours)

Before running Quick Connect on a domain with active email services, export or screenshot all existing DNS records. Quick Connect modifies records via OAuth and can overwrite MX, SPF, DKIM, and DMARC records. If you have active email hosting on the domain, use manual DNS configuration instead — it gives you more control over which records change. See the Quick Connect documentation for full details.

Manually configure DNS records in GoDaddy

Use manual DNS configuration if Quick Connect isn't available, if your domain previously used custom nameservers, or if you need to protect existing email DNS records from being overwritten. The full process takes about 10 minutes of active work, plus DNS propagation time.

Add your domain in Webflow

Add the domain in Webflow before you make any changes in GoDaddy. Webflow generates the specific DNS values your site needs, including a unique TXT verification code.

To add the domain:

1. Go to Site settings > Publishing > Production.
2. Click Add a custom domain.
3. Choose Manually add domain.
4. Enter your domain (e.g., yourdomain.com) and click Add domain.

The root domain and the www subdomain are added at the same time. Copy the three DNS values displayed on screen before you open GoDaddy. Always pull values from your own dashboard — the DNS infrastructure is being migrated, and your site may show different values than older documentation.

Configure records in GoDaddy DomainControl

Sign in to your GoDaddy account, go to My Products, find your domain, and click Manage DNS. If GoDaddy displays a message that nameservers aren't managed by GoDaddy, reset them first: go to the Nameservers section, click Manage, and restore to GoDaddy defaults (ns01.domaincontrol.com / ns02.domaincontrol.com). Resetting nameservers wipes all existing DNS records, so document your current records (especially MX and email-related records) before you make this change.

To add the required records:

1. Click Add New Record. Set Type to A, Name to @, and Value to the IP address shown in your Webflow dashboard (for example, 198.202.211.1). Leave TTL at 1 hour. Click Save.
2. Click Add New Record again. Set Type to CNAME, Name to www, and Value to the CNAME target shown in your Webflow dashboard (for example, cdn.webflow.com). Click Save.
3. Click Add New Record once more. Set Type to TXT, Name to _webflow, and Value to the unique one-time-verification=... code from your Webflow dashboard. Click Save.
4. Remove any existing A or CNAME records pointing to previous hosting providers. Conflicting records prevent proper domain resolution.

Verify and publish

Return to Site settings > Publishing > Production and click Check Status next to your custom domain. Once you see a green verification status, click Publish. DNS propagation typically takes a few minutes to a few hours, but can take up to 48 hours depending on TTL settings and ISP caching. A "not secure" browser warning during the 1 to 3 hour SSL provisioning window is expected and resolves automatically.

After both domains resolve, click Make default next to your preferred version (www.yourdomain.com is recommended for GoDaddy domains). Redirects from the non-default version happen automatically. See the manual domain connection guide for the full walkthrough.

Automate domain workflows with Make

Make (formerly Integromat) is the recommended automation platform for GoDaddy domain and DNS management actions alongside a Webflow module. It includes actions for creating domains, deleting DNS records, retrieving domain details, renewing domains, and making arbitrary API calls on the GoDaddy side, combined with CMS operations and site publishing on the Webflow side. The combined GoDaddy and Webflow integration page lists 50 modules total across triggers, actions, and searches.

Triggers and actions available for Webflow and GoDaddy workflows on Make include:

• Webflow form submission trigger > GoDaddy DNS record creation action
• Webflow site published trigger > GoDaddy domain details lookup action
• GoDaddy domain renewal action chained with Webflow site publish action

These workflows fit teams that want automation without building directly against both APIs.

Build with the Webflow and GoDaddy APIs

If you're an agency provisioning domains across multiple client sites or a SaaS platform managing custom domains across many sites, use the Webflow Data API and GoDaddy APIs to manage DNS records and site publishing through code. This setup requires server-side development and familiarity with REST API authentication for both platforms.

For this setup, use:

• The GoDaddy Domains API for DNS record management, domain availability checks, domain registration, and nameserver configuration
• The Data API v2 for custom domain retrieval and site publishing
• Webhooks for real-time events (like site_publish) that can trigger GoDaddy API calls from a receiving server

The Data API can't add custom domains to a site. Add domains manually through the Webflow dashboard before the API can read or publish to them. The GoDaddy DNS side is fully automatable, but the Webflow domain registration step always requires a manual dashboard action. See the custom domain endpoint reference.

Automate DNS record configuration for a new site

Once you've manually added a domain in the Webflow dashboard, you can automate DNS record creation on GoDaddy and trigger a site publish through the Data API. The GoDaddy API uses sso-key authentication, and the Data API uses Bearer token authentication.

To implement automated DNS provisioning:

1. Authenticate with GoDaddy using your API key and secret in the Authorization: sso-key {KEY}:{SECRET} header format. Use PATCH /v1/domains/{domain}/records to add A, CNAME, and TXT records without removing existing records.
2. Call GET /v2/sites/{site_id}/custom-domains to retrieve the domain ID for the connected domain. The domain must already exist in the Webflow dashboard for this call to return results.
3. Call POST /v2/sites/{site_id}/publish with the domain ID in the request body to publish the site to your custom domain.

// Step 1: Add DNS records on GoDaddy (non-destructive PATCH)
await fetch(`https://api.godaddy.com/v1/domains/${domain}/records`, {
  method: 'PATCH',
  headers: {
    'Authorization': `sso-key ${API_KEY}:${API_SECRET}`,
    'Content-Type': 'application/json'
  },
  body: JSON.stringify([
    { type: 'A', name: '@', data: '198.202.211.1', ttl: 600 },
    { type: 'CNAME', name: 'www', data: 'cdn.webflow.com', ttl: 600 },
    { type: 'TXT', name: '_webflow', data: 'one-time-verification=<value>', ttl: 600 }
  ])
});

// Step 2: Retrieve Webflow custom domain ID
const domainsRes = await fetch(
  `https://api.webflow.com/v2/sites/${siteId}/custom-domains`,
  { headers: { 'Authorization': `Bearer ${WEBFLOW_TOKEN}` } }
);
const { customDomains } = await domainsRes.json();

// Step 3: Publish site to the custom domain
await fetch(`https://api.webflow.com/v2/sites/${siteId}/publish`, {
  method: 'POST',
  headers: {
    'Authorization': `Bearer ${WEBFLOW_TOKEN}`,
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    customDomains: [customDomains[0].id]
  })
});

DNS propagation can take up to 48 hours. You can trigger the publish immediately, but the domain won't resolve until propagation completes. The publish endpoint allows 1 successful publish per minute per site.

Verify DNS before publishing to production

A CI/CD-style workflow can check GoDaddy's DNS records before you publish Webflow changes. This adds a verification gate that keeps you from publishing to a domain with misconfigured DNS.

To implement a DNS verification gate:

1. Call GET /v1/domains/{domain}/records/A/@ on GoDaddy's API. Confirm the returned value matches your A record IP.
2. Call GET /v1/domains/{domain}/records/CNAME/www. Confirm the value matches cdn.webflow.com (or the CNAME target from your dashboard).
3. If both records match, call POST /v2/sites/{site_id}/publish to publish the site.

GoDaddy's API returns configured records, not live DNS resolution. To verify propagation, run a separate DNS lookup against a public resolver like dnschecker.org in addition to the GoDaddy API check.

What can you build with the GoDaddy DomainControl Webflow integration?

Integrating GoDaddy DomainControl with Webflow lets you publish Webflow sites on GoDaddy-registered domains without transferring domain registration away from GoDaddy.

• Branded business sites with email continuity: Connect a GoDaddy domain to a Webflow marketing site while keeping GoDaddy-managed email (Google Workspace, Microsoft 365, or GoDaddy Email) running on the same domain. Only the A and CNAME records change, so MX records and email delivery stay intact.
• Multi-subdomain web properties: Route separate GoDaddy subdomains to different Webflow projects from a single domain. You could point www.example.com to your main Webflow site, careers.example.com to a recruiting site, and resources.example.com to a content hub, all managed through GoDaddy's DNS panel.
• Agency client delivery with clean handoffs: Build a client's Webflow site under an agency workspace, connect the client's GoDaddy domain via DNS configuration, then transfer the site to the client's own workspace. The client keeps their GoDaddy domain credentials throughout, and no registrar transfer is needed.
• Automated domain provisioning pipelines: Use the GoDaddy API to batch-configure DNS records across multiple client domains and the Data API to publish each site to its custom domain. If you onboard multiple clients per month, you can script the GoDaddy DNS steps and reduce manual configuration to the single Webflow dashboard step that can't be automated.

If you need more control over batch provisioning or dynamic subdomain creation for multi-tenant platforms, the API integration path covers those cases with the same DNS and publishing methods described above.