CDN for Sitecore
A global delivery layer in front of Sitecore.
Sitecore published sites still need a CDN for media library files, static assets and anonymous HTML. Without it, every region depends on the content delivery cluster.
Cache published media and public pages at Cloud CDN. Bypass Experience Editor and personalised responses that cannot be shared. Purge on publish.
Why teams use Aptranet
What CDN for Sitecore looks like on this network.
Cloud CDN caches and accelerates eligible content on 210+ points of presence, with Origin Shield when the origin must stay out of the way.
Published sites closer to visitors
Anonymous HTML and assets are served from 210+ locations.
Media library off the CD cluster
Images and documents are cached at the edge after the first miss.
Content delivery hosts less exposed
The public hostname terminates at Cloud CDN with TLS 1.3 and DDoS mitigation.
How to set it up
A cutover you can validate before DNS moves.
Create the Cloud CDN configuration, prove it on an Aptranet hostname, then point production DNS when the path looks correct.
- 1Front the content delivery hostname
Pull the published Sitecore CD origin over HTTPS.
- 2Cache shareable output
Bypass Experience Editor, tracking-sensitive personalised variants and authenticated pages.
- 3Purge on publish
Invalidate item URLs and media when publishing completes.
- 4Attach certificates and DNS
Map the public domain after validating cache behaviour.
Outcomes
What changes once the hostname is on Aptranet.
- Published Sitecore traffic is cached globally
- Editing tools remain on Sitecore
- Media library files are delivered from the edge
- Publish can purge affected URLs
Keep reading
Related pages
More CDN use cases on the same Cloud CDN footprint.
Frequently Asked Questions
Only variants that are truly shareable. Most personalised HTML should bypass cache or use a cache key you fully control.
No. Sitecore output cache still reduces CD work. Cloud CDN repeats that result worldwide.
Include the query string in the cache key when Sitecore media URLs vary by width or crop.
Yes. Cloud CDN can be one delivery path in a Sitecore architecture that already uses more than one CDN.