How to Switch DNS to Webflow and Go Live (Step-by-Step, 2026)

To switch DNS to Webflow: in Site Settings → Publishing, add your custom domain. Webflow shows the required A records (75.2.70.75 and 99.83.190.102) and CNAME record (proxy-ssl.webflow.com). Add these at your domain registrar (GoDaddy, Namecheap, Cloudflare, etc.), wait 24–48 hours for propagation, then click Publish in Webflow. SSL is enabled automatically.

‍Connect custom domain Webflow takes less than 15 minutes of actual work, but DNS propagation can require up to 48 hours for global visibility. This final step transforms your webflow.io staging site into a professional, branded web presence that builds trust, improves SEO, and creates memorable user experiences.

Going live with a Webflow site means pointing your custom domain's DNS records to Webflow's hosting servers. The process takes 10 minutes of configuration plus 24–48 hours of DNS propagation. This guide covers exactly which DNS records to add (A records, CNAME, root vs www), how to handle the redirect between root and www, what to do if SSL fails to provision, and the post-launch checklist to verify your site is live correctly.

Pre-Launch Requirements and Preparation

Essential Prerequisites

1. Paid Webflow site plan 

It enables custom domain connection. Free plans restrict publishing to webflow.io subdomains only. Basic plans ($14/month) support custom domains, while CMS, Business, and Enterprise plans offer additional features for content-rich or high-traffic sites.

2. Custom domain ownership 

Requires purchasing a domain from registrars like GoDaddy, Namecheap, Cloudflare, Google Domains (now Squarespace), or similar providers. Ensure you have registrar account access to modify DNS settings.

3. Completed website design and testing 

You should finish before initiating domain connection. Content, functionality, and design should be final or near-final to avoid publishing incomplete work to your custom domain.

4. Backup and version control 

It protects against launch issues. Create a backup restore point in Webflow before making final changes. Document current settings for quick rollback if needed.

Pre-Launch Testing Checklist

1. Responsive design verification 

It processes across all breakpoints, ensuring a consistent experience. Test desktop, tablet, and mobile views thoroughly, checking that all content displays properly and interactions work across device sizes.

2. Browser compatibility testing 

It validates functionality in Chrome, Firefox, Safari, and Edge. Different browsers render CSS and JavaScript differently, so comprehensive testing prevents browser-specific issues.

3. Form submission testing

It confirms all forms deliver emails correctly, display appropriate success messages, and handle validation errors gracefully. Test with real email addresses to verify delivery.

4. Link checking and validation 

It prevents broken internal and external links. Verify navigation menus, footer links, CTA buttons, and content links all point to correct destinations.

5. Performance optimization 

Image compression, script minification, and asset optimization, ensures fast loading speeds. Run Google PageSpeed Insights tests and address any major performance issues before launch.

DNS Basics for Webflow

1. DNS (Domain Name System) records 

It translates human-readable domain names like yoursite.com into IP addresses that computers use to locate servers. When someone visits your domain, DNS records tell their browser where to find your website.

2. Webflow DNS A records: which IPs to use

For the root domain (e.g., yourdomain.com  without the www), Webflow requires two A records pointing to its load balancers:

• 75.2.70.75
• 99.83.190.102

Add both records at your domain registrar. The "Host" or "Name" field should be <code>@</code> (which represents the root domain at most registrars). The "Value" is each IP address one row per IP.

For the www subdomain, use a CNAME record (covered in the next section) instead of an A record.

3. CNAME Records point subdomains 

Your website (www.yoursite.com) to other domain names. Webflow requires a CNAME record pointing www to proxy-ssl.webflow.com, which handles SSL certificates and routing.

4. Root domain vs www subdomain 

This distinction affects configuration. The root domain (yoursite.com) uses A records, while the www subdomain uses CNAME. Most businesses set www as the default, redirecting the root to www automatically.

5. DNS propagation 

It describes the time required for DNS changes to spread globally across internet service providers and DNS servers. Propagation typically completes within 4-24 hours but can take up to 48 hours.

Webflow's DNS Requirements

