Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Status Investigating
Created by Guest
Created on May 4, 2022

Create private subdomains for CDN images and pdf hosting

Optimizely is in the process of putting a CDN in place for all Spire Sites and Classic sites that have migrated to containers.

CDNs are great to improve site speed, however, best practice would be to implement the CDN as a subdomain of the main site. For example:

When turned on, our CDN currently shows all images and documents hosted on 'a random string of characters' on the domain. Example:

From a UX prespective, if your sales rep or customer shares a link to a spec sheet PDF from your site, it will look like a spam link, which saavy users (and email providers) have been trained to look for in emails to prevent phishing attacks. Example:

According to an article from SEMRush, "Enabling CDN using your own subdomain keeps the service proprietary to you and points SEO values of the CDN based resources to your root domain — instead of This approach maintains or even increases your main site's authority scores. This in turn boosts your SEO rankings. And of course, you are not bypassing your domain value to a third-party CDN site while improving page speed."

As currently implemented, using the domain, users will lose SEO value. Images and documents no longer appear to be hosted on your site, negatively affecting your brand authority, and removing important signals for SEO.