Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit WEBFLOW-I-819 Clean asset links: Host assets on a site's Custom Domain and don't prepend the names with number ID strings.

Allow custom domain for assets (images, CSS, and JS) Merged

For customers with strict firewall whitelist policies that have not whitelisted cloudfront.net, the css, image, and JS assets do not load, essentially breaking our site for those customers. It makes our site look unprofessional and reflects poorly on us.

It would be fantastic if the images, css, and js assets could be hosted behind the custom domain as well. That will reduce the likelihood that the site appears broken and simplify the process of fixing it for customers for whom it still is (e.g. we just need to tell them to whitelist our custom domain, instead of both our custom domain and cloudfront.net)

  • Stein Setvik
  • Aug 8 2017
  • Pete Minnelli commented
    18 Jan, 2018 08:26pm

    I can't think of any clients of mine who find it acceptable that their files can't be hosted on their own domain. Don't understand why webflow hasn't ironed this out yet.

  • Webmaster Archplan commented
    8 Jan, 2018 05:48pm

    This is definetely needed, since e.g. PDFs etc. should be hosted on own domain not a clooudfront domain as links etc. won't bring SEO power and such.

  • Eric Potratz commented
    20 Oct, 2017 12:02am

    I believe having a custom domain within the image/PDF URL would have some SEO benefits as well. Google gives SEO credit for unique images. Surprised they're aren't more votes for this.

  • and 12 more