We want the option to stage and dev on custom domain (white label if you like) for sites.
So instead of client.webflow.io we could have client.our-agency.net
We only need one domain so it would be
client1.our-agency.net, client2.our-agency.net, client3.our-agency.net and so on.
Dan Andersen
Enterprise customers and Enterprise Partners can use a custom domain as their Webflow site’s staging domain rather than the webflow.io subdomain.
With this update you’ll be able to use one consistent domain (your domain!) for staging to keep things simple and secure.
To add a custom domain for staging, go to your Site Settings → Publishing tab → under the Staging section, you can add a custom domain by selecting Use a custom domain.
Once you’ve added your custom domain, when you go to publish your site to staging you’ll see in the Publishing Workflow your new custom domain option as the default staging domain.
For more details on how to start using this today, check out our Webflow University lesson. To learn more about how to get access to custom staging domains or private staging, get in touch with our sales team.
.svg){kind=logo}
You can already connect multiple domains to a site, so adding the ability to present one of them as a staging domain, let alone, just allowing you to push to changes to one of two custom domains is a must!
white labeling is useless as is.
It should be that an account plan can designate a staging subdomain at their own domain to be used account wide.
projectname.staging.agencydomain.com
instead of
projectname.webflow.io
allowing this doesn't allow any abuse of hosting, since clients won't be happy with their site sitting on an agency domain in production. Or at least the vast majority wouldn't, and if they would, they would be fine with webflow.io too, which is already allowed without a site plan.
if webflow is getting money from an account plan, then this should be allowed.
2021 here: really, really wish that this was a thing. Kind of ridiculous that I have to present my client a Webflow hosted site in our development period. Also ridiculous that there's a limit to CMS items during staging.
The only alternative seems to be paying hosting for the site before it's done and passing that cost off to the client, but when development can take months, it's a cost that doesn't make all that much sense with as much as I'm already paying to develop in Webflow.
As an alternate solution, what if Webflow provided a 2nd staging domain? Something like temp.site that looks generic and doesn't include any Webflow branding.
Still can't believe webflow doesn't offer this but I guess they are holding out because you have to pay more money for a hosting plan if you want to show a preview without advertising them. Pretty slimy...
Guys, if you want to stage on subdomain, just create it at your Domain provider and transfer subdomain to webflow with a CNAME record. Works like a charm!
+1
Markus J.: "even if one pays for a plan that alledgetly allows for whitelablling" -> Exactly this.
You can definitely do this if your site has Webflow Hosting -
https://forum.webflow.com/t/how-to-white-labeled-staging-domain-for-clients/60454
I currently use a hosted webflow site as a landing page hosted on a subdomain to my ecommerce site.
Because of this I see the problem with allowing white-labeled URL staged sites, because I'd instantly have a free landing page builder if that were the case.
I also see the value of brand consistency for agencies when previewing sites to clients.
I think the simple solution is to require white labeled URL staged sites to be password protected and/or limit traffic to X users per month.
I think this would eliminate the "abusability" of an unrestricted white-labled staging URL while also providing the desired product to agencies and freelancers.
+1 Definitely need this in place.
Any updates to this?
Definitely need this one! Prior to the hosting price increase, we were paying $5/month during design phase to use our custom agency domain. With increased hosting fee this is no longer feasible.
Would be great to have this feature included with team plans, perhaps with some caveats about the domain, eg. it must include .dev, .design, .preview or a similar list.
We had a wildcard DNS record set up which pointed *.design.our-agency.com to Webflow servers so we could quickly add custom domains when providing preview links to clients.
Agreed, we really need this!
Agreed with what everyone else has said. Staging on a custom subdomain is an absolute must – especially for freelance/agency use.
Please consider adding this feature
I *just* signed up for the Pro plan with this expectation based on the "remove webflow branding from staging sites" portion of the White Labeling section. I guess the big "webflow.io" portion of the URL isn't part of that.
What's the point of white labeling anything at all if the LINK itself I send out has "webflow" in it?
A must for white labeling the platform! Clients/prospects sometimes connect the dots and ask why they would host the site with us rather than their own webflow account.
+1 on this feature. So important to be able to have our agency URL for staging! Please implement this feature with premium hosting plans.
Must have, thanks for that!
Absolutely – just found out in the forum that this isn't possible – even if one pays for a plan that alledgetly allows for whitelablling. Having to show a client a dev site under a webflow domain is not what I'd call whitelabelling!