1. Two A Records pointing to Webflow IPs provide redundancy and load balancing. Both IP addresses (75.2.70.75 and 99.83.190.102) must be added as separate A Records with @ or blank host values.
2. CNAME Record for www subdomain enables Webflow's SSL certificate provisioning and secure hosting. The www subdomain must point to proxy-ssl.webflow.com exactly as specified.
3. Why these specific configurations relate to Webflow's infrastructure design. The dual A Records provide failover capability if one server experiences issues, while the CNAME enables Webflow's automated SSL certificate management.
4. Common registrar differences affect interface and terminology but not underlying DNS record requirements. Some registrars use "Host" while others use "Name," some show "@" while others leave it blank for the root domain, but the result remains identical.

DNS and Domain Connection

Step 1: Adding Your Domain to Webflow

Accessing Domain Settings

Navigating to Site Settings begins in Webflow Designer:

1. Open your project in Webflow Designer

2. Click the Settings icon in the left sidebar

3. Navigate to the "Publishing" tab

4. Click on "Production" section

5. Locate "Add custom domain" button.

Publishing tab and Production section 

Distinguish between staging (webflow.io) and production (custom domain) environments. Production settings control your live, public-facing website.

Add Custom Domain button 

The custom domain button initiates the domain connection process. This button appears only on projects with paid site plans. Free plans cannot add custom domains.

Domain name format requirements 

Accept both root domains (yoursite.com) and www subdomains (www.yoursite.com). Webflow recommends entering just the root domain, which automatically adds both versions.

Quick Connect vs Manual Setup

The Quick Connect option (Entri integration) automates DNS configuration for supported registrars. Webflow partners with Entri to modify DNS records automatically after you authorize the connection.

Benefits of Quick Connect include:

• Automated DNS record creation
• No manual DNS configuration required
• Faster setup (typically 5-10 minutes)
• Reduced chance of configuration errors
• Automatic record updates if needed

Supported registrars for Quick Connect include major providers like GoDaddy, Namecheap, Google Domains (Squarespace), Domain.com, and others. Webflow displays supported registrars during the Quick Connect flow.

When to choose manual setup:

• Your registrar doesn't support Quick Connect
• You prefer manual control over DNS records
• Your domain uses advanced DNS configurations
• Corporate DNS policies require manual approval
• You're using Cloudflare or DNS Made Easy

Step 2: Configuring DNS Records

Accessing Your Domain Registrar

Finding DNS management section varies by registrar but typically lives in account settings under "DNS," "DNS Management," "Nameservers," or "Domain Settings".

Common registrar interfaces include:

• GoDaddy: My Products > Domains > DNS Management
• Namecheap: Domain List > Manage > Advanced DNS
• Cloudflare: DNS > Records
• Google Domains: DNS > Custom records

Preparing for DNS changes includes:

• Taking screenshots of existing DNS records
• Documenting current configuration
• Identifying records to delete
• Noting email-related records (MX, TXT) to preserve

Backing up existing records 

It protects against accidental deletion of critical records like email configuration. Export or screenshot all existing records before making changes.

Adding A Records

Creating first A Record (75.2.70.75):

1. Click "Add Record" or similar button
2. Select "A" as record type
3. Enter "@" or leave "Host/Name" blank (for root domain)
4. Enter "75.2.70.75" in "Points to" or "Value" field
5. Set TTL to "Automatic" or "3600" (1 hour)
6. Save the record.

Creating a second A Record (99.83.190.102):

1. Repeat the same process
2. Select "A" as record type
3. Enter "@" or leave "Host/Name" blank
4. Enter "99.83.190.102" in "Points to" or "Value" field
5. Set TTL to "Automatic" or "3600"
6. Save the record

Host/Name field configuration varies by registrar:

• Some use "@" symbol for root domain
• Others leave the field blank
• Some show your domain name
• All methods achieve the same result

TL settings and recommendations control how long DNS servers cache your records. Lower TTL (600-3600 seconds) enables faster updates, while higher TTL reduces DNS query load. Use 3600 (1 hour) for launches, then increase to 86400 (24 hours) after stable operation.

How to set up the Webflow CNAME record

The CNAME record handles the www. version of your domain (and any other subdomain you point to Webflow). The value is always:

1. Click "Add Record"
2. Select "CNAME" as record type
3. Enter "www" in "Host/Name" field
4. Enter "proxy-ssl.webflow.com" in "Points to" or "Value" field
5. Set TTL to "Automatic" or "3600"
6. Save the record.

Pointing to proxy-ssl.webflow.com enables Webflow's SSL certificate management and secure hosting infrastructure. This exact value is required—variations like "proxy.webflow.com" or "webflow.com" will not work.

