I think the whitelabel option should rewrite src
from
<img src="https://uploads-ssl.webflow.com...
into
<img src="https://uploads-ssl.mydomain.com...
or something more generic like
<img src="https://uploads-ssl.webassets.com (an alias like webform.io to hide webflow brand)
The same for the Webflow object inside the main JS app.
is this something doable?
Andrea Brai
Hi all - this is live: now when you enable whitelabeling for a site, your assets will live at a generic, unbranded URL (something like https://assets.website-files.com/randomfilename, instead of https://uploads-ssl.webflow.com/randomfilename).
For existing projects, be sure to republish that site to ensure your images serve at an unbranded URL.
.svg){kind=logo}
How do you enable whitelabeling?
Attachments Open full size
This doesn't really solve the problem. If I have an asset that others link to, all the link juice flows to webflow, not my site. This is an SEO nightmare.
This should absolutely be a top priority to implement.
Attachments Open full size
Is this still available?
I have a pro account with the Editor white labeling enabled. But my assets still display as 'uploads.weflow...' in the URL.
Attachments Open full size
Are we still unable to use our own URLs for assets?
Attachments Open full size
We need our own URLs. It is cosmetically better to have non-webflow url but it doesn't solve real issues such as whitelisting of sites through strict firewalls, such as China or corporate firewalls.
Attachments Open full size
Maybe I'm missing something here. What/how is this set up?
Can we specify the "unbranded" URL? If so, how?
thanks - dave
Attachments Open full size
This would also help solve hosting speed in China. If a URL has received the right authorizations in China it can be cached there. But as our content is hosted on a webflow URL and Webflow doesn't have an ICP code our site is extremely slow in China.
Attachments Open full size
Please incorporate this along with to FTP feature!
Attachments Open full size
Awesome
Attachments Open full size
This would mean we could do a lot of great things with CDNs and speed things up a lot
Attachments Open full size
Webflow, you are doing so much right, but...
I can understand why hosting these files on your own domain might is easier, but it's a really unprofessional look for anyone building a site with downloads or the like.
Can you provide some feedback, so we can set expectations with clients or even decide whether Webflow is the right fit?
Thanks
Attachments Open full size
Please do this in conjunction with WEBFLOW-I-1057
Attachments Open full size
When the white label for assets will be implemented? Thanks!
Attachments Open full size
For those who export their static sites, you can have all Webflow references removed automatically by using https://jinglebell.io ! And obviously the assets file paths will be custom because you're using your own hosting under your own domain!
Attachments Open full size
Yes. for sure.
Attachments Open full size
If i am paying for white-label service than I should have it covered all the way! PLEASE have this be fixed ASAP. There is a reason why we are doing white labeling on our end!
Thanks,
Julianne.
Attachments Open full size
As suggested in https://wishlist.webflow.com/ideas/WEBFLOW-I-1173 the file name should be a simple extension of the route domain: https://domain.com/files/file.example or a clean, simple subdomain: https://files.domain.com/file.txt, https://assets.domain.com/file.txt ext
Please set it up in whichever way that allows files to be password protected/exclusively accessible through login of a password protected page.
Attachments Open full size
Couldn't agree more!
Attachments Open full size
+1 very important!!!
Attachments Open full size
hi guys! any news about this idea? It shouldn't be so hard to develop... please consider adding it on top of roadmap! thanks
Attachments Open full size