How do I set the default domain in Webflow?

Choose one host for the whole site

The default domain is the address Webflow redirects your other connected domains to. If yourdomain.com and www.yourdomain.com both reach the same site, people and crawlers can open one page on two hosts. Webflow's help article says a default domain helps avoid SEO penalties due to duplicate content.

Quick connect sets the default to the www subdomain, for example www.yourdomain.com. You can switch it to the root, yourdomain.com, when that is the address you want in the browser. Pick one host and keep it. Shared links and the global canonical URL should use that same host.

Connect every domain you plan to use before you set the default. DNS for a first connection is a separate job. This setting only chooses which connected host receives the traffic.

Set the default, then publish

Open Site settings, then Publishing, then Production. Beside the domain you want people to land on, click Make default.

The redirect starts when you publish. Publish the site to the default domain. Then type the other host into the address bar. The browser should finish on the default.

Example: the brand uses www. In Production you click Make default on www.yourdomain.com and publish to that domain. You open https://yourdomain.com. The address bar should end on https://www.yourdomain.com. If it stays on the root, publish again to the default domain and confirm Make default is on www.

Redirect an old domain, or add one later

The same control sends an old domain to a new one. Connect both the old domain and the new domain. Set one of the new domains as the default. Publish to that default domain. Visitors who still type the old domain are sent to the new one.

That redirect covers the whole domain. It does not move a renamed page. A path that changed, such as /old-services now living at /services, still needs its own 301.

A domain you add after a default already exists can vanish from the publish menu. Webflow documents a short sequence for that. Click Make default next to the domain that is already the default. Publish the site to the new domain or subdomain. Then set the default domain again. The new host can be published, and the preferred host is the default once more.

Line the canonical host up with the default

Webflow's default domain article says to update the global canonical tag URL when it does not match the default domain. If the two disagree, a different domain may show up in some places. The help article names Android's share sheet as one case, because that sheet reads the global canonical URL.

After you change the default, point the global canonical URL at the same host. Include www only when www is the default. Publish again so the live tags match the host you chose.

If the published site then shows a too many redirects error, the default and the DNS records are looping, often between www and the root. Webflow says you are likely still on deprecated DNS records. In Site settings, Publishing, Production, copy the current records. At the DNS host, remove the old A records and CNAME records for those hosts and replace them with the records Webflow shows. Verify the domain, click Make default on either the root or www, and publish. DNS can take up to 48 hours to settle, though many domains update sooner. Retest in a private window, or on a phone, so a cached error page is not what you are judging.