Host/Name field configuration for CNAME records uses "www" specifically, not "@" or blank. This creates the www subdomain (www.yoursite.com).

If you're using Cloudflare, make sure the CNAME's proxy status is set to DNS only (gray cloud icon), not Proxied (orange cloud). Webflow handles SSL itself — Cloudflare's proxy in front breaks the SSL provisioning.

Common CNAME errors to avoid:

• Missing "www" in host field
• Incorrect proxy-ssl.webflow.com spelling
• Adding "http://" or "https://" prefixes
• Pointing to webflow.io domain instead
• Using an A record instead of CNAME for www

Removing Conflicting Records

Identifying conflicting A and CNAME records that point to previous hosting services prevents DNS conflicts. Look for A records pointing to old IP addresses or CNAME records pointing to previous hosts.

Safely deleting old hosting records requires:

• Verify old records aren't actively used
• Delete conflicting A Records for @ host
• Delete conflicting CNAME Records for www host
• Remove old hosting provider records
• Keep only new Webflow records

Preserving email DNS records prevents email disruption. MX Records, TXT Records for email authentication (SPF, DKIM), and email-related CNAME Records should remain unchanged unless you're also migrating email services.

Testing before deletion By creating new records first, then removing old ones after verification, continuous service is ensured. If uncertain about a record's purpose, research or contact your registrar before deletion.

Step 3: Domain Verification in Webflow

Verification Process

Returning to Webflow settings after configuring DNS records:

1. Navigate back to Webflow Site Settings

2. Go to Publishing > Production

3. Find your added custom domain

4. Locate "Check Status" button next to the domain.

Check Status button functionality triggers Webflow to query DNS servers and verify proper record configuration. Webflow checks that both A Records and CNAME Record point correctly to Webflow infrastructure.

Understanding verification status messages:

• "Pending": DNS records not yet visible to Webflow (propagation in progress)
• "Connected": DNS records properly configured and verified
• "Error": DNS configuration problems detected
• "Needs attention": Additional configuration required

Verification timeline expectations vary based on DNS propagation speed. Most domains verify within 4-8 hours, though 24-48 hours represents the maximum typical timeframe. TTL settings affect verification speed.

Setting Default Domain

"www vs root domain" preference affects which domain displays in browser address bars. Most businesses prefer www.yoursite.com as default, with yoursite.com redirecting automatically.

Making a domain default:

1. After domain verification shows "Connected"
2. Click the three-dot menu next to your preferred domain
3. Select "Make Default" or "Set as Default"
4. Webflow configures automatic redirects from non-default to default domains.

SEO implications of default domain require consistency. Choose one version (www or root) as default and maintain that choice to avoid duplicate content issues and consolidate SEO authority.

Redirect behavior automatically sends traffic from the non-default domain to the default domain using 301 redirects, preserving SEO value and ensuring consistent brand presentation.

Step 4: SSL Certificate Configuration

Webflow's Automatic SSL

Let's Encrypt certificate provisioning happens automatically after domain verification. Webflow requests and installs free SSL certificates from Let's Encrypt, a trusted certificate authority.

SSL certificate generation timeline typically completes within minutes of domain verification but can take up to an hour. Webflow displays SSL status in domain settings.

Certificate renewal automation occurs automatically before expiration. Let's Encrypt certificates expire after 90 days, but Webflow renews them automatically 30 days before expiration, ensuring continuous SSL coverage.

Multi-domain certificate coverage includes both the root domain and the www subdomain in a single certificate. Webflow's SSL certificate covers all connected custom domains and subdomains.

Enabling Force HTTPS

Accessing SSL settings in Webflow:

1. Navigate to Site Settings > Publishing
2. Scroll to "SSL Certificate" section
3. Locate "Force HTTPS" toggle
4. Enable after SSL certificate is issued.

Force HTTPS toggle redirects all HTTP traffic to HTTPS automatically, ensuring all visitors access your site securely. This setting should be enabled for all production sites.

HTTP to HTTPS redirection uses Webflow 301 permanent redirects that preserve SEO value while upgrading connection security. Search engines recognize and reward HTTPS usage with minor ranking boosts.

Testing secure connections involves:

• Visit http://yoursite.com (without s)
• Verify automatic redirect to https://yoursite.com
• Check browser shows padlock icon
• Test all pages for mixed content warnings
• Verify forms submit over HTTPS

