CDN for Squarespace
Give Squarespace sites an edge you can measure.
Squarespace sites that outgrow a single publishing hostname — extra landing domains, large media, or a reverse-proxy in front of the site — need cache, purge and TLS controls outside the website builder.
Place Cloud CDN in front of the hostnames you control. Cache public pages and media, bypass site-editor traffic, and keep commerce checkout on Squarespace when it must stay there.
Why teams use Aptranet
What CDN for Squarespace 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.
Public pages closer to visitors
Cached Squarespace or proxied HTML is served from 210+ locations with 30 ms average latency.
Portfolio and product media at the edge
Large galleries are cached and can be converted or resized at delivery time.
TLS and DDoS on the public hostname
TLS 1.3, managed certificates and L3-L7 DDoS mitigation sit on the delivery path you expose.
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.
- 1Confirm you control DNS for the hostname
Cloud CDN maps a domain you own. Editor hostnames stay on Squarespace.
- 2Pull the public origin
Reverse-proxy the live site or the adjacent landing origin and verify cache hits.
- 3Exclude editor and checkout where needed
Do not cache site editing or shopper-specific commerce flows.
- 4Cut over DNS
Attach the certificate and point the domain at the distribution.
Outcomes
What changes once the hostname is on Aptranet.
- Public Squarespace hostnames can sit on Cloud CDN
- Editor traffic is not cached
- Media is delivered from the edge
- You get independent purge, logs and TLS controls
Keep reading
Related pages
More CDN use cases on the same Cloud CDN footprint.
Frequently Asked Questions
Only when DNS for the public hostname can point at Cloud CDN and the origin accepts the pull. Review the current Squarespace custom-domain behaviour first.
Do not cache editor or preview hosts. Only the public site hostname should go through Cloud CDN.
Yes. Cache anonymous catalogue and content. Keep checkout and account flows on Squarespace.
Publish in Squarespace, then purge the changed URLs so the edge does not wait on TTL.