I recently changed my domain from karboncard.com to karbonbusiness.com. As daunting as that whole domain change was, the torture has not ended. There are these crazy redirect chains thanks to webflow that are increasing the latency on the website and confusing Google. So it 3 redirects for someone to go from http://karboncard.com to https://www.karbonbusiness.com
If I had access to htaccess file I could add some manual redirects but webflow doesn’t provide access to those. Surely, there is a solution.
Webflow’s redirects are efficient from a system engineering standpoint, which makes the chains more reliable and easier to debug.
In general you should never have http: or even https://karboncard.com out in the wild, because your canonical would have been https://www.karboncard.com.
Google doesn’t care, what it does care is that the end page in a valid 2xx result and that it matches its canonical. Then it will correctly update your change and preserve your SEO.
I find domain replacements on Webflow super easy- add the domain, make it default, done. Site migrations are more work due to the redirect table.
But if you really want to short circuit the redirects you can probably remove a hop or two on non-canonical requests using Cloudflare as a reverse proxy and its redirects feature.
In general though, it will follow a similar starting pattern… redirect http: to https: first, then process the next routing rule. It’s a common approach.