Step 5: Publishing Your Site

Publishing Process

The publish button location sits prominently in the top-right corner of Webflow Designer. This bright blue button initiates the publishing workflow.

Selecting domains for publishing:

1. Click the Publish button
2. Webflow displays all connected domains
3. Check boxes next to domains to receive updates:
   - webflow.io staging domain
   -  Custom domain(s)
4. Click "Publish to Selected Domains."

Staging vs production domains serve different purposes. Staging domains (yoursite.webflow.io) enable testing before public launch, while production domains (yoursite.com) serve live traffic.

Publish confirmation appears after successful publishing, displaying which domains received updates and confirming live status.

Verifying Live Site

Testing custom domain access:

• Open browser in incognito/private mode
• Type your custom domain in address bar
• Verify site loads correctly
• Check HTTPS displays properly
• Test from different devices and networks

Checking all pages load correctly requires systematic testing:

• Navigate through all main sections
• Test internal links
• Verify images load
• Confirm forms work
• Check CMS collection pages
• Test e-commerce functionality if applicable

Verifying SSL certificate ensures secure connections:

• Click padlock icon in browser address bar
• View certificate details
• Confirm issued to your domain
• Check expiration date (should be ~90 days future)
• Verify certificate chain valid

Testing across devices validates responsive design:

• Desktop computers (various screen sizes)
• Tablets (iPad, Android tablets)
• Mobile phones (iOS and Android)
• Different browsers on each device type

Registrar-Specific Instructions

GoDaddy DNS Setup

Navigating GoDaddy DNS Management:

1. Log into GoDaddy account
2. Click "My Products"
3. Find your domain, click "DNS"
4. Scroll to "Records" section

Adding records in GoDaddy interface:

• A Records: Type "A", Name "@", Value "IP address"
• CNAME Record: Type "CNAME", Name "www", Value "proxy-ssl.webflow.com"
• TTL defaults to 600 (10 minutes)

GoDaddy-specific quirks:

• Default A Records often exist (delete these)
• Parking page CNAME for www (must delete)
• Interface shows @ as domain name after saving
• May show multiple IP addresses initially

Verification typically takes 2-6 hours with GoDaddy's fast DNS servers, though the official timeframe remains 24-48 hours.

Namecheap DNS Setup

Accessing Advanced DNS settings:

1. Log into Namecheap account
2. Domain List > Manage button
3. Navigate to "Advanced DNS" tab
4. Find "Host Records" section

Record configuration in Namecheap:

• A Records: Type "A Record", Host "@", Value "IP"
• CNAME: Type "CNAME Record", Host "www", Value "proxy-ssl.webflow.com"
• Remove default parking page records

Namecheap defaults to change:

• Delete default parking page redirect
• Remove default URL Redirect Record
• Clear default CNAME Records
• Keep email records (MX, TXT) if using Namecheap email

Common Namecheap issues:

• Forgetting to delete parking page
• Mixing Basic DNS with Advanced DNS
• Not waiting full 30 minutes for cache clearing
• Leaving old A Records active

Cloudflare DNS Setup

Cloudflare DNS management interface:

1. Log into Cloudflare account
2. Select your domain
3. Click "DNS" in left menu
4. Add Records section

Proxy vs DNS-only settings:

• Orange cloud icon = Proxied (Cloudflare CDN active)
• Gray cloud icon = DNS only (direct to Webflow)
• Use DNS-only (gray cloud) for Webflow domains
• Proxied mode conflicts with Webflow's SSL

SSL/TLS mode configuration:

• Set SSL/TLS to "Full (strict)" after Webflow SSL activates
• Avoid "Flexible" mode (causes redirect loops)
• Enable "Always Use HTTPS" in SSL settings
• Disable "Automatic HTTPS Rewrites" to prevent conflicts

Cloudflare optimization settings:

• Page Rules can supplement Webflow
• Auto Minify should be disabled (Webflow handles this)
• Rocket Loader should be disabled
• Keep basic security features active

Google Domains DNS Setup

1. Log into Google Domains (now managed by Squarespace)
2. Select domain > DNS
3. Scroll to "Custom resource records"
4. Add records one by one

Google Domains specific format:

• A Records: Name "@", Type "A", Data "IP address"
• CNAME: Name "www", Type "CNAME", Data "proxy-ssl.webflow.com"
• TTL typically 3600

