We can now create wildcard URL redirects, and Domain Connect auto-creates them to forward the www to the root. 🎉

What is still very much needed is an indication in the domain dropdown (within a funnel or website's settings where you select which domain to connect) of which, www or root, is the primary and one to be selected to connect to (or simply not showing the other as an option) - this is not intuitive to the average user.

Loving the progress!

I agree! The option in the settings for connecting a domain should only be for confirming whether the platform lands traffic on a www or non-www version of the domain.

I currently manually create this with just TWO Cloudflare page rules, and this should be easily achieved automatically inside of HighLevel to ensure traffic sent to EITHER version of the URL still lands on the correct page:

Rule #1

Forwarding URL (Status Code: 301 - Permanent Redirect, Url: https://www.website.com/$1)

Rule #2

Forwarding URL (Status Code: 301 - Permanent Redirect, Url: https://www.website.com/$1)

This is a massive inconvenience that is fundamental functionality. When a client, or when we set up a GHL website, it should automatically work with root and www as does WordPress and SiteGround. It's also causing conflicts with the funnel pages because it's allowing the funnel to choose the same domain as what is chosen for the website. I agree with all the comments below.

A rapidly-deployable fix for this would be a button in the Settings page that checks to see what domain format is selected for the funnel, and creates URL Redirects for every page in the funnel for the other domain format (root vs www).

It would need to remove any existing URL redirects for the given funnel before creating the new ones, but that's the only technical hurdle that would prevent this from being implemented... an EASY fix, and FAST to market.

This functionality has worked for me in the past, still works for some sub-accounts but not others. This was functional in the past, but they some what recently broke it.

All in all, I would like to see the "primary domain" field be eliminated and dynamically create an index of the domains from the website/funnel/blog/redirect associations and then push it to the reverse proxy configurations. All in all, it would be much cleaner experience for the end users.

Really need this as well. Hope to see it soon.

This is HUGE! Every other builder I have used has ways to do this automatically. Constantly dealing with 404 issues. Cloning a site that gets updated regularly is doubling all of the work required.

When onboarding a number of clients, we have issues with old www backlinks that are attached to the site and creates a lot of issues in Google Search Console. The ability to add www and have it automatically redirect to a non-www page is crucial for any serious web designer.