CDN for Nuxt
Nuxt builds. Cloud CDN delivers the result worldwide.
Nuxt apps combine hashed client bundles with SSR or SSG pages. Those files should not all depend on a single Node origin.
Cache _nuxt assets with long TTLs. Cache anonymous pages and payloads at Cloud CDN. Bypass preview and authenticated routes. Purge on deploy.
Why teams use Aptranet
What CDN for Nuxt 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.
Client bundles at the edge
Hashed _nuxt files are served from 210+ PoPs with 30 ms average latency.
SSG and SSR HTML you can cache
Anonymous routes can be stored at Cloud CDN so Node is not on every page view.
One hostname for the app
Assets, pages and APIs you expose can share the same distribution and certificate.
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.
- 1Connect the Nuxt origin
Pull the Nitro or static-host origin over HTTPS.
- 2Split cache policy by path
Immutable cache for _nuxt. Purgeable cache for HTML and payload files.
- 3Bypass preview
Nuxt preview and user-specific routes must reach the origin.
- 4Purge on release
Invalidate HTML after each production deploy.
Outcomes
What changes once the hostname is on Aptranet.
- Nuxt client assets are cached globally
- Shareable pages live at the edge
- Preview remains dynamic
- Releases purge HTML immediately
Keep reading
Related pages
More CDN use cases on the same Cloud CDN footprint.
Frequently Asked Questions
Yes. Static output is an ideal CDN origin. Cloud CDN adds global cache, TLS and purge.
Cache the generated HTML and purge or use a TTL that matches how fresh the page must be.
Only public GET responses. Authenticated or mutation APIs must bypass cache.
Give each route a cache policy that matches whether the HTML is shareable.