Transfer to Squarespace note: Google Domains was sold to Squarespace in 2023. Existing Google Domains users can still manage DNS, but new registrations go through Squarespace with a similar interface.

Alternative registrars if leaving Google Domains:

• Cloudflare (domain registration + DNS)
• Namecheap (affordable, reliable)
• Porkbun (competitive pricing)
• Name.com (simple interface)

DNS propagation: why your Webflow site isn't live yet

Understanding Propagation

DNS propagation describes how DNS record changes spread across the global network of DNS servers maintained by ISPs and DNS providers.

Typical propagation timeframes:

• Minimum: 4-8 hours
• Average: 12-24 hours
• Maximum: 48 hours
• Some users may see changes within 1 hour

Factors affecting propagation speed:

• TTL settings (lower TTL = faster propagation)
• ISP DNS caching policies
• Geographic location
• DNS server refresh schedules
• Registrar DNS infrastructure

Global vs local propagation means some geographic regions see changes before others. Your local network might show updates while users in other countries still see old records.

DNS changes don't apply instantly. After updating your A and CNAME records, the new values propagate across global DNS servers over 24–48 hours. During this window, your site may be reachable from some networks but not others.

To check propagation status:

• Visit dnschecker.org
• Enter your domain
• Select A for the root domain or CNAME for www
• Confirm the values match what Webflow requires

If 90%+ of global checks return the Webflow values, you're propagated. Click <strong>Publish to selected domains</strong> in Webflow and verify the site loads on the custom domain.

If SSL shows as "Pending" or "Failed" in Webflow's domain panel after 48 hours, the most common cause is a stuck CAA record at the registrar. Delete any existing CAA records, wait an hour, and Webflow will retry SSL provisioning automatically.

SEO and Analytics Setup

Meta titles and descriptions:

• Unique title for each page (50-60 characters)
• Compelling descriptions (150-160 characters)
• Keywords included naturally
• Brand name in titles
• No duplicate titles/descriptions

Open Graph and Twitter cards:

• OG title, description, image set
• Twitter card type configured
• Image dimensions correct (1200x630px)
• Test with Facebook Debugger
• Validate with Twitter Card Validator

Sitemap generation:

• Webflow auto-generates sitemap.xml
• Verify the sitemap is accessible at /sitemap.xml
• Submit sitemap to Google Search Console
• Submit to Bing Webmaster Tools
• Update robots.txt if needed

Google Analytics integration:

• GA4 tracking code installed
• Events tracking configured
• Conversion goals set up
• E-commerce tracking (if applicable)
• Cross-domain tracking (if needed)

Google Search Console setup:

• Property verified via DNS or HTML
• Sitemap submitted
• URL inspection working
• Coverage report reviewed
• Performance tracking active

Conclusion

Switching DNS and going live with your Webflow site requires systematic execution across domain connection, DNS configuration, SSL setup, and comprehensive testing. The process combines technical precision with thorough quality assurance to ensure professional launches.

DNS propagation patience remains essential as global DNS updates require time despite proper configuration. Testing from multiple locations and networks validates successful propagation before announcing your launch.

Ready to launch your Webflow site with confidence and professional execution that ensures flawless performance from day one? theCSS Agency specializes in comprehensive Webflow launches, including DNS configuration, pre-launch testing, go-live management, and post-launch support. Our proven methodology guarantees smooth launches without technical surprises.

Schedule your launch consultation today and discover how professional launch management eliminates stress, prevents downtime, and delivers the polished launch your website deserves.

FAQs

1. How long does it take to switch DNS to Webflow?

The configuration itself takes 10 minutes at your registrar. DNS propagation across global servers takes 24–48 hours typically, though it can complete in under 4 hours if your registrar has fast propagation and you weren't migrating from another active host.

2. Do I need to keep my old hosting active during the Webflow DNS switch?

Yes, for safety. Keep your old hosting active until you've confirmed Webflow is serving traffic from 90%+ of global DNS checks. This prevents downtime during propagation. Once Webflow is fully live, you can cancel old hosting.

3. Why does my Webflow SSL show as "Pending"?

SSL provisioning waits for DNS propagation to complete and for any CAA records at your registrar to allow Webflow's certificate authority (Amazon). If SSL stays Pending past 48 hours, check for existing CAA records and delete them, then wait an hour for Webflow to retry